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/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/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/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/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