Merge branch 'develop' into DOCSPLAT-2993

Author: lopenchi

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,7 +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-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 %}

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

@@ -10,66 +10,74 @@ redirect_from: "/connections/destinations/catalog/actions-stackadapt/"
 
 {% include content/plan-grid.md name="actions" %}
 
-[StackAdapt](https://www.stackadapt.com/){:target="_blank"} is a programmatic advertising platform specializing in audience engagement. StackAdapt lets marketers deliver high-performing advertising campaigns across channels through real-time bidding, detailed audience targeting, and data-driven insights. StackAdapt’s integration with [Engage](/docs/engage/) helps you sync user data to optimize targeting and improve your campaign outcomes.
+[StackAdapt](https://www.stackadapt.com/){:target="\_blank"} is a programmatic advertising platform specializing in audience engagement. StackAdapt lets marketers deliver high-performing advertising campaigns across channels through real-time bidding, detailed audience targeting, and data-driven insights. StackAdapt’s integration with [Engage](/docs/engage/) helps you sync user data to optimize targeting and improve your campaign outcomes.
 
-This destination is maintained by StackAdapt. For any issues with the destination, submit a ticket to [StackAdapt's support team](https://support.stackadapt.com/hc/en-us/requests/new?ticket_form_id=360006572593){:target="_blank"}.
+This destination is maintained by StackAdapt. For any issues with the destination, submit a ticket to [StackAdapt's support team](https://support.stackadapt.com/hc/en-us/requests/new?ticket_form_id=360006572593){:target="\_blank"}.
 
 ## Getting started
 
 > info "Getting your StackAdapt GraphQL token"
-> If you do not have an existing StackAdapt read & write API key, contact the [StackAdapt team](https://support.stackadapt.com/hc/en-us/requests/new?ticket_form_id=360006572593){:target="_blank"}.
+> If you do not have an existing StackAdapt read and write API key, contact the [StackAdapt team](https://support.stackadapt.com/hc/en-us/requests/new?ticket_form_id=360006572593){:target="\_blank"}.
 
 ### Setting up the StackAdapt Audiences destination in Engage
 
 1. In your Segment workspace, navigate to **Connections > Catalog > Destinations**.
 2. Search for and select "StackAdapt Audiences".
 3. Click **Add Destination**.
 4. Select an existing Engage space source to connect to the StackAdapt Audience destination.
-5. Enter a name for your destination.
-6. On the Settings screen, provide your StackAdapt GraphQL API token. Then, put in the ID of the advertiser you want to sync the audience with. You can [find the advertiser ID in StackAdapt](#finding-the-advertiser-id-in-stackadapt).
-7. Toggle the destination on using **Enable Destination**.
-8. Click **Save Changes**.
-9. Follow the Destinations Actions documentation to [customize mappings](/docs/connections/destinations/actions/#customize-mappings) or [sync an Engage Audience](#sync-an-engage-audience).
-10. Enable the destination and click **Save Changes**.
+5. On the Settings screen, enter a name for your destination.
+6. Provide your StackAdapt GraphQL API token.
+7. Input the ID of the advertiser you want to sync the audience with. You can [find the advertiser ID in StackAdapt](#finding-the-advertiser-id-in-stackadapt).
+8. Toggle the destination on using **Enable Destination**.
+9. Click **Save Changes**.
 
 #### Finding the advertiser ID in StackAdapt
+
 In StackAdapt, go to **Execute** (or **Overview**) and click **Advertiser**.
 From the **Filter** section, select the advertiser. The advertiser ID appears in the URL after `advertiser=`.
 
 ### Sync an Engage Audience
 
 To sync an Engage audience with StackAdapt:
 
-1. Each Engage audience should only contain profiles that have a valid email address. Profiles missing an email address are not valid on StackAdapt's platform.
-2. Add a condition to the Engage audience to ensure the required email trait is included.
-3. Open the previously created StackAdapt Audience destination.
-4. Create a mapping: In the mappings tab, click **New Mapping** and select **Forward Audience Event**.
+Each Engage audience should only contain profiles that have a valid email address. Profiles missing an email address are not valid on StackAdapt's platform.
+
+1. Go to **Engage > Audiences** and select the audience you would like to sync.
+2. Scroll to the destinations section and add the **StackAdapt Audience** destination.
+3. Under the **Connection settings** section, enable **Send Identify**.
+4. Under **Event settings**, select **Customized Setup** to choose the list of profile traits you want to sync.
+   - Add **email** as an identifier.
+   - Add traits as needed. Note that you should set up corresponding mappings for the fields in step 9 for the traits selected here if you want them to be imported.
+5. Click **Save**.
+6. Click on the **StackAdapt Audience** destination under the **Destinations** section.
+7. Under the **Matching Mappings** tab, click **Add mapping**.
    - To reuse your Segment audience on the StackAdapt platform, select **Sync Audience**.
-   - To apply import profiles to the StackAdapt platform, select **Forward Profile**.
-   - **Note**: you don't have to set up both mappings.
-5. Define the event trigger: Click **Add Condition** and add this condition: **Event Type is `Track` or `Identify`**.
-6. Map fields:
+   - To import profiles to the StackAdapt platform, select **Forward Profile**.
+   - **Note**: You don't have to set up both mappings. The mappings will be shared across all audiences that have sync enabled to this destination. You should create a new destination if you wish to use different mappings for different audiences.
+8. Define the event trigger: Ensure the Event Type is `Track` or `Identify`.
+9. Map fields:
    - (**Required**:) Select a default value for `Marketing Status`.
-   - (**Required**:) Select the source field for `Email`.
-   - Select source field for `Standard User Properties`,
+   - (**Required**:) Confirm that you have a valid source field for `Email`.
+   - Select the source field for `Standard User Properties`. Ensure the source field matches the profile traits selected in step 4. You can learn more about the field format by hovering over the info icon of the field.
    - Create mappings for `Custom User Properties` if applicable.
+   - Follow the Destinations Actions documentation to [customize mappings](/docs/connections/destinations/actions/#customize-mappings).
 
-To verify that your audience syncs with StackAdapt, open StackAdapt and navigate to **Audience & Attribution > Customer Data > Profiles**. On the Profiles tab, you should be able to see a list of profiles being synced to StackAdapt platform.
+To verify that your audience syncs with StackAdapt, open StackAdapt and navigate to **Audience & Attribution > Customer Data > Profiles**. On the Profiles tab, you should be able to see a list of profiles being synced to the StackAdapt platform.
 
 > info "Syncs can take up to 4 hours"
 > It can take up to 4 hours from the time you initiate a sync for profiles to show up in StackAdapt.
 
 To create a StackAdapt audience from your Engage audience:
 
-1. Open StackAdapt and navigate to **Audience & Attribution > Data Data > Segments**, then click **Create Segment**.
+1. Open StackAdapt and navigate to **Audience & Attribution > Customer Data > Segments**, then click **Create Segment**.
 2. Select the advertiser you have synced your audience to.
 3. Choose **Profile Properties > Segment** and select **External Audience Name** as the rule.
-4. Select a condition and put in the audience name as the filter.
+4. Select a condition and enter the audience name as the filter.
 5. Click **Submit** to create the segment.
 
 > info "Audience name format"
-> Use the *snake_case* name of the Segment Engage audience which can be found in **Settings**, shown in the following screenshot.
-![Image showing sample audience settings tab](./images/audience-example.png)
+> Use the _snake_case_ name of the Segment Engage audience which can be found in **Settings**, shown in the following screenshot.
+> ![Image showing sample audience settings tab](./images/audience-example.png)
 
 ### Sending an audience to StackAdapt
 
@@ -80,4 +88,4 @@ To create a StackAdapt audience from your Engage audience:
 
 ## Data and privacy
 
-Review [StackAdapt's Data Processing Agreement](https://www.stackadapt.com/data-processing-agreement){:target="_blank"} to learn more about StackAdapt's privacy and data terms.
+Review [StackAdapt's Data Processing Agreement](https://www.stackadapt.com/data-processing-agreement){:target="\_blank"} to learn more about StackAdapt's privacy and data terms.