Release 25.42.1

src/_data/catalog/kotlin_resources.yml

@@ -16,7 +16,7 @@ items:
   categories: 
   - app
 - name: Android AdvertisingId Plugin
-  url: https://github.com/segmentio/analytics-kotlin/blob/main/samples/kotlin-android-app/src/main/java/com/segment/analytics/next/plugins/AndroidAdvertisingIdPlugin.kt
+  url: https://github.com/segmentio/analytics-kotlin/blob/1ef79eaf035549d08f91bac4e0a1de8ca6793e7b/samples/kotlin-android-app/src/main/java/com/segment/analytics/next/plugins/AndroidAdvertisingIdPlugin.kt
   categories: 
   - plugin
 - name: Screen Recording Plugin

src/connections/auto-instrumentation/configuration.md

@@ -13,10 +13,21 @@ This guide assumes that you've already added the Signals SDK to your application
 > info "Auto-Instrumentation in public beta"
 > Auto-Instrumentation is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.                  
 
+> info "Regional availability"
+> Auto-Instrumentation isn't supported in EU workspaces.
+
 ## Converting signals to events
 
 After you set up the Signals SDK to capture the signals you want to target, you can create rules in your Segment workspace to translate the captured signals into traditional Segment analytics events. These rules are deployed in your application the next time a user launches your app.
 
+The process works like this:
+
+1. The SDK sends raw signals from your app or website to Segment.
+2. You build event rules in your workspace that define how those signals should become analytics events.
+3. You publish the event rules.
+
+After publishing, Segment analyzes user interactions in your app or website against these rules and automatically generates analytics events when matching interactions occur.
+
 ### Getting started with rule creation
 
 1. Ensure you have the `Workspace Owner` or `Source Admin` role in Segment. If your source is connected to a tracking plan, you will also need, at a minimum, the `Tracking Plan Read-only` role. To view the content in the Event Builder tab, you will need, at a minimum, the `Source Read-only` role.
@@ -47,13 +58,11 @@ You can enrich your events by adding properties based on signal metadata. For ex
 
 These properties are sent alongside your event, giving your team deeper insights without requiring any manual instrumentation.
 
+<!-- PW, 6 August 2025: Commenting this section out for now
 #### Preview your event rule
 
 To verify that a rule is working as expected, you don't need to enter a cycle of creating and updating the rule, generating signals, then checking the source debugger for the generated event. As you create, edit, or view a rule, you can preview it in real time against the current signal buffer to see which signals match and what the resulting event will look like. Event properties are mapped to the values found in the matched signals, and complete matches are grouped by anonymous ID.
 
-
-<!-- PW, 6 August 2025: Commenting this section out for now
-
 The Rules Editor also lets you test your rules with recent signals to verify that they produce the data you need before you deploy. 
 
 The following example tracks all Screen events:

src/connections/auto-instrumentation/event-builder.md

@@ -10,6 +10,9 @@ You can use it to create Track, Identify, Page, and other event types directly f
 > info "Auto-Instrumentation Private Beta"
 > Auto-Instrumentation is currently in Private Beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience.
 
+> info "Regional availability"
+> Auto-Instrumentation isn't supported in EU workspaces.
+
 ## Access the Event Builder
 
 The Event Builder appears as a tab within each source, next to the Debugger. If you don't see the Event Builder tab, first confirm that you've installed the required Auto-Instrumentation SDK. 

src/connections/auto-instrumentation/index.md

@@ -29,6 +29,9 @@ Auto-Instrumentation simplifies tracking in your websites and apps by removing t
 > info "Auto-Instrumentation in public beta"
 > Auto-Instrumentation is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
 
+> info "Regional availability"
+> Auto-Instrumentation isn't supported in EU workspaces.
+
 ## Background
 
 Collecting high-quality analytics data is essential, but traditional tracking setups often fall behind as business needs change. Instrumentation updates take time away from other engineering priorities, and these delays reduce visibility and increase the burden on engineering teams.

src/connections/auto-instrumentation/kotlin-setup.md

@@ -10,6 +10,9 @@ This guide shows how to install and configure the library, as well as how to ena
 > info "Auto-Instrumentation in public beta"
 > Auto-Instrumentation is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
 
+> info "Regional availability"
+> Auto-Instrumentation isn't supported in EU workspaces.
+
 ## Before you start
 
 To use Signals with Android, you need:

src/connections/auto-instrumentation/swift-setup.md

@@ -10,6 +10,9 @@ Learn how to connect an existing source, integrate dependencies, turn on Auto-In
 > info "Auto-Instrumentation in public beta"
 > Auto-Instrumentation is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
 
+> info "Regional availability"
+> Auto-Instrumentation isn't supported in EU workspaces.
+
 ## Step 1: Get your source write key
 
 You need the `writeKey` from an existing Segment source. To find it:

src/connections/auto-instrumentation/web-setup.md

@@ -10,6 +10,9 @@ Learn how to connect an existing source, integrate dependencies, turn on Auto-In
 > info "Auto-Instrumentation in public beta"
 > Auto-Instrumentation is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
 
+> info "Regional availability"
+> Auto-Instrumentation isn't supported in EU workspaces.
+
 ## Step 1: Get your source write key
 
 You need the `writeKey` from an existing Segment source. To find it:

src/connections/destinations/catalog/ab-smartly/index.md

@@ -24,12 +24,12 @@ Segment provides specific implementation details for A/B Smartly in the sections
 1. From the Destinations catalog page in the Segment App, click **Add Destination**.
 2. Search for "A/B Smartly" in the Destinations Catalog, and select the "A/B Smartly" destination.
 3. Choose which Source should send data to the "A/B Smartly" destination.
-4. Go to the A/B Smartly dashboard(https://your-org-name.absmartly.com/apikey/list){:target="_blank”}, find and copy the "API key" that you created for segment.
+4. Go to the A/B Smartly dashboard (`https://your-org-name.absmartly.com/apikey/list`), find and copy the "API key" that you created for segment.
 5. Enter the "API Key" in the "A/B Smartly" destination settings in Segment.
 6. If the integration requests for an Application name go to your A/B Smartly dashboard (`https://your-org-name.absmartly.com/application/create`) and create an Application named "Segment", or whatever you would like to call it. Use that name in the Application field of the integration settings.
 7. Add also your A/B Smartly Collector endpoint. It's the same endpoint that you are using in all your A/B Smartly SDKs.
 8. Enter the environment from your Environment list (`https://your-org-name.absmartly.com/environment/list`) that should receive your Segment data. Most likely it will be the production one.
-9. And finally a mapping of Segment Identities to A/B Smartly Units(`https://your-org-name.absmartly.com/unit/list`). You should map all of your Segment identities that you would like to use in your A/B tests to the units that you already have in A/B Smartly. Users must map all the identity types, but not for the individual users. Map all of your ids in your Unit List(`https://your-org-name.absmartly.com/unit/list`).
+9. And finally a mapping of Segment Identities to A/B Smartly Units (`https://your-org-name.absmartly.com/unit/list`). You should map all of your Segment identities that you would like to use in your A/B tests to the units that you already have in A/B Smartly. Users must map all the identity types, but not for the individual users. Map all of your ids in your Unit List(`https://your-org-name.absmartly.com/unit/list`).
 10. Optionally go to "Goal Mapping" and start adding the track calls that you would like to see showing up on A/B Smartly as goals. You only need to create a name mapping if the name of the goal on A/B Smartly's platform is different from the name of the track call in Segment.
 
 ## Page

src/connections/destinations/catalog/aboardly/index.md

@@ -10,8 +10,6 @@ Once the Segment library is integrated with your server, toggle Aboardly on in y
 
 Aboardly supports the `identify` and `track` methods.
 
-- - -
-
 ## Identify
 
 When you `identify` a user, we'll pass that user's information to Aboardly with `userId` as Aboardly's External Customer ID. Aboardly recognizes all traits sent by Segment, however in order to send emails you should always add the `email` trait when possible.

src/connections/destinations/catalog/actions-first-party-dv360/index.md

@@ -9,7 +9,7 @@ redirect_from: /connections/destinations/catalog/first-party-dv360/
 
 Google’s [Display & Video (DV360)](https://marketingplatform.google.com/about/display-video-360/){:target="_blank"} is an end-to-end campaign management tool that enables enterprise customers to plan, measure, and run display and video advertisements. Segment’s integration with DV360 enables Segment customers to sync audiences created in Engage with DV360 for centralized audience management and improved retargeting.
 
-This destination is different from the existing DV360 Actions as it allows you to upload [contact info](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#ContactInfo){:target="_blank"} and the [mobile device ID](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#mobiledeviceidlist){:target="_blank"}.
+This destination is different from the existing DV360 Actions as it allows you to upload [contact info](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#contactinfo){:target="_blank"} and the [mobile device ID](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#mobiledeviceidlist){:target="_blank"}.
 
 This destination can only be used with Engage. 
 
@@ -68,12 +68,15 @@ Segment automatically sends consent as `TRUE` for this destination.  Segment use
 
 ## Data requirements
 Based on Google’s documentation, make sure you send the correct required identifiers:
-* [Contact info list requirements](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#contactinfo){:target="_blank"}
+* [Contact info list requirements](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#contactinfo){:target="_blank"}
    * For example, you must send first name, last name, ZIP code, and country code all together and not just one. Make sure all phone numbers are in [E.164 format](https://en.wikipedia.org/wiki/E.164){:target="_blank"}. 
-* [Mobile ID Requirements](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#mobiledeviceidlist){:target="_blank"}
+* [Mobile ID Requirements](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#mobiledeviceidlist){:target="_blank"}
 
 
 ## FAQs
 
 #### When will my data appear in DV360?
 When you complete the connection between Segment and DV360, it can take from 24 to 48 hours for Google to create the user list. This must complete before Segment can begin to sync users into that list. 
+
+#### What is membershipDurationDays and its limit?
+The duration in days that an entry remains in the audience after the qualifying event. The set value must be greater than 0 and less than or equal to 540.

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

@@ -0,0 +1,23 @@
+---
+title: FullSession (Actions) Destination
+id: 68c14f4eefb643527597844c
+beta: true
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[FullSession](https://fullsession.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} provides user behavior analytics software that helps you visualize all user interactions, analyze trends and patterns with laser precision, and optimize your website for peak performance. The Segment integration for FullSession helps accurately identify your customers and track their behavior within the FullSession dashboard.
+
+This destination is maintained by FullSession. For any issues with the destination, [contact the FullSession support team](mailto:support@fullsession.com){:target="_blank"}.
+
+## Getting started
+
+1. From your workspace’s [Destination Catalog](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"}, search for **“FullSession”**.
+2. Select **FullSession**, then click **Add Destination**.  
+3. Choose an existing **JavaScript Source** to connect with FullSession (Actions).  
+4. Navigate to the [FullSession Setup](https://app.fullsession.io/settings/setup){:target="_blank"} page and copy your **Customer ID**, beginning with `cus_`.  
+5. Paste the **Customer ID** into the **FullSession Destination settings** in Segment.  
+6. Before enabling the destination, go to the **Mappings** tab and configure the mappings to ensure the correct data is captured.  
+7. Once your mappings are configured and enabled, go to the **Settings** tab and enable the destination. Segment then automatically loads the **FullSession recording snippet** in the user’s browser.
+
+{% include components/actions-fields.html %}