diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index 730322405a..49592364ef 100644 --- a/src/_data/catalog/destination_categories.yml +++ b/src/_data/catalog/destination_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination categories last updated 2025-02-27 +# destination categories last updated 2025-03-06 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml index 0020d974da..6b0446b8ac 100644 --- a/src/_data/catalog/destinations.yml +++ b/src/_data/catalog/destinations.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2025-02-27 +# destination data last updated 2025-03-06 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -42021,9 +42021,9 @@ items: screen: false page: true platforms: - browser: true + browser: false mobile: false - server: true + server: false warehouse: true cloudAppObject: false linkedAudiences: false @@ -42037,9 +42037,9 @@ items: mobile: false server: false cloud: - web: true + web: false mobile: false - server: true + server: false settings: - name: retlAdAccountId type: string diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index 721676fa68..ef26d1c6dd 100644 --- a/src/_data/catalog/destinations_private.yml +++ b/src/_data/catalog/destinations_private.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2025-02-27 +# destination data last updated 2025-03-06 items: - id: 54521fd925e721e32a72eee1 display_name: Pardot diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index a27bc4f36f..2c222fd03b 100644 --- a/src/_data/catalog/source_categories.yml +++ b/src/_data/catalog/source_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# source categories last updated 2025-02-27 +# source categories last updated 2025-03-06 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml index 0f568ce409..a095f04ade 100644 --- a/src/_data/catalog/sources.yml +++ b/src/_data/catalog/sources.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# sources last updated 2025-02-27 +# sources last updated 2025-03-06 items: - id: 8HWbgPTt3k display_name: .NET diff --git a/src/_data/changelogs/analytics-android.yml b/src/_data/changelogs/analytics-android.yml index 4c27a09432..bdeceb5bbb 100644 --- a/src/_data/changelogs/analytics-android.yml +++ b/src/_data/changelogs/analytics-android.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-12-19 +# Releases last updated 2025-03-06 releases: - version: 4.11.3 url: https://github.com/segmentio/analytics-android/releases/tag/4.11.3 diff --git a/src/_data/changelogs/analytics-go.yml b/src/_data/changelogs/analytics-go.yml index e24c0d7594..3b23eb090c 100644 --- a/src/_data/changelogs/analytics-go.yml +++ b/src/_data/changelogs/analytics-go.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-12-19 +# Releases last updated 2025-03-06 releases: - version: v3.3.0 url: https://github.com/segmentio/analytics-go/releases/tag/v3.3.0 diff --git a/src/_data/changelogs/analytics-ios.yml b/src/_data/changelogs/analytics-ios.yml index 8a96782e5d..ec522b62d4 100644 --- a/src/_data/changelogs/analytics-ios.yml +++ b/src/_data/changelogs/analytics-ios.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-12-19 +# Releases last updated 2025-03-06 releases: - version: 4.1.8 url: https://github.com/segmentio/analytics-ios/releases/tag/4.1.8 diff --git a/src/_data/changelogs/analytics-java.yml b/src/_data/changelogs/analytics-java.yml index f8a187c8e0..c7f1041d80 100644 --- a/src/_data/changelogs/analytics-java.yml +++ b/src/_data/changelogs/analytics-java.yml @@ -1,3 +1,3 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-12-19 +# Releases last updated 2025-03-06 releases: [] diff --git a/src/_data/changelogs/analytics-node.yml b/src/_data/changelogs/analytics-node.yml index 1fac05eb28..41fffae534 100644 --- a/src/_data/changelogs/analytics-node.yml +++ b/src/_data/changelogs/analytics-node.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-12-19 +# Releases last updated 2025-03-06 releases: - version: '' url: https://github.com/segmentio/analytics-node/releases/tag/v6.2.0 diff --git a/src/_data/changelogs/analytics-php.yml b/src/_data/changelogs/analytics-php.yml index 75578a34c5..afdf8d1620 100644 --- a/src/_data/changelogs/analytics-php.yml +++ b/src/_data/changelogs/analytics-php.yml @@ -1,6 +1,10 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-12-19 +# Releases last updated 2025-03-06 releases: +- version: 3.8.1 + url: https://github.com/segmentio/analytics-php/releases/tag/3.8.1 + date: '2025-01-27T18:42:28Z' + notes: "## What's Changed\r\n* Convert exec() output to string by @JeroenBakker in https://github.com/segmentio/analytics-php/pull/239\r\n\r\n## New Contributors\r\n* @JeroenBakker made their first contribution in https://github.com/segmentio/analytics-php/pull/239\r\n\r\n**Full Changelog**: https://github.com/segmentio/analytics-php/compare/3.8.0...3.8.1" - version: 3.8.0 url: https://github.com/segmentio/analytics-php/releases/tag/3.8.0 date: '2024-02-15T16:09:44Z' diff --git a/src/_data/changelogs/analytics-python.yml b/src/_data/changelogs/analytics-python.yml index f8a187c8e0..c7f1041d80 100644 --- a/src/_data/changelogs/analytics-python.yml +++ b/src/_data/changelogs/analytics-python.yml @@ -1,3 +1,3 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-12-19 +# Releases last updated 2025-03-06 releases: [] diff --git a/src/_data/changelogs/analytics-react-native.yml b/src/_data/changelogs/analytics-react-native.yml index b245dbd731..7e3f6e0753 100644 --- a/src/_data/changelogs/analytics-react-native.yml +++ b/src/_data/changelogs/analytics-react-native.yml @@ -1,6 +1,27 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-12-19 +# Releases last updated 2025-03-06 releases: +- version: '@segment/analytics-react-native-v2.20.4' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.20.4 + date: '2025-03-05T16:09:56Z' + notes: '' +- version: '@segment/analytics-react-native-plugin-appsflyer-v0.6.1' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-appsflyer-v0.6.1 + date: '2025-03-05T16:11:22Z' + notes: |- + ### Dependencies + + * **@segment/analytics-react-native:** upgraded to 2.20.4 +- version: '@segment/analytics-react-native-plugin-advertising-id-v1.3.4' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-advertising-id-v1.3.4 + date: '2025-03-05T16:10:44Z' + notes: |- + ### Dependencies + + * **@segment/analytics-react-native:** upgraded to 2.20.4 - version: '@segment/analytics-react-native-plugin-advertising-id-v1.3.3' url: >- https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-advertising-id-v1.3.3 @@ -190,32 +211,5 @@ releases: notes: |- ### Dependencies - * **@segment/analytics-react-native:** upgraded to 2.18.0 - * **@segment/sovran-react-native:** upgraded to 1.1.0 -- version: '@segment/analytics-react-native-plugin-facebook-app-events-v0.6.0' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-facebook-app-events-v0.6.0 - date: '2024-02-05T22:46:10Z' - notes: |- - ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0 - * **@segment/sovran-react-native:** upgraded to 1.1.0 -- version: '@segment/analytics-react-native-plugin-device-token-v1.1.0' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-device-token-v1.1.0 - date: '2024-02-05T22:44:32Z' - notes: |- - ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0 - * **@segment/sovran-react-native:** upgraded to 1.1.0 -- version: '@segment/analytics-react-native-plugin-destination-filters-v1.1.0' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-destination-filters-v1.1.0 - date: '2024-02-05T22:43:30Z' - notes: |- - ### Dependencies - * **@segment/analytics-react-native:** upgraded to 2.18.0 * **@segment/sovran-react-native:** upgraded to 1.1.0 diff --git a/src/_data/changelogs/analytics.NET.yml b/src/_data/changelogs/analytics.NET.yml index 35bd8b5a18..09f71ffbdb 100644 --- a/src/_data/changelogs/analytics.NET.yml +++ b/src/_data/changelogs/analytics.NET.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-12-19 +# Releases last updated 2025-03-06 releases: - version: '' url: https://github.com/segmentio/Analytics.NET/releases/tag/3.8.1 diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index 538f56f5b1..836c62e999 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -288,7 +288,7 @@ sections: - path: /connections/regional-segment title: Regional Segment - path: /connections/test-connections - title: Event Tester + title: Testing Connections - path: /connections/data-export-options title: Data Export Options - path: /connections/destination-data-control diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index 85ee24661d..e235093fa9 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -157,14 +157,13 @@ To delete a destination action: click the action to select it, and click **Delet This takes effect within minutes, and removes the action completely. Any data that would have gone to the destination is not delivered. Once deleted, the saved action cannot be restored. ## Test a destination action -To test a destination action, follow the instructions in [Testing Connections](/docs/connections/test-connections/). You must enable a mapping in order to test the destination. Otherwise, this error occurs: *You may not have any subscriptions that match this event.* +To test a destination action, follow the instructions in [Event Tester](/docs/connections/test-connections/). You must enable a mapping in order to test the destination. Otherwise, this error occurs: *You may not have any subscriptions that match this event.* You can also test within the mapping itself. To test the mapping: 1. Navigate to the **Mappings** tab of your destination. 2. Select a mapping and click the **...** and select **Edit Mapping**. -3. In step 2 of the mappings edit page, click **Load Test Event from Source** to add a test event from the source, or you can add your own sample event. -4. Scroll to step 4 on the page, and click **Test Mapping** to test the mapping and view the response from the destination. - +3. In step 2 of the **Set up mappings** page, click **Load event from source** to add a test event from the source, select **Generate sample event** for Segment to generate a sample event for you, or enter your own event. +4. Scroll to step 5 on the page and click **Send test event** to test the mapping and view the response from the destination. > info "Test Mapping might not return the events you're looking for" > Segment only surfaces a small subset of events for the Test Mapping feature and might not always return the event you're looking for. If you'd like to test with a specific event, copy a specific event from your [Source Debugger](/docs/connections/sources/debugger/) and paste it into the **Add test event** interface. diff --git a/src/connections/images/event-tester-2025.png b/src/connections/images/event-tester-2025.png new file mode 100644 index 0000000000..32743072a0 Binary files /dev/null and b/src/connections/images/event-tester-2025.png differ diff --git a/src/connections/images/event-tester-filter.png b/src/connections/images/event-tester-filter.png new file mode 100644 index 0000000000..cbe81df62d Binary files /dev/null and b/src/connections/images/event-tester-filter.png differ diff --git a/src/connections/sources/catalog/libraries/website/javascript/identity.md b/src/connections/sources/catalog/libraries/website/javascript/identity.md index 6c475819ee..7f57aa9c60 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/identity.md +++ b/src/connections/sources/catalog/libraries/website/javascript/identity.md @@ -168,6 +168,17 @@ analytics.track('Clicked Email', { This appends the `plan_id` trait to this Track event. This does _not_ add the name or email, since those traits were not added to the `context` object. You must do this for every following event you want these traits to appear on, as the `traits` object does not persist between calls. +By default, non-Identify events (like Track or Page) **don't automatically collect user traits** from previous Identify calls. To include traits from an `identify()` event in later events, you'll need to add them manually to the `context.traits` object within the `options` parameter. + +Each Analytics.js method has an `options` parameter where you can pass the `context.traits` object, but each method has a specific format. Follow the formats in the [Segment Spec](/docs/connections/spec/) when adding traits, like in these examples: + +- [Identify](/docs/connections/spec/identify/) - The [Analytics.js Identify](/docs/connections/sources/catalog/libraries/website/javascript/#identify) method follows this format : `analytics.identify([userId], [traits], [options], [callback])`; +- [Track](/docs/connections/spec/track/) - The [Analytics.js Track](/docs/connections/sources/catalog/libraries/website/javascript/#track) method follows this format : `analytics.track(event, [properties], [options], [callback])`; +- [Page](/docs/connections/spec/page/) - The [Analytics.js Page](/docs/connections/sources/catalog/libraries/website/javascript/#page) method follows this format : `analytics.page([category], [name], [properties], [options], [callback])`; +- [Group](/docs/connections/spec/group/) - The [Analytics.js Group](/docs/connections/sources/catalog/libraries/website/javascript/#group) method follows this format : `analytics.group(groupId, [traits], [options], [callback])`; + +Adding traits to events is especially useful if you're using [Actions destinations](/docs/connections/destinations/actions/), since it makes those traits available for mapping in the destination’s configuration. + ## Clearing Traits diff --git a/src/connections/test-connections.md b/src/connections/test-connections.md index df043c7756..3270536975 100644 --- a/src/connections/test-connections.md +++ b/src/connections/test-connections.md @@ -1,60 +1,79 @@ --- -title: "Event Tester" +title: Testing Connections --- +Segment provides these 2 testing tools to enable you to test your connections between Segment and your destination: +* [Event Tester](#event-tester): Test all of your enabled mappings within a destination. +* [Mappings Tester](#mappings-tester): Test a single mapping configuration for your destination. -Segment has an Event Tester that enables you to test your connections between Segment and your destination. You can access the Event Tester from your Source Debugger, or from your destination settings.    +Both testing tools share the same underlying testing infrastructure, which ensures consistent results across your testing workflows. The results from both testers display API requests, responses, and success/failure status to help you diagnose any issues. -> info "Available for server-side event streaming destinations only" -> This feature is only available for server-side integrations (also known as cloud-mode destinations). You can't use this for client-side integrations (also known as device-mode destinations). +You can use the Event and Mappings Tester for these products: +* [Connections](/docs/connections/) +* [Linked Audiences](/docs/engage/audiences/linked-audiences/) +* [Linked Events](/docs/unify/data-graph/linked-events/#testing-with-linked-events-enrichments) +* [Reverse ETL](/docs/connections/reverse-etl/) +* [Journeys](/docs/engage/journeys/) -## Use Cases +## Event Tester -There are two scenarios where you might want to use the Event Tester: +> info "" +> The Event Tester is only available for server-side, [cloud-mode](/docs/connections/destinations/#connection-modes) integrations. It doesn't work for client-side, [device-mode](/docs/connections/destinations/#connection-modes) integrations. +>

You must have write access in your Segment workspace to use the Event Tester. -* ensuring an event is successfully making it to a specific destination -* ensuring your new destination is configured correctly +The Event Tester enables you to test your connections between Segment and your destination. You can inspect both the request sent from Segment and the response you receive back from the destination. The tester provides a comprehensive view of how your event data flows through multiple mappings. You can use the Event Tester to ensure: +* An event successfully arrives to a specific destination +* Your new destination is configured correctly -## Ensuring an event is successfully making it to a specific destination +The Event Tester sends a real event that appears in your end tool alongside your existing data. -**1. Choose an event from the Source Debugger that you want to debug and select "Validate"** +### Using the Event Tester -Go to your Source Debugger, select an event and in the top right hand side of the debugger view, select "Validate". +> info "" +> The event tester only tests the enabled mappings for the destination. -![Screenshot of the Debugger tab, with a Checkout Started event selected and an error pointing to the Validate button.](images/event-tester_GgyOswJA.png) +To use the Event Tester: +1. Navigate to **Connections > Destinations** and select your destination. +2. Click the **Event Tester** tab. +3. Select the type of test event. You can choose from: Track, Identify, Page, Screen, Group. +4. Enter your test event payload. You can type in your own event or choose from **Load event from source** or **Generate sample event**. + * **Load event from source**: Segment loads an event based on your source. + * **Generate sample event**: Segment generates a sample event for you. +5. Click **Send test event to destination**. +   -**2. Choose the destination you want to test with** +If your test event successfully sends to the destination, you can see in the **View test outcome** section: +* The request, response, and status for each API call +* How many of your mappings matched +* The total number of API calls that were made as one test event can result in multiple API calls +* Which mappings were successful and which ones failed +* The destination's API endpoint used to make the request -Select the destination that you want to test this event with. At this time, you can only use the Event Tester for cloud-mode (server side) destinations. +![Screenshot of the Event Tester with a Track test event that resulted in 4 API calls](images/event-tester-2025.png) -![A screenshot of the destination selection pop up modal](images/event-tester_2JfoKddf.png) +You can navigate between the different API calls and can use the filter to navigate to specific mappings. -**3. Send event to destination** +![Screenshot of the Event Tester filter with dropdown of different mappings](images/event-tester-filter.png) -The event payload from your debugger that you just selected will automatically load in the JSON view. You have the option to edit the payload if you want. Assuming it looks good, select "Send Event" at the bottom right of the screen.  +## Mappings Tester +When you add a destination and create a mapping in Connections, Reverse ETL, Linked Audience, and Journeys, you can test the specific mapping using the Mappings Tester. The Mappings Tester only tests a single mapping at a time and you can edit field values before initiating a test. This helps you verify that your configured mapping works as expected. -![A screenshot of the Event Tester, with a track event selected](images/event-tester_J7TEDYvY.png) +Use the Mappings Tester when you need to: +* Verify a single mapping configuration +* Edit field values before testing a mapping +* Troubleshoot a specific mapping that isn't working as expected -**4. Ensure you're happy to send the test event to the destination** +### Using the Mappings Tester +To use the Mapppings Tester: +1. Navigate to the product (Connections, Reverse ETL, Linked Audience, or Journeys) you want to test the mapping for. +2. Select the destination that has the mapping you want to test. +3. Select **Edit mapping**. +4. Edit any values in the **Send test record** section. +5. Click **Send test event**. -This is a real event that will appear in your end tool alongside your existing data. If you're not comfortable with this, then select "Cancel" and do not send the event.  -![Screenshot of the popup that appears when you click the Send test event button.](/docs/guides/images/asset_Yxw1DJqb.png) - -**5. View the Partner API response** - -On the right hand side of the Event Tester you will see the response from the partner API. At the top, Segment provide of summary of the response. Below is the raw response payload Segment received that you can use for further debugging if necessary.  - -![A screenshot of the Event Tester with a successful response from the destination](images/event-tester_il6mvexS.png) - -If you are receiving an error and are unsure how to fix the issue, visit the partner docs (for example [https://developers.google.com/analytics/devguides/reporting/core/v3/errors](https://developers.google.com/analytics/devguides/reporting/core/v3/errors){:target="_blank”}) or contact the partner support team.  - -## FAQ - -#### Why can't I see the Event Tester when I log into my workspace? - -The Event Tester is only accessible to users with write access in their Segment workspace (read-only users will not see the Event Tester in their workspace).  +## FAQs #### The Event Tester experienced an error when sending my event. Why did this happen? diff --git a/src/engage/audiences/account-audiences.md b/src/engage/audiences/account-audiences.md index 6c5b49dcbc..8f2a71e46c 100644 --- a/src/engage/audiences/account-audiences.md +++ b/src/engage/audiences/account-audiences.md @@ -23,9 +23,11 @@ You can use account-level audiences to accomplish the following use cases: ## Enable account-level audiences -1. Contact [friends@segment.com](mailto:friends@segment.com) and provide your workspace ID to have account-level audiences enabled for your workspace. Navigate to **Settings > Workspace Settings > General Settings** to view your workspace ID. -2. Ensure that `group_id` is configured as an identifier in Engage Identity Resolution settings. For more information, see [Identity Resolution Settings](/docs/unify/identity-resolution/identity-resolution-settings/). -3. Instrument [group](/docs/connections/spec/group/) calls to send account information to Segment. +1. Contact [friends@segment.com](mailto:friends@segment.com) to request account-level audiences. Include: + - **Your Workspace ID** (which you can find in **Settings > Workspace Settings > General Settings**) + - **Your intended use cases** for account-level audiences +2. If your workspace has account-level audiences enabled, ensure that `group_id` is configured as an identifier in Engage [Identity Resolution settings](/docs/unify/identity-resolution/identity-resolution-settings/). +3. Instrument [Group calls](/docs/connections/spec/group/) to send account information to Segment. ## Account-level audience conditions diff --git a/src/engage/journeys/event-triggered-journeys-steps.md b/src/engage/journeys/event-triggered-journeys-steps.md index 278845711d..18f66b8a07 100644 --- a/src/engage/journeys/event-triggered-journeys-steps.md +++ b/src/engage/journeys/event-triggered-journeys-steps.md @@ -103,6 +103,38 @@ Segment creates these aliases automatically during setup, and they show up in th Deleting a Hold Until step can impact downstream steps that rely on it. When you delete a configured step, Segment displays a modal that summarizes the potential impact on related branches and steps. Review all dependencies carefully to avoid unintentionally disrupting the journey. +## Fixed delays + +The **Delay** step helps you control the timing of journey actions by pausing profiles for a set period before they continue in the journey. This enables controlled timing for messages, actions, or other journey events. + +Unlike the Hold Until step, Delay doesn't depend on a user action: profiles always move down the journey after the time you set. This makes Delay useful for pacing interactions, like spacing out emails, without requiring user engagement. + +### How Delay works + +When a journey reaches the Delay step: + +1. Profiles enter the step and wait for the configured duration. +2. Segment logs the profile's status in the observability timeline. +3. If the profile meets an exit condition during the hold period, the profile leaves the journey early. +4. After the delay ends, the profile moves to the next step in the journey. + +### Configurable parameters + +The following table explains the parameters you can configure for the Delay step: + +| Parameter | Details | +| ------------------ | ------------------------------------------------------- | +| Duration time unit | Set the delay period in minutes, hours, days, or weeks. | +| Minimum delay | 5 minutes | +| Maximum delay | 182 days (around 6 months) | + +To configure the Delay step: + +1. Drag the Delay step onto the journey canvas, or click **+** to add it. +2. (*Optional*) Give the step a unique name. +3. Enter a duration and select a time unit (minutes, hours, days, weeks). +4. Click **Save**. + ## Send to Destination The **Send to Destination** step lets you send journey data to one of your [configured Engage destinations](/docs/connections/destinations/), enabling real-time integration with tools like marketing platforms, analytics systems, or custom endpoints. @@ -218,4 +250,4 @@ There may be cases where events sent to Segment are missing specific properties - If an event property is mapped but is missing in the Track event, Segment still includes the mapped key in the payload but with a value of `undefined`. - Similarly, if a mapped trait is missing on the profile, the key is included in the payload with a value of `undefined`. -Carefully configuring mappings and handling missing attributes can help you maintain data integrity and avoid errors in downstream systems. \ No newline at end of file +Carefully configuring mappings and handling missing attributes can help you maintain data integrity and avoid errors in downstream systems. diff --git a/src/engage/product-limits.md b/src/engage/product-limits.md index ee999c65b6..c7d74d06ce 100644 --- a/src/engage/product-limits.md +++ b/src/engage/product-limits.md @@ -23,18 +23,17 @@ To learn more about custom limits and upgrades, contact your dedicated Customer ## Audiences and Computed Traits -| name | limit | Details | -| --------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Compute Concurrency | 5 new concurrent audiences or computed traits | Segment computes five new audiences or computed traits at a time. Once the limit is reached, Segment queues additional computations until one of the five finishes computing. | -| Edit Concurrency | 2 concurrent audiences or computed traits | You can edit two concurrent audiences or computed traits at a time. Once the limit is reached, Segment queues and locks additional computations until one of the two finishes computing. | -| Batch Compute Concurrency Limit | 10 (default) per space | The number of batch computations that can run concurrently per space. When this limit is reached, Segment delays subsequent computations until current computations finish. | -| Compute Throughput | 10000 computations per second | Computations include any Track or Identify call that triggers an audience or computed trait re-computation. Once the limit is reached, Segment may slow audience processing. | -| Events Lookback History | 3 years | The period of time for which Segment stores audience and computed traits computation events. | -| Real-time to batch destination sync frequency | 12-15 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | -| Event History | `1970-01-01` | Events with a timestamp less than `1970-01-01` aren't always ingested, which could impact audience backfills with event timestamps prior to this date. | -| Engage Data Ingest | 1x the data ingested into Connections | The amount of data transferred into the Compute Engine. | -| Audience Frequency Update | 1 per 8 hours | Audiences that require time windows (batch audiences), [funnels](/docs/engage/audiences/#funnel-audiences), [dynamic properties](/docs/engage/audiences/#dynamic-property-references), or [account-level membership](/docs/engage/audiences/#account-level-audiences) are processed on chronological schedules. The default schedule is once every eight hours; however, this can be delayed if the "Batch Compute Concurrency Limit" is reached. Unless otherwise agreed upon, the audiences will compute at the limit set forth. | -| Event Properties (Computed Traits) | 10,000 | For Computed Traits that exceed this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values. | +| name | limit | Details | +| --------------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Compute Concurrency | 5 new concurrent audiences or computed traits | Segment computes five new audiences or computed traits at a time. Once the limit is reached, Segment queues additional computations until one of the five finishes computing. | +| Edit Concurrency | 2 concurrent audiences or computed traits | You can edit two concurrent audiences or computed traits at a time. Once the limit is reached, Segment queues and locks additional computations until one of the two finishes computing. | +| Batch Compute Concurrency Limit | 10 (default) per space | The number of batch computations that can run concurrently per space. When this limit is reached, Segment delays subsequent computations until current computations finish. | +| Compute Throughput | 10000 computations per second | Computations include any Track or Identify call that triggers an audience or computed trait re-computation. Once the limit is reached, Segment may slow audience processing. | +| Real-time to batch destination sync frequency | 12-15 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | +| Event History | `1970-01-01` | Segment may not ingest events with a timestamp earlier than `1970-01-01`, which can impact audience backfills for older events. Segment stores data indefinitely, but ingestion depends on event timestamps.

While Segment stores all events, event conditions typically evaluate data from the past three years by default. Your plan or configuration may allow a longer time window. | +| Engage Data Ingest | 1x the data ingested into Connections | The amount of data transferred into the Compute Engine. | +| Audience Frequency Update | 1 per 8 hours | Audiences that require time windows (batch audiences), [funnels](/docs/engage/audiences/#funnel-audiences), [dynamic properties](/docs/engage/audiences/#dynamic-property-references), or [account-level membership](/docs/engage/audiences/#account-level-audiences) are processed on chronological schedules. The default schedule is once every eight hours; however, this can be delayed if the "Batch Compute Concurrency Limit" is reached. Unless otherwise agreed upon, the audiences will compute at the limit set forth. | +| Event Properties (Computed Traits) | 10,000 | For Computed Traits that exceed this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values. | ## SQL Traits diff --git a/src/engage/using-engage-data.md b/src/engage/using-engage-data.md index bf64a98156..be0e261c00 100644 --- a/src/engage/using-engage-data.md +++ b/src/engage/using-engage-data.md @@ -296,3 +296,4 @@ Connect any Cloud-mode destination that supports Identify or Track calls to Enga - [Pinterest Audiences](/docs/connections/destinations/catalog/pinterest-audiences/) - [Marketo Static Lists (Actions)](/docs/connections/destinations/catalog/actions-marketo-static-lists/) - [Responsys](/docs/connections/destinations/catalog/responsys/) +- [TikTok Audiences](/docs/connections/destinations/catalog/actions-tiktok-audiences/) diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index 613c9363eb..5c633fc754 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -125,7 +125,7 @@ Select the default retention period for the workspace in this setting. This valu You can select from the following Archive Retention time periods: -- 7 days +- 14 days - 30 days - 90 days - 180 days @@ -142,7 +142,7 @@ Override the workspace default retention period on a per-source level. You can select from the following Archive Retention time periods: - Default (This is the default value you set in the [Workspace Default Archive Retention Period](#workspace-default-archive-retention-period)) -- 7 days +- 14 days - 30 days - 90 days - 180 days diff --git a/src/unify/data-graph/index.md b/src/unify/data-graph/index.md index 1a14affc55..242e9e5f10 100644 --- a/src/unify/data-graph/index.md +++ b/src/unify/data-graph/index.md @@ -21,6 +21,9 @@ To use the Data Graph, you'll need the following: - Under **Profile materialized tables**, select all the tables (`user_identifier`, `user_traits`, `profile_merges`) for faster and more cost-efficient Linked Audiences computations in your data warehouse. - Under **Track event tables**, select **Sync all Track Call Tables** to enable filtering on event history for Linked Audiences conditions. +> info "" +> To define entity relationships, you need to enable Linked Audiences. Contact your Customer Success Manager to get access to Linked Audiences. + ## Step 1: Set up Data Graph permissions in your data warehouse > warning "" > Data Graph, Reverse ETL, and Profiles Sync require different warehouse permissions. diff --git a/src/unify/data-graph/linked-events.md b/src/unify/data-graph/linked-events.md index 0fe6f01a83..193f538a40 100644 --- a/src/unify/data-graph/linked-events.md +++ b/src/unify/data-graph/linked-events.md @@ -180,18 +180,23 @@ In the Mappings tab, locate the **Select Mappings** section where you can enrich 1. Select the property field that you'd like to enrich, then select the **Enrichments** tab. 2. Select the entity you want to send to your destination. -- You’ll have access to all rows/columns in your data warehouse associated with the property you've selected in the previous step. +- You have access to all rows/columns in your data warehouse associated with the property you've selected in the previous step. 3. Add the key name on the right side, which is what Segment sends to your destination. +4. Click **Save**. -> warning "" -> At this time, Linked Events doesn't support a preview of enriched payloads. +#### Testing with Linked Events Enrichments +The [Event Tester and Mappings Tester](/docs/connections/test-connections/#) support testing enrichments from Linked Events, allowing you to verify that entity data is correctly attached to your events before they reach destinations. When you have Linked Events configured, these enrichments appear in your test payload, showing you exactly how profile traits will add to your events. -### Save your enrichments +When you test mappings with Linked Events Enrichments: +* You can view the enriched fields in the **Request** section of the test results. +* Verify that the correct entity traits are attaching to your events based on your entity matching configuration. +* The tester includes any configured Linked Events enrichments in the sample payload. -When you're satisfied with the mappings, click **Save**. Segment returns you to the Mappings table. +This helps you confirm that the right information sends to your destinations when testing activation scenarios that rely on profile data enrichment + +> info "" +> If an enriched field appears empty in your test results, this could indicate either that the entity matching failed to find a matching profile, or that the profile exists but does not have data for that specific trait. -> warning "" -> At this time, when you select mappings or test events, you won’t see enrichment data. Enrichment data is only available with real events. ## Enrichment observability diff --git a/src/unify/product-limits.md b/src/unify/product-limits.md index 6c5b9f583f..9f7c9c1df5 100644 --- a/src/unify/product-limits.md +++ b/src/unify/product-limits.md @@ -39,18 +39,17 @@ Visit Segment's [pricing page](https://segment.com/pricing/){:target="_blank"} t ## Audiences and Computed Traits -| name | limit | Details | -| --------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Compute Concurrency | 5 new concurrent audiences or computed traits | Segment computes five new audiences or computed traits at a time. Once the limit is reached, Segment queues additional computations until one of the five finishes computing. | -| Edit Concurrency | 2 concurrent audiences or computed traits | You can edit two concurrent audiences or computed traits at a time. Once the limit is reached, Segment queues and locks additional computations until one of the two finishes computing. | -| Batch Compute Concurrency Limit | 10 (default) per space | The number of batch computations that can run concurrently per space. When this limit is reached, Segment delays subsequent computations until current computations finish. | -| Compute Throughput | 10000 computations per second | Computations include any Track or Identify call that triggers an audience or computed trait re-computation. Once the limit is reached, Segment may slow audience processing. | -| Events Lookback History | 3 years | The period of time for which Segment stores audience and computed traits computation events. | -| Real-time to batch destination sync frequency | 2-3 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | -| Event History | `1970-01-01` | Events with a timestamp less than `1970-01-01` aren't always ingested, which could impact audience backfills with event timestamps prior to this date. | -| Engage Data Ingest | 1x the data ingested into Connections | The amount of data transferred into the Compute Engine. | -| Audience Frequency Update | 1 per 8 hours | Audiences that require time windows (batch audiences), [funnels](/docs/engage/audiences/#funnel-audiences), [dynamic properties](/docs/engage/audiences/#dynamic-property-references), or [account-level membership](/docs/engage/audiences/#account-level-audiences) are processed on chronological schedules. The default schedule is once every eight hours; however, this can be delayed if the "Batch Compute Concurrency Limit" is reached. Unless otherwise agreed upon, the audiences will compute at the limit set forth. | -| Event Properties (Computed Traits) | 10,000 | For Computed Traits that exceed this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values. | +| name | limit | Details | +| --------------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Compute Concurrency | 5 new concurrent audiences or computed traits | Segment computes five new audiences or computed traits at a time. Once the limit is reached, Segment queues additional computations until one of the five finishes computing. | +| Edit Concurrency | 2 concurrent audiences or computed traits | You can edit two concurrent audiences or computed traits at a time. Once the limit is reached, Segment queues and locks additional computations until one of the two finishes computing. | +| Batch Compute Concurrency Limit | 10 (default) per space | The number of batch computations that can run concurrently per space. When this limit is reached, Segment delays subsequent computations until current computations finish. | +| Compute Throughput | 10000 computations per second | Computations include any Track or Identify call that triggers an audience or computed trait re-computation. Once the limit is reached, Segment may slow audience processing. | +| Real-time to batch destination sync frequency | 2-3 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | +| Event History | `1970-01-01` | Segment may not ingest events with a timestamp earlier than `1970-01-01`, which can impact audience backfills for older events. Segment stores data indefinitely, but ingestion depends on event timestamps.

While Segment stores all events, event conditions typically evaluate data from the past three years by default. Your plan or configuration may allow a longer time window. | +| Engage Data Ingest | 1x the data ingested into Connections | The amount of data transferred into the Compute Engine. | +| Audience Frequency Update | 1 per 8 hours | Audiences that require time windows (batch audiences), [funnels](/docs/engage/audiences/#funnel-audiences), [dynamic properties](/docs/engage/audiences/#dynamic-property-references), or [account-level membership](/docs/engage/audiences/#account-level-audiences) are processed on chronological schedules. The default schedule is once every eight hours; however, this can be delayed if the "Batch Compute Concurrency Limit" is reached. Unless otherwise agreed upon, the audiences will compute at the limit set forth. | +| Event Properties (Computed Traits) | 10,000 | For Computed Traits that exceed this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values. | ## SQL Traits