diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index a5973d1377..7f7a928abe 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-03-13 +# destination categories last updated 2025-03-20 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 015b3dfab9..20961f93f2 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-03-13 +# destination data last updated 2025-03-20 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -106045,7 +106045,7 @@ items: hidden: false defaultTrigger: type = "identify" fields: - - id: oiXto9Ga3x9ZjmnVCKQg3m + - id: msLYhTzSiH9frKQypk39j7 sortOrder: 0 fieldKey: contactKey label: Contact Key @@ -106071,7 +106071,7 @@ items: hidden: false defaultTrigger: null fields: - - id: aLcHAWVXuPT2m6EqqaooGd + - id: ghafCSxbPa4YnJ5wvTtnNk sortOrder: 0 fieldKey: eventDefinitionKey label: Event Definition Key @@ -106085,7 +106085,7 @@ items: choices: null dynamic: false allowNull: false - - id: ffKH5kYww6CaBjNgx2Ex8A + - id: bLxSxMj6A2SPBvN4KoTEmC sortOrder: 1 fieldKey: contactKey label: Contact Key @@ -106099,7 +106099,7 @@ items: choices: null dynamic: false allowNull: false - - id: xbtTMVBmWPAPHDLJEhhsfp + - id: 4A7PLdbdqJHtHKGGXVHqgd sortOrder: 2 fieldKey: data label: Event Data @@ -106126,7 +106126,7 @@ items: hidden: false defaultTrigger: null fields: - - id: 2LSnRWWZaiixnT3yp9LhVD + - id: kNSQHQwm64spyAdqch3dhQ sortOrder: 0 fieldKey: key label: Data Extension Key @@ -106141,7 +106141,7 @@ items: choices: null dynamic: false allowNull: false - - id: 2BhFd19YmCQGWdNETqaKD1 + - id: wdoPweXHmqyrx7xJXxnU3v sortOrder: 1 fieldKey: id label: Data Extension ID @@ -106156,7 +106156,7 @@ items: choices: null dynamic: false allowNull: false - - id: nKnByfL5D8dYQcKksvGUBu + - id: udmLA78M6Yhx2QJ9iDbPaT sortOrder: 2 fieldKey: keys label: Data Extension Primary Keys @@ -106173,7 +106173,7 @@ items: choices: null dynamic: false allowNull: false - - id: kAhwakJxjyE5zdpAZZ7kK4 + - id: 2cai2ov124dX1pQcQeapf6 sortOrder: 3 fieldKey: values label: Data Extension Fields @@ -106191,7 +106191,7 @@ items: choices: null dynamic: false allowNull: false - - id: 3aYydqS6fdHTQGYLEiNXAZ + - id: v6UonL8VGaCbs3qem3t7j6 sortOrder: 4 fieldKey: enable_batching label: Batch data to SFMC @@ -106214,7 +106214,7 @@ items: hidden: false defaultTrigger: type = "identify" fields: - - id: guKt4p6edmrdqcmAdg1LCR + - id: 7ZbXQMmYsVmpV4RA81Lu2H sortOrder: 0 fieldKey: key label: Data Extension Key @@ -106229,7 +106229,7 @@ items: choices: null dynamic: false allowNull: false - - id: 4ZtgpCXSPTFM146NRzarz9 + - id: 389oJtq61F6G5RcHpDY7wu sortOrder: 1 fieldKey: id label: Data Extension ID @@ -106244,7 +106244,7 @@ items: choices: null dynamic: false allowNull: false - - id: 9nWih4PiFHHY4M9qykDRan + - id: i6tbKHJz5djGNVqNQd9S7L sortOrder: 2 fieldKey: keys label: Data Extension Primary Keys @@ -106264,7 +106264,7 @@ items: choices: null dynamic: false allowNull: false - - id: kxvdgvYwVJcYvw9XETmQv1 + - id: 2MJqS6xURYZe7osGZoFr3V sortOrder: 3 fieldKey: values label: Contact Fields @@ -106281,7 +106281,7 @@ items: choices: null dynamic: false allowNull: false - - id: 5sHM4HiXoYJFF4QWrHq6Mh + - id: rP3kMRC9L1vhPE7kb6suZR sortOrder: 4 fieldKey: enable_batching label: Batch data to SFMC diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index bb309eead9..de179b1305 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-03-13 +# destination data last updated 2025-03-20 items: - id: 54521fd925e721e32a72eee1 display_name: Pardot diff --git a/src/_data/catalog/regional-supported.yml b/src/_data/catalog/regional-supported.yml index 68e87896aa..fdfd71f47f 100644 --- a/src/_data/catalog/regional-supported.yml +++ b/src/_data/catalog/regional-supported.yml @@ -287,7 +287,7 @@ sources: - us - id: UYaQxaZO3a display_name: Editable Profile Source Metadata - hidden: true + hidden: false slug: editable-profile-source-metadata url: connections/sources/catalog/cloud-apps/editable-profile-source-metadata regions: diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index 9137f4e0d8..2ffc32c9a1 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-03-13 +# source categories last updated 2025-03-20 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 6d917df5be..0d230d6bdd 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-03-13 +# sources last updated 2025-03-20 items: - id: 8HWbgPTt3k display_name: .NET diff --git a/src/_includes/content/destination-maintenance.md b/src/_includes/content/destination-maintenance.md index c60d47ccfe..7915b56e86 100644 --- a/src/_includes/content/destination-maintenance.md +++ b/src/_includes/content/destination-maintenance.md @@ -11,5 +11,5 @@ {% endif %}

{{page.title | replace: 'Destination', ''}} (Classic) is in Maintenance mode

-

The {{name}} (Classic) Destination has entered maintenance mode. Future updates are limited to security updates and bug fixes. {{blurb}}

+

The {{name}} Destination has entered maintenance mode. Future updates are limited to security updates and bug fixes. {{blurb}}

\ No newline at end of file diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md index e36d513d90..cc64ab5474 100644 --- a/src/connections/delivery-overview.md +++ b/src/connections/delivery-overview.md @@ -4,13 +4,6 @@ title: Delivery Overview Delivery Overview is a visual observability tool designed to help Segment users diagnose event delivery issues for any cloud-streaming destination receiving events from cloud-streaming sources. -> info "Delivery Overview for RETL destinations and Engage Audience Syncs currently in development" -> This means that Segment is actively developing Delivery Overview features for RETL destinations and Engage Audience syncs. Some functionality may change before Delivery Overview for these integrations becomes generally available. -> -> Delivery Overview is generally available for streaming connections (cloud-streaming sources and cloud-streaming destinations) and in public beta for storage destinations. Some metrics specific to storage destinations, like selective syncs, failed row counts, and total rows seen, are not yet available. -> All users of Delivery Overview have access to the Event Delivery tab, and can configure delivery alerts for their destinations. - - ## Key features Delivery Overview has three core features: @@ -63,6 +56,21 @@ The following image shows a storage destination with 23 partially successful syn ![A screenshot of the Delivery Overview tab for a Storage destination, with the Failed to sync step selected and a table of partially successful syncs.](images/delivery-overview-storage-destinations.png) +#### Destinations connected to Engage Destinations + +> info "Delivery Overview for Engage Destinations is in Public Beta" +> During the Public Beta, you can filter your pipeline view by audience. + +Destinations connected to an Audience have the following steps in the pipeline view: +- **Events from audience***: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership. +- **Filtered at source**: Events discarded by Protocols: either by the [schema settings](/docs/protocols/enforce/schema-configuration/) or [Tracking Plans](/docs/protocols/tracking-plan/create/). +- **Filtered at destination**: If any events aren’t eligible to be sent (for example, due to destination filters, insert function logic, and so on), Segment displays them at this step. +- **Events pending retry**: A step that reveals the number of events that are awaiting retry. Unlike the other steps, you cannot click into this step to view the breakdown table. +- **Failed delivery**: Events that Segment _attempted_ to deliver to your destination, but that ultimately _failed_ to be delivered. Failed delivery might indicate an issue with the destination, like invalid credentials, rate limits, or other error statuses received during delivery. +- **Successful delivery**: Events that Segment successfully delivered to your destination. You’ll see these events in your downstream integrations. + +*_The "Events from audience" step is currently only available for Linked Audiences._ + ### Breakdown table The breakdown table provides you with greater detail about the selected events. diff --git a/src/connections/destinations/catalog/hubspot/index.md b/src/connections/destinations/catalog/hubspot/index.md index 69d8579b80..532d0f20c1 100644 --- a/src/connections/destinations/catalog/hubspot/index.md +++ b/src/connections/destinations/catalog/hubspot/index.md @@ -223,7 +223,7 @@ When using any of Segment's server-side sources, a connector infers `traits.life ### Loading Forms SDK -Segment gives you the option to load the [HubSpot Forms SDK](https://developers.hubspot.com/docs/methods/forms/advanced_form_options){:target="_blank"} alongside their tracking library. Enable the **Load Forms SDK** setting when you your HubSpot integration. +Segment gives you the option to load the [HubSpot Forms SDK](https://developers.hubspot.com/docs/methods/forms/advanced_form_options){:target="_blank"} alongside HubSpot's tracking library. Enable the **Load Forms SDK** setting for your HubSpot integration. > info "" > The Forms SDK expects to load synchronously but analytics.js loads asynchronously. To interact with the API, run code inside an [analytics.ready](/docs/connections/sources/catalog/libraries/website/javascript/#ready) callback. For example: diff --git a/src/connections/sources/catalog/cloud-apps/hubspot-profiles/index.md b/src/connections/sources/catalog/cloud-apps/hubspot-profiles/index.md new file mode 100644 index 0000000000..7cf41a897e --- /dev/null +++ b/src/connections/sources/catalog/cloud-apps/hubspot-profiles/index.md @@ -0,0 +1,99 @@ +--- +title: Connect HubSpot to Segment Profiles +plan: unify +--- + +This guide explains how to set up HubSpot as a source and connect it to Segment Profiles. + +Once configured, this integration lets you send HubSpot data directly to Segment Profiles, eliminating the need for a data warehouse and enabling faster data synchronization and profile enrichment. + +> info "Public Beta" +> The HubSpot/Segment Profiles integration is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. + +## Prerequisites + +Before you begin, make sure that you have the following: + +- A Segment workspace with [Unify](/docs/unify/) enabled and [Identity Resolution](/docs/unify/identity-resolution/) configured. +- Administrator access to your HubSpot account. + +## Integration steps + +Follow the steps in this section to connect HubSpot to Segment Profiles. + +### 1. Add HubSpot as a source + +To start syncing HubSpot data, first add HubSpot as a source to your workspace. + +1. From your Segment workspace, go to **Connections > Catalog** and search for **HubSpot**. +2. Select **HubSpot**, then click **Add Source**. +3. Enter a name for your HubSpot source and add an optional label. +4. Log in to HubSpot and choose the account you want to sync data from. +5. Once you've authenticated, return to Segment and click **Next**. +6. Verify the **Schema name**, then click **Next**. +7. In the **Selective Sync** settings: + - Set a start date for the initial sync (or leave it blank for a full historical sync). + - Keep the default sync frequency (every three hours) or adjust it by contacting friends@segment.com. + - Choose the collections to sync. + +After adding the source, go to **Settings > Basic settings** and toggle **Enable source**. The first sync begins immediately. + +### 2. Add a Segment Profiles destination + +Next, add a Segment Profiles destination. + +1. From your HubSpot source, go to the **Models** tab and click **Add destination**. +2. Select **Segment Profiles**, then click **Add destination**. +3. Enter a name for the destination, then click **Create destination**. + +### 3. Create a data model + +A data model defines how HubSpot data maps to Segment Profiles. + +1. In the HubSpot source, go to the **Models** tab and click **Create Model**. +2. Select the collections and columns to sync. +3. Preview the data in real time and validate the schema. +4. Name the model and click **Next** to save it. + +### 4. Map HubSpot data to Segment Profiles + +Now, configure mappings to determine how HubSpot data updates Segment Profiles. + +1. In the **Models** tab of your HubSpot source, click **Add mapping**. +2. Segment redirects you to the Segment Profiles destination. Click **Add mapping**. +3. Select your data model and define the mapping rules: + - Choose the Profile Space to update. + - Map HubSpot fields to Segment Profile fields. + - **You must map either the User ID, Anonymous ID, or Group ID field.** +4. Test the mapping with real HubSpot data. +5. Save the configuration. + + +### 5. Enable destination mapping and finish setup + +Finish the setup process by enabling the destination mapping. + +1. From the **Overview** tab of the Segment Profiles destination, toggle **Mapping Status** to **Enabled**. +2. Return to your HubSpot source and verify that **Settings > Basic settings** is enabled. + +Once complete, HubSpot data syncs to Segment Profiles automatically. + +## Data synchronization + +After connecting HubSpot to the Segment Profiles destination, the integration begins syncing data: + +- New or updated records in HubSpot get sent to Segment Profiles based on your mapping configuration. +- The first sync includes historical data based on your selected start date. +- Future syncs run at the default interval of every three hours. + +If you change the start date after the first sync, Segment doesn’t retroactively sync data unless you manually trigger a full sync. Changes to synced collections apply only to future syncs. Data you previously synced from removed collections stays in your workspace. + +## Best practices + +Keep the following in mind when working with the HubSpot/Segment Profiles integration: + +- Start with a small dataset to validate mappings before expanding to all HubSpot objects. +- Regularly review your mappings to make sure they reflect any schema changes in HubSpot or Segment Profiles. +- Monitor both your HubSpot source and Segment Profiles destination for errors and data discrepancies. + +Each data model supports mapping from one HubSpot collection at a time. For complex use cases requiring multiple collections, create separate data models and mappings. diff --git a/src/connections/sources/catalog/libraries/server/pixel-tracking-api/index.md b/src/connections/sources/catalog/libraries/server/pixel-tracking-api/index.md index 198a166ca9..66a2b1ba51 100644 --- a/src/connections/sources/catalog/libraries/server/pixel-tracking-api/index.md +++ b/src/connections/sources/catalog/libraries/server/pixel-tracking-api/index.md @@ -55,6 +55,12 @@ Each endpoint *always* responds with a `200 `, even if an error occur eyJ3cml0ZUtleSI6ICJZT1VSX1dSSVRFX0tFWSIsICJ1c2VySWQiOiAiMDI1cGlrYWNodTAyNSIsICJldmVudCI6ICJFbWFpbCBPcGVuZWQiLCAicHJvcGVydGllcyI6IHsgICAic3ViamVjdCI6ICJUaGUgRWxlY3RyaWMgRGFpbHkiLCAgICJlbWFpbCI6ICJwZWVrQXRNZUBlbWFpbC5wb2tlIiB9fQ ``` +##### If you choose not to encode your payload, send it like this instead: + +``` +https://api.segment.io/v1/pixel/track?userId=user_123&event=Email Opened&properties.subject=The Electric Daily&properties.email=jane.kim@example.com&writeKey= +``` + ##### Add an image tag to your email newsletter with `src` pointing to a Pixel API route: ```html diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md index 4fb33cd1e3..800bf35006 100644 --- a/src/engage/audiences/index.md +++ b/src/engage/audiences/index.md @@ -202,6 +202,78 @@ Engage then processes your realtime Audience or Trait edits. While the edit task > warning "" > You can't edit an audience to include anonymous users. If you need to include anonymous profiles, recreate the audience with the appropriate conditions +## Monitor the health of your Audience syncs + +Use Segment's [Delivery Overview](#delivery-overview) and [Alerting](#alerting) features to monitor the health of your Audience syncs and get notifications when event volume spikes or drops. + +### Delivery Overview + +Delivery Overview is a visual observability tool designed to help Segment users diagnose event delivery issues for any event-streaming destination receiving events from Engage Audiences. + +Delivery Overview has three core features: +- [Pipeline view](/docs/connections/delivery-overview/#pipeline-view): A visual overview of each step your data takes during the delivery process - from when your audiences outputs events to when events are successfully delivered to your connected destination. +- [Breakdown table](/docs/connections/delivery-overview/#breakdown-table): If you select a step in the pipeline view, you can see more details about the events that were processed at each pipeline step. +- [Discard table](/docs/connections/delivery-overview/#discard-table): If you select an event in a breakdown table, you can see more details about the events that failed or were filtered out of your process. You can also inspect samples of the discarded events. + +For more information about the breakdown and discard tables, see the [Delivery Overview](/docs/connections/delivery-overview/) documentation. + +To view Delivery Overview for an Audience: +1. From your Segment workspace's home page, navigate to **Engage > Audiences**. +2. Find an Audience, click the **(...)** menu, and select Delivery Overview. +3. On the Delivery Overview page, select the Audience dropdown to filter by a specific Audience, select the Date range dropdown to filter by a specific time period, or use the Show metrics toggle to view your metrics as percentages. + +#### Steps in the pipeline view + +By default, Segment displays Delivery Overview information for all Audiences connected to your destination. You can filter your Delivery Overview pipeline view by an individual Audience for more granular data. + +You can also further refine the data displayed on the pipeline view using the time picker and the metric toggle, located under the destination header. With the time picker, you can specify a time period (last 10 minutes, 1 hour, 24 hours, 7 days, 2 weeks, or a custom date range over the last two weeks) for which you’d like to see data. With the metric toggle, you can switch between seeing metrics represented as percentages (for example, _85% of events_ or _a 133% increase in events_) or as counts (_13 events_ or _an increase of 145 events_.) Delivery Overview shows percentages by default. + +> info "Linked Audiences have additional filtering functionality" +> Linked Audiences users can filter the Delivery Overview event pipeline by [Linked Audience events](/docs/engage/audiences/linked-audiences/#step-2c-define-how-and-when-to-trigger-an-event-to-your-destination). For more information, see the [Linked Audiences](/docs/engage/audiences/linked-audiences/#delivery-overview-for-linked-audiences) documentation. + +Audiences have the following steps in the pipeline view: +- **Events that Segment created for your activation***: The number of events for each compute depends on the changes detected in your audience membership. +- **Filtered at source**: Events discarded by Protocols: either by the [schema settings](/docs/protocols/enforce/schema-configuration/) or [Tracking Plans](/docs/protocols/tracking-plan/create/). +- **Filtered at destination**: If any events aren’t eligible to be sent (for example, due to destination filters, insert function logic, and so on), Segment displays them at this step. +- **Events pending retry**: A step that reveals the number of events that are awaiting retry. Unlike the other steps, you cannot click into this step to view the breakdown table. +- **Failed delivery**: Events that Segment _attempted_ to deliver to your destination, but that ultimately _failed_ to be delivered. Failed delivery might indicate an issue with the destination, like invalid credentials, rate limits, or other error statuses received during delivery. +- **Successful delivery**: Events that Segment successfully delivered to your destination. You’ll see these events in your downstream integrations. + +*_The "Events from audience" step is currently only available for Linked Audiences._ + +### Alerting + +Create alerts related to the performance and throughput of Audience syncs and receive in-app, email, and Slack notifications when event volume fluctuations occur. + +> info "Generate a Slack webhook to receive Slack notifications" +> To receive an alert in a Slack channel, you must first create a Slack webhook. For more information about Slack webhooks, see Slack's [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks){:target="_blank”} documentation. + +To access Audience alerting, navigate to **Engage > Audiences**, select an Audience, and click the Alerts tab. + +On the Alerts tab, you can create new alerts and view all active alerts for this connection. You can only edit or delete the alerts that you create, unless you have the [Workspace Owner role](/docs/segment-app/iam/roles/). + +#### Activation event health spikes or drops + +You can create an Activation event health spikes or drops alert that notifies you when events sent from your audience to a downstream destination have failures to a destination above a certain threshold. For example, if you set a change percentage of 4% and your destination received 100 events from your Audience over the first 24 hours, Segment would notify you the following day if your destination ingested fewer than 96 or more than 104 events. + +To create an Activation event health spikes or drops alert: +1. From your Segment workspace's home page, navigate to **Engage > Audiences**. +2. Select the Audience you want to create an alert for, select the Alerts tab, and click **Create alert**. +3. On the Create alert sidesheet, select the destination for which you'd like to monitor event health. +4. Enter a percentage threshold to trigger activation event health notifications. +5. Select one or more of the following alert channels: + - **Email**: Select this to receive notifications at the provided email address. + - **Slack**: Select this to send alerts to one or more channels in your workspace. + - **In-app**: Select this to receive notifications in the Segment app. To view your notifications, select the bell next to your user icon in the Segment app. +6. Click **Save**. + +To make changes to an Activation event health spikes or drops alert, select the icon in the Actions column for the alert and click **Edit**. + +To delete a Activation event health spikes or drops alert, select the icon in the Actions column for the alert and click **Delete**. + +> info "Deleting alerts created by other users requires Workspace Owner role" +> All users can delete alerts that they created, but only those with [Workspace Owner role](/docs/segment-app/iam/roles/) can delete alerts created by other users. + ## Access your Audiences using the Profiles API You can access your Audiences using the Profile API by querying the `/traits` endpoint. For example, you can query for `high_value_user` property with the following `GET` request: diff --git a/src/engage/audiences/linked-audiences.md b/src/engage/audiences/linked-audiences.md index 15a9ce941e..7f13873dd8 100644 --- a/src/engage/audiences/linked-audiences.md +++ b/src/engage/audiences/linked-audiences.md @@ -242,12 +242,20 @@ With your Linked Audience activated, follow these steps to monitor your activati ### Delivery Overview for Linked Audiences -Delivery Overview shows you four steps in your data activation pipeline: - -- **Events from Audience**: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership. -- **Filtered at Destination**: The activation pipeline is rich with features that let you control which events make it to the destination. If any events aren't eligible to be sent (for example, due to destination filters, insert function logic, and so on), Segment will show them in Filtered at Destination. -- **Failed Delivery**: Events that Segment attempted but failed to deliver to your destination. Failed Delivery indicates an issue with the destination, like invalid credentials, rate limits, or other error statuses received during delivery. -- **Successful Delivery**: Events that Segment successfully delivered to your destination. You'll see these events in your downstream integration. +In addition to the standard Audience observability provided by [Delivery Overview](/docs/engage/audiences/#delivery-overview), Linked Audiences can filter Delivery Overview's pipeline view by [Linked Audience events](/docs/engage/audiences/linked-audiences/#step-2c-define-how-and-when-to-trigger-an-event-to-your-destination). + +To filter by events: +1. From your Segment workspace's home page, navigate to **Engage > Audiences**. +2. Find an Audience, click the **(...)** menu, and select Delivery Overview. +3. On the Delivery Overview page, select the Linked audience event dropdown to filter by a specific event. + +Linked Audiences have the following steps in Delivery Overview's pipeline view: +- **Events from audience**: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership. +- **Filtered at source**: Events discarded by Protocols: either by the [schema settings](/docs/protocols/enforce/schema-configuration/) or [Tracking Plans](/docs/protocols/tracking-plan/create/). +- **Filtered at destination**: If any events aren’t eligible to be sent (for example, due to destination filters, insert function logic, and so on), Segment displays them at this step. +- **Events pending retry**: A step that reveals the number of events that are awaiting retry. Unlike the other steps, you cannot click into this step to view the breakdown table. +- **Failed delivery**: Events that Segment _attempted_ to deliver to your destination, but that ultimately _failed_ to be delivered. Failed delivery might indicate an issue with the destination, like invalid credentials, rate limits, or other error statuses received during delivery. +- **Successful delivery**: Events that Segment successfully delivered to your destination. You’ll see these events in your downstream integrations. ## Maintaining Linked Audiences diff --git a/src/engage/journeys/event-triggered-journeys-steps.md b/src/engage/journeys/event-triggered-journeys-steps.md index 18f66b8a07..3adcc1b914 100644 --- a/src/engage/journeys/event-triggered-journeys-steps.md +++ b/src/engage/journeys/event-triggered-journeys-steps.md @@ -8,7 +8,7 @@ plan: engage-foundations Steps are the building blocks of a journey. This page explains the **Hold Until** and **Send to Destination** steps, which enable precise control over journey progression and data delivery. > info "Public Beta" -> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Event-Triggered Journeys is not currently HIPAA eligible. +> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. ## Hold Until: smart pauses in journeys diff --git a/src/engage/journeys/event-triggered-journeys.md b/src/engage/journeys/event-triggered-journeys.md index 0816956535..94d1e5f579 100644 --- a/src/engage/journeys/event-triggered-journeys.md +++ b/src/engage/journeys/event-triggered-journeys.md @@ -10,7 +10,7 @@ Unlike traditional audience-based journeys that rely on pre-defined user segment On this page, you'll learn how to create an event-triggered journey, configure entry conditions, and work with published event-triggered journeys. > info "Public Beta" -> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Event-Triggered Journeys is not currently HIPAA eligible. +> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. ## Overview diff --git a/src/engage/journeys/journey-context.md b/src/engage/journeys/journey-context.md index a6d8410e5a..e0443833db 100644 --- a/src/engage/journeys/journey-context.md +++ b/src/engage/journeys/journey-context.md @@ -8,7 +8,7 @@ plan: engage-foundations This page explains Journey context, which can help you dynamically adapt each journey to individual user interactions, creating highly relevant, real-time workflows. > info "Public Beta" -> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Event-Triggered Journeys is not currently HIPAA eligible. +> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. ## Overview diff --git a/src/privacy/data-retention-policy.md b/src/privacy/data-retention-policy.md index 4c4d0b4c9d..55b789bec7 100644 --- a/src/privacy/data-retention-policy.md +++ b/src/privacy/data-retention-policy.md @@ -35,6 +35,9 @@ The default data retention period for each of the data types is as follows: | **Team** | 365 days | Not applicable | 90 days | 365 days | Not applicable | | **Free** | 180 days | Not applicable | 60 days | 180 days | Not applicable | +> info "" +> Segment calculates your data retention period starting from the date Segment ingests an event, not from the date an event originally occurred. + Through the self-serve Data Retention configuration in your workspace, you can configure a custom data retention period through the [Workspace Default Archive Retention Period](#workspace-default-archive-retention-period) setting. Segment recommends keeping your data for at least 30 days to enable [replays](/docs/guides/what-is-replay/) of your data. diff --git a/src/unify/data-graph/linked-events.md b/src/unify/data-graph/linked-events.md index 193f538a40..407b8b303f 100644 --- a/src/unify/data-graph/linked-events.md +++ b/src/unify/data-graph/linked-events.md @@ -30,9 +30,6 @@ To use Linked Events, you'll need the following: 2. Access to Unify in your workspace. 3. Access to the actions-based destination you'll be using with Linked Events so that you can validate your data. -> info "" -> Segment stores and processes all data in the United States. - > info "" > Profiles Sync isn't required for Linked Events.