Release 25.27.1

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2025-06-26 
+# destination categories last updated 2025-07-03 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2025-06-26 
+# destination data last updated 2025-07-03 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2025-06-26 
+# destination data last updated 2025-07-03 
 items:
   - id: 54521fd925e721e32a72eee1
     display_name: Pardot

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2025-06-26 
+# source categories last updated 2025-07-03 
 items:
   - display_name: A/B testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2025-06-26 
+# sources last updated 2025-07-03 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET

src/_includes/content/functions/settings.md

@@ -17,7 +17,7 @@ You can configure the details about this setting, which change how it's displaye
 - **Type** - Type of the setting's value.
 - **Description** - Optional description, which appears below the setting name.
 - **Required** - Enable this to ensure that the setting cannot be saved without a value.
-- **Encrypted** - Enable to encrypt the value of this setting. Use this setting for sensitive data, like API keys.
+- **Secret** - Enable this to ensure that sensitive data, like API key values or passwords, are not displayed in the Segment UI. 
 
 As you change the values, a preview to the right updates to show how your setting will look and work.
 

src/_includes/content/functions/source-settings.md

@@ -0,0 +1,28 @@
+<!-- usually placed under a heading called "Settings and Secrets" -->
+
+Settings allow you to pass configurable variables to your function, which is the best way to pass sensitive information such as security tokens. For example, you might use `settings` as placeholders to use information such as an API endpoint and API key. This way, you can use the same code with different settings for different purposes. When you deploy a function in your workspace, you are prompted to fill out these settings to configure the function.
+
+First, add a setting in **Settings** tab in the code editor:
+
+![A screenshot of the functions settings tab](/docs/connections/functions/images/settings-tab-empty.png){:width="500"}
+
+Click **Add Setting** to add your new setting.
+
+![A screenshot of the "Add Setting" section of the functions settings tab, with apiKey settings included](/docs/connections/functions/images/add-source-setting-dialog.png)
+
+You can configure the details about this setting, which change how it's displayed to anyone using your function:
+
+- **Label** - Name of the setting, which users see when configuring the function.
+- **Name** - Auto-generated name of the setting to use in function's source code.
+- **Type** - Type of the setting's value.
+- **Description** - Optional description, which appears below the setting name.
+- **Required** - Enable this to ensure that the setting cannot be saved without a value.
+- **Encrypted** - Enable to encrypt the value of this setting. Use this setting for sensitive data, like API keys.
+
+As you change the values, a preview to the right updates to show how your setting will look and work.
+
+Click **Add Setting** to save the new setting.
+
+Once you save a setting, it appears in the **Settings** tab for the function. You can edit or delete settings from this tab.
+
+![A screenshot of the functions settings tab, showing the apiKey setting](/docs/connections/functions/images/settings-tab-non-empty.png){:width="500"}

src/_sass/components/_accordion.scss

@@ -13,7 +13,7 @@
   &__heading {
     padding-right: 20px;
     font-size: 16px;
-    font-weight: 600;
+    font-weight: 500;
     color: color(gray-800);
     line-height: 1.71;
     position: relative;
@@ -38,7 +38,7 @@
     display: inline-block;
     margin-top: 7px;
     font-size: 14px;
-    font-weight: 600;
+    font-weight: 500;
     text-decoration: underline;
   }
 

src/_sass/components/_button.scss

@@ -1,6 +1,6 @@
 .button {
   font-size: 12px;
-  font-weight: 600;
+  font-weight: 500;
   line-height: 1.5;
   text-align: center;
   padding: 8px 12px;

src/_sass/components/_code-example.scss

@@ -26,7 +26,7 @@
       color: color(gray-700);
       font-size: 12px;
       line-height: 16px;
-      font-weight: 600;
+      font-weight: 500;
 
       &:hover {
         color: color(primary);

src/_sass/components/_destination-menu.scss

@@ -1,6 +1,6 @@
 .destination-menu {
   &__title {
-    font-weight: 600;
+    font-weight: 500;
     padding-bottom: 10px;
     font-size: 14px;
   }

src/_sass/components/_list-steps.scss

@@ -9,7 +9,7 @@
     height: 40px;
     border-radius: 50%;
     background-color: color(primary-lighter);
-    font-weight: 600;
+    font-weight: 500;
     color: color(primary);
   }
 

src/_sass/components/_markdown.scss

@@ -183,7 +183,7 @@
       &::before {
         content: counter(list-items) ". ";
         color: color(primary);
-        font-weight: 600;
+        font-weight: 500;
         transform: translate(-23px, 0);
       }
     }
@@ -227,7 +227,7 @@
 
     th {
       color: color(gray-700);
-      font-weight: 600;
+      font-weight: 500;
       padding: 12px;
 
       @include breakpoint(medium up) {
@@ -240,7 +240,7 @@
     }
     th > code {
       color: #696f8c;
-      font-weight: 600;
+      font-weight: 500;
       font-size: 10px;
       background-color: inherit;
     }
@@ -392,7 +392,7 @@ tr.show {
   padding: 0px 6px;
   border-radius: 4px;
   height: 16px;
-  font-weight: 600;
+  font-weight: 500;
   text-transform: uppercase;
   color: rgb(71, 77, 102);
   opacity: 0.65;

src/_sass/components/_mobile-menu-side.scss

@@ -14,7 +14,7 @@
   }
 
   &__title {
-    font-weight: 600;
+    font-weight: 500;
   }
 
   &__list {

src/_sass/components/_quickinfo.scss

@@ -14,7 +14,7 @@
     background-color:#E7E4F9;
     color: #6E62B6;
     text-transform: uppercase;
-    font-weight: 600;
+    font-weight: 500;
     padding: 0px 6px;
     border-radius: 4px
 
@@ -35,7 +35,7 @@
     margin-top: 12px;
     th {
       font-size: 14px;
-      font-weight: 600;
+      font-weight: 500;
       padding: 5px 13px;
       background-color: #F4F6FA;
       text-transform: none;

src/_sass/components/_thumbnail-integration.scss

@@ -56,7 +56,7 @@
     border-radius: 4px;
     font-size: 11px;
     line-height: 16px;
-    font-weight: 600;
+    font-weight: 500;
     text-transform: uppercase;
     letter-spacing: 0.2px;
     color: #6E62B6;

src/_sass/components/_widget.scss

@@ -12,7 +12,7 @@
 
     a {
       text-decoration: underline;
-      font-weight: 600;
+      font-weight: 500;
     }
   }
 

src/_sass/generics/_typography.scss

@@ -19,5 +19,5 @@ samp {
 }
 
 strong {
-  font-weight: 600;
+  font-weight: 500;
 }

src/_sass/vendors/_premonition.scss

@@ -94,7 +94,7 @@
 
   .header {
     font-size: 14px;
-    font-weight: 600;
+    font-weight: 500;
     line-height: 24px;
   }
 

src/connections/destinations/actions.md

@@ -183,7 +183,7 @@ If necessary, click **New Mapping** to create a new, blank action.
     This step looks for events that match the criteria in the [debugger queue](/docs/connections/sources/debugger/), so you might need to Trigger some events with the expected criteria to test your conditions. You can skip the test step if needed, and re-try it at any time.
 3. Select data models to [enrich your events](/docs/unify/linked-profiles/linked-events/) with.
 4. Set up the data mapping from the Segment format to the destination tool format.
-- You can click the Source field, then select the **Enrichments** tab to view and select Enrichments to use.
+- You can click the Source field, then select previously configured Enrichments from the Event Properties tab.
 5. Test the mapping with data from a sample event.
     The edit panel shows you the mapping output in the format for the destination tool. The **Select Object** option sends the entire object from the event, while the **Edit Object** option lets you map each individual property. You can change your mapping as needed and re-test.
 6. When you're satisfied with the mapping, click **Save**. Segment returns you to the Mappings table.
@@ -200,29 +200,45 @@ If necessary, click **New Mapping** to create a new, blank action.
 Segment offers suggested mappings that automatically propose relevant destination fields for both model columns and payload elements. For example, if your model includes a column or payload field named `transaction_amount`, the feature might suggest mapping it to a destination field like `Amount` or `TransactionValue`. This automation, powered by intelligent autocompletion, matches and identifies near-matching field names to streamline the setup. For more information, see [Segment's suggested mappings blogpost](https://segment.com/blog/ai-assisted-magical-mappings/){:target="_blank”} and the [Suggested Mappings Nutrition Label](/docs/connections/reverse-etl/suggested-mappings-nutrition-facts). 
 
 > warning ""
-> Review the suggested mappings for accuracy before finalizing them as the suggestions aren't guaranteed to be 100% accurate. 
+> Review the suggested mappings for accuracy before finalizing them as the suggestions aren't guaranteed to be 100% accurate.
+
+## Static values
+Segment supports 4 static value types in Destination Actions mappings: string, boolean, number, and null. 
+* To create a string static value, type the string directly into the input field. 
+* To create boolean, number, and null values, use the **Static values** tab to create the appropriate static value based on its type.
+
+## Functions
+In Destination Actions mappings, functions transform event data before it sends to the destination. This enables custom data handling, such as selecting non-null values or formatting fields.
 
 ### Coalesce function
 
 The coalesce function takes a primary value and uses it if it is available. If the value isn't available, the function uses the fallback value instead. 
 
+### Case function
+
+The case function allows you to change the casing of a given string value.
+
+### JSON function
+
+The JSON function allows you to convert an object or array to a JSON encoded string, or to convert from JSON to objects.
+
+### Flatten function
+
+The flatten function allows you to flatten a nested object to an object with a depth of 1. Keys are delimited by the configured separator. For example, an object like {a: { b: { c: 1 }, d: 2 } } will be converted to { 'a.b.c': 1, 'a.d': 2 }.
+
 ### Replace function
 
 The replace function allows you to replace a string, integer, or boolean with a new value. You have the option to replace up to two values within a single field.
 
 ### Concatenate function
 
-To combine two values in the event variable field, you can concatenate them using plain text and variables together. For example, to prepend the country code to a phone number, enter `+1{{Phone Number}}`.
+To combine 2 values in the event variable field, you can concatenate them using plain text and variables together. For example, to prepend the country code to a phone number, enter `+1{{Phone Number}}`. Segment evaluates this field as a string, so placing text next to a variable automatically concatenates them.
 
-Segment evaluates this field as a string, so placing text next to a variable automatically concatenates them.
+You can't concatenate event variables and plain text with static values and functions. Adding a static value or function into an input field replaces any previously added event variables and plain text.
 
 ![Mapping UI showing two concatenated fields: "+1 phone" and "context.page.url context.page.path"](images/mapping-concatenation.png)
 
-### Flatten function
-
-The flatten function allows you to flatten a nested object to an object with a depth of 1. Keys are delimited by the configured separator. For example, an object like {a: { b: { c: 1 }, d: 2 } } will be converted to { 'a.b.c': 1, 'a.d': 2 }.
-
-### Conditions
+## Conditions
 
 > info ""
 > Self-service users can add a maximum of two conditions per Trigger.

src/connections/destinations/catalog/actions-linkedin-conversions/index.md

@@ -43,6 +43,10 @@ Your inputs must meet the following criteria:
   - `LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID`
   - `ACXIOM_ID`
   - `ORACLE_MOAT_ID`
-- `conversionHappenedAt` must be a valid timestamp (milliseconds since epoch) and must have happened in the past 90 days
+- `conversionHappenedAt` must be a valid epoch timestamp (milliseconds since epoch) and must have happened in the past 90 days. Segment additionally accepts [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601){:target="_blank"} formatted timestamps, and converts it to a valid epoch timestamp.
 
 Any deviations from this specification might lead to failed inputs.
+
+### Why does LinkedIn show "no integration data" after I successfully sent the data?
+
+One possible reason is that your events are missing the **currency** and **amount** fields. LinkedIn’s API won't reject events due to the lack of currency and amount data, but their platform will silently drop these events later during processing. Please ensure your payload includes those fields with valid values.

src/connections/destinations/catalog/actions-ortto/index.md

@@ -46,6 +46,8 @@ This destination is maintained by Ortto. For support or questions, [contact the
 
 **Ortto (Actions)** allows you to sync your Segment users with an Ortto Audience, enabling precise activation of rich, behavior-based segments—perfect for lifecycle marketing, retargeting, and large-scale personalization. You can manually create new audiences or use existing ones in Ortto, and dynamically add or remove contacts through profile upserts or activity tracking. This gives you real-time control over audience membership.
 
+To define which audience the contact should be linked to, enter the **Audience Name** in the "**Associate Audience**" section.
+
 Ortto blocks rapid audience re-entry to avoid undesirable side-effects from asynchronous updates. If a contact exits an audience and then re-enters the audience within 1 minute, Ortto blocks the update that causes them to rejoin the audience. Ortto uses a daily synchronization to make sure the result of any rapid updates is correctly applied.
 Ortto updates the Segment member audience field as normal, and any audience re-entries throughout the day that are longer than 1 minute after the last exit are processed in real time.
 

src/connections/destinations/catalog/actions-reddit-audiences/index.md

@@ -11,7 +11,7 @@ The Reddit Audiences destination allows advertisers to send Engage audiences fro
 This destination is maintained by Reddit. For any issues with the destination, [contact their Support team](mailto:[email protected]).
 
 ### Reddit Requirements 
-* Create a Reddit Ads account. * Find your ad account ID in [Accounts](https://ads.reddit.com/accounts). 
+- **Create a Reddit Ads account.** Find your ad account ID in [Accounts](https://ads.reddit.com/accounts){:target="_blank"}. 
 
 ### Connect Reddit Ads to your workspace
 

src/connections/destinations/catalog/actions-the-trade-desk-crm/index.md

@@ -53,6 +53,7 @@ To sync additional Audiences from your Engage space, create a separate instance
 
 ## Limitations
 
+* Audiences up to 100 million profiles in size will be synced.
 * An audience must have at least 1500 unique members; otherwise, the destination fails, and the data won't sync. 
 * Audience attempts to sync once per day.
 * Audience sync is a full sync.

src/connections/destinations/catalog/actions-webhook-extensible/microsoft-integration-recipe.md

@@ -89,10 +89,10 @@ To create or update the Account entity only, you can skip this step and directly
 
 #### Data mapping
 
-1. Create a new Mapping in the Mappings tab and select the **Send** HTTP action.
+1. Create a new mapping in the Mappings tab and select the **Send** HTTP action.
 2. Choose which events you want to send to Google Search Ads 360 API using the Event filters.
 3. Fill out mapping fields:
-        - Specify the URL:  `[Organization URI]/api/data/v9.2/accounts` (this is for creating new accounts)
+    - Specify the URL:  `[Organization URI]/api/data/v9.2/accounts` (this is for creating new accounts)
 4. Use the mapping interface and search for the “body” parameter that was created in the insert function to select the transformed object that can be sent as the event body.
 5. Turn off batching for this operation.
 

src/connections/functions/destination-functions.md

@@ -23,12 +23,12 @@ All functions are scoped to your workspace, so members of other workspaces can't
 
 1. From your workspace, go to **Connections > Catalog** and click the [Functions tab](https://app.segment.com/goto-my-workspace/functions/catalog){:target="_blank"}.
 2. Click **New Function**.
-3. Select **Destination** as the function type and click **Build**.
+3. Select **Destination** as the function type and click **Next: Build Function**.
 
-After you click **Build**, a code editor appears. Use the editor to write the code for your function, configure settings, and test the function's behavior.
+After you click **Next: Build Function**, a code editor appears. Use the editor to write the code for your function, configure settings, and test the function's behavior.
 
 > success ""
-> **Tip:** Want to see some example functions? Check out the templates available in the Functions UI, or in the open-source [Segment Functions Library](https://github.com/segmentio/functions-library){:target="_blank"}. (Contributions welcome!)
+> **Tip:** Want to see some example functions? Check out the templates available in the Functions UI, or in the open-source [Segment Functions Library](https://github.com/segmentio/functions-library){:target="_blank"}.
 
 
 ## Code the destination function

src/connections/functions/source-functions.md

@@ -276,7 +276,7 @@ The handler for Source functions is `onRequest()`.
 
 ## Create settings and secrets
 
-{% include content/functions/settings.md %}
+{% include content/functions/source-settings.md %}
 
 Next, fill out this setting's value in **Test** tab, so that you can run the function and check the setting values being passed.
 

src/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/firebase-react-native.md

@@ -24,8 +24,8 @@ Run `pod install` after the installation to autolink the Firebase SDK.
 
 See [React Native Firebase](https://rnfirebase.io) and [React Native Firebase Analytics](https://rnfirebase.io/analytics/usage) for more details of Firebase packages.
 
-> info "rnfirebase dependency"
-> You will need to follow the [install guide](/docs/connections/sources/catalog/libraries/mobile/react-native/classic) for the rnfirebase dependency too. This may include adding the `GoogleService-Info.plist` and the `google-services.json` file.
+> info "Installation"
+> You will need to follow the install guide for [Android](https://rnfirebase.io/analytics/usage/installation/android){:target="_blank”} and/or [iOS](https://rnfirebase.io/analytics/usage/installation/ios){:target="_blank”}. This includes adding the `GoogleService-Info.plist` and the `google-services.json` file.
 
 
 ## Using the Plugin in your App