From 1259204abeeca89f3bd91b0575d49d906aeceafc Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 13 May 2025 15:14:07 -0400 Subject: [PATCH 1/8] resync backfill notice --- src/engage/audiences/index.md | 3 +++ src/unify/Traits/computed-traits.md | 3 +++ 2 files changed, 6 insertions(+) diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md index 3f104f92f6..119d9549ca 100644 --- a/src/engage/audiences/index.md +++ b/src/engage/audiences/index.md @@ -166,6 +166,9 @@ Engage displays the following compute statuses for Audiences and Traits. #### Batch computations +> warning "Disabled batch computations don't automatically backfill data when re-enabled" +> If you disable and re-enable a batch computation, Segment does not automatically create a backfill. Any data Segment recieves during the disabled period is not sent to your Destination after you re-enable your batch computation. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. + | Computation status | Description | |---------------------------|---------------------------------------| | Preparing | Engage is preparing the computation. | diff --git a/src/unify/Traits/computed-traits.md b/src/unify/Traits/computed-traits.md index e5b97ca007..d1e303ff17 100644 --- a/src/unify/Traits/computed-traits.md +++ b/src/unify/Traits/computed-traits.md @@ -12,6 +12,9 @@ redirect_from: Computed Traits allow you to quickly create user or account-level calculations that Segment keeps up-to-date over time. These can be computations like the `total_num_orders` a customer has completed, the `lifetime_revenue` of a customer, the `most_frequent_user` to determine which user is most active in an account, or the `unique_visitors_count` to assess how many visitors from a single domain. These computations are based on your events and event properties that you are sending through Segment on the [page](/docs/connections/spec/page/) and [track](/docs/connections/spec/track) calls. +> warning "Disabled batch computations don't automatically backfill data when re-enabled" +> If you disable and re-enable a batch computation, Segment does not automatically create a backfill. Any data Segment recieves during the disabled period is not sent to your Destination after you re-enable your batch computation. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. + {% include content/trait-types.md %} ## Types of Computed Traits From 49b00aba2123b5bcec94b20508030f19c1f7988b Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 13 May 2025 15:19:22 -0400 Subject: [PATCH 2/8] [netlify-build] --- src/unify/Traits/computed-traits.md | 1 - 1 file changed, 1 deletion(-) diff --git a/src/unify/Traits/computed-traits.md b/src/unify/Traits/computed-traits.md index d1e303ff17..27b4bd731e 100644 --- a/src/unify/Traits/computed-traits.md +++ b/src/unify/Traits/computed-traits.md @@ -9,7 +9,6 @@ redirect_from: > info "" > Beginning August 18, 2023, new Unify Plus users can access Computed Traits in Unify. - Computed Traits allow you to quickly create user or account-level calculations that Segment keeps up-to-date over time. These can be computations like the `total_num_orders` a customer has completed, the `lifetime_revenue` of a customer, the `most_frequent_user` to determine which user is most active in an account, or the `unique_visitors_count` to assess how many visitors from a single domain. These computations are based on your events and event properties that you are sending through Segment on the [page](/docs/connections/spec/page/) and [track](/docs/connections/spec/track) calls. > warning "Disabled batch computations don't automatically backfill data when re-enabled" From 15fd796bfa520c0df04be01cab16ac00426f6b18 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 13 May 2025 17:05:26 -0400 Subject: [PATCH 3/8] fix [netlify-build] --- src/engage/audiences/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md index 119d9549ca..73ce4001c9 100644 --- a/src/engage/audiences/index.md +++ b/src/engage/audiences/index.md @@ -169,6 +169,8 @@ Engage displays the following compute statuses for Audiences and Traits. > warning "Disabled batch computations don't automatically backfill data when re-enabled" > If you disable and re-enable a batch computation, Segment does not automatically create a backfill. Any data Segment recieves during the disabled period is not sent to your Destination after you re-enable your batch computation. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. + + | Computation status | Description | |---------------------------|---------------------------------------| | Preparing | Engage is preparing the computation. | From e80ed6b692801f9b8793fd919f20b944de268eb0 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 13 May 2025 17:38:53 -0400 Subject: [PATCH 4/8] updated language [netlify-build] --- src/unify/Traits/computed-traits.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/unify/Traits/computed-traits.md b/src/unify/Traits/computed-traits.md index 27b4bd731e..c25d16eeca 100644 --- a/src/unify/Traits/computed-traits.md +++ b/src/unify/Traits/computed-traits.md @@ -11,8 +11,8 @@ redirect_from: Computed Traits allow you to quickly create user or account-level calculations that Segment keeps up-to-date over time. These can be computations like the `total_num_orders` a customer has completed, the `lifetime_revenue` of a customer, the `most_frequent_user` to determine which user is most active in an account, or the `unique_visitors_count` to assess how many visitors from a single domain. These computations are based on your events and event properties that you are sending through Segment on the [page](/docs/connections/spec/page/) and [track](/docs/connections/spec/track) calls. -> warning "Disabled batch computations don't automatically backfill data when re-enabled" -> If you disable and re-enable a batch computation, Segment does not automatically create a backfill. Any data Segment recieves during the disabled period is not sent to your Destination after you re-enable your batch computation. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. +> warning "Disabled computed traits don't automatically backfill data when re-enabled" +> If you disable and re-enable a computed trait, Segment does not automatically create a backfill. Any data Segment recieves during the disabled period is not sent to your Destination after you re-enable your computed trait. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. {% include content/trait-types.md %} From 1f311b5788928017031d960b405f99901dc6a2b9 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 3 Jun 2025 16:58:51 -0400 Subject: [PATCH 5/8] [netlify-build] --- src/engage/audiences/index.md | 4 +++- src/unify/Traits/computed-traits.md | 6 ++++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md index 73ce4001c9..3158d5d23a 100644 --- a/src/engage/audiences/index.md +++ b/src/engage/audiences/index.md @@ -166,8 +166,10 @@ Engage displays the following compute statuses for Audiences and Traits. #### Batch computations -> warning "Disabled batch computations don't automatically backfill data when re-enabled" +> warning "Starting June 2nd, 2025, disabled batch computations don't automatically backfill data when re-enabled" > If you disable and re-enable a batch computation, Segment does not automatically create a backfill. Any data Segment recieves during the disabled period is not sent to your Destination after you re-enable your batch computation. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. +> +> Segment is releasing this feature on a phased rollout plan, and expects this to be available to all customers by July 18, 2025. diff --git a/src/unify/Traits/computed-traits.md b/src/unify/Traits/computed-traits.md index c25d16eeca..356b686ccb 100644 --- a/src/unify/Traits/computed-traits.md +++ b/src/unify/Traits/computed-traits.md @@ -11,8 +11,10 @@ redirect_from: Computed Traits allow you to quickly create user or account-level calculations that Segment keeps up-to-date over time. These can be computations like the `total_num_orders` a customer has completed, the `lifetime_revenue` of a customer, the `most_frequent_user` to determine which user is most active in an account, or the `unique_visitors_count` to assess how many visitors from a single domain. These computations are based on your events and event properties that you are sending through Segment on the [page](/docs/connections/spec/page/) and [track](/docs/connections/spec/track) calls. -> warning "Disabled computed traits don't automatically backfill data when re-enabled" -> If you disable and re-enable a computed trait, Segment does not automatically create a backfill. Any data Segment recieves during the disabled period is not sent to your Destination after you re-enable your computed trait. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. +> warning "Starting June 2nd, 2025, disabled computed traits don't automatically backfill data when re-enabled" +> If you disable and re-enable a computed trait, Segment does not automatically create a backfill. Any data Segment receives during the disabled period is not sent to your Destination after you re-enable your trait. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. +> +> Segment is releasing this feature on a phased rollout plan, and expects this to be available to all customers by July 18, 2025. {% include content/trait-types.md %} From df64d3daa457d92981ee547c85bdb14b54f4d72e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 3 Jun 2025 17:03:27 -0400 Subject: [PATCH 6/8] speling [netlify-build] --- src/engage/audiences/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md index 3158d5d23a..baf021f796 100644 --- a/src/engage/audiences/index.md +++ b/src/engage/audiences/index.md @@ -167,7 +167,7 @@ Engage displays the following compute statuses for Audiences and Traits. #### Batch computations > warning "Starting June 2nd, 2025, disabled batch computations don't automatically backfill data when re-enabled" -> If you disable and re-enable a batch computation, Segment does not automatically create a backfill. Any data Segment recieves during the disabled period is not sent to your Destination after you re-enable your batch computation. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. +> If you disable and re-enable a batch computation, Segment does not automatically create a backfill. Any data Segment receives during the disabled period is not sent to your Destination after you re-enable your batch computation. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. > > Segment is releasing this feature on a phased rollout plan, and expects this to be available to all customers by July 18, 2025. From a1cb5676fb586c4ca7ead5777ef328f783fc3e94 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 5 Jun 2025 09:13:46 -0400 Subject: [PATCH 7/8] lang update requested by PM --- src/unify/Traits/computed-traits.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/unify/Traits/computed-traits.md b/src/unify/Traits/computed-traits.md index 356b686ccb..e41fcc1005 100644 --- a/src/unify/Traits/computed-traits.md +++ b/src/unify/Traits/computed-traits.md @@ -11,8 +11,8 @@ redirect_from: Computed Traits allow you to quickly create user or account-level calculations that Segment keeps up-to-date over time. These can be computations like the `total_num_orders` a customer has completed, the `lifetime_revenue` of a customer, the `most_frequent_user` to determine which user is most active in an account, or the `unique_visitors_count` to assess how many visitors from a single domain. These computations are based on your events and event properties that you are sending through Segment on the [page](/docs/connections/spec/page/) and [track](/docs/connections/spec/track) calls. -> warning "Starting June 2nd, 2025, disabled computed traits don't automatically backfill data when re-enabled" -> If you disable and re-enable a computed trait, Segment does not automatically create a backfill. Any data Segment receives during the disabled period is not sent to your Destination after you re-enable your trait. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. +> warning "Starting June 2nd, 2025, disabled batch computed traits don't automatically backfill data when re-enabled" +> If you disable and re-enable a batch computed trait, Segment does not automatically create a backfill. Any data Segment receives during the disabled period is not sent to your Destination after you re-enable your trait. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. > > Segment is releasing this feature on a phased rollout plan, and expects this to be available to all customers by July 18, 2025. From 903362b1ab1d7b4442a1444aface5eed66578fd5 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 5 Jun 2025 10:16:40 -0400 Subject: [PATCH 8/8] style guide updates --- src/unify/Traits/computed-traits.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/unify/Traits/computed-traits.md b/src/unify/Traits/computed-traits.md index e41fcc1005..c8d9865429 100644 --- a/src/unify/Traits/computed-traits.md +++ b/src/unify/Traits/computed-traits.md @@ -9,7 +9,7 @@ redirect_from: > info "" > Beginning August 18, 2023, new Unify Plus users can access Computed Traits in Unify. -Computed Traits allow you to quickly create user or account-level calculations that Segment keeps up-to-date over time. These can be computations like the `total_num_orders` a customer has completed, the `lifetime_revenue` of a customer, the `most_frequent_user` to determine which user is most active in an account, or the `unique_visitors_count` to assess how many visitors from a single domain. These computations are based on your events and event properties that you are sending through Segment on the [page](/docs/connections/spec/page/) and [track](/docs/connections/spec/track) calls. +Computed Traits allow you to quickly create user or account-level calculations that Segment keeps up-to-date over time. These can be computations like the `total_num_orders` a customer has completed, the `lifetime_revenue` of a customer, the `most_frequent_user` to determine which user is most active in an account, or the `unique_visitors_count` to assess how many visitors from a single domain. These computations are based on your events and event properties that you are sending through Segment on the [Page](/docs/connections/spec/page/) and [Track](/docs/connections/spec/track) calls. > warning "Starting June 2nd, 2025, disabled batch computed traits don't automatically backfill data when re-enabled" > If you disable and re-enable a batch computed trait, Segment does not automatically create a backfill. Any data Segment receives during the disabled period is not sent to your Destination after you re-enable your trait. If you want to backfill your data, you must reach out to [Segment Support](mailto:friends@segment.com) to request a resync. @@ -164,13 +164,13 @@ The following operators are available. ## Connecting your Computed Trait to a Destination -Segment sends user-level computed Traits to destinations using the [Identify call](/docs/connections/spec/identify/) for user traits, or using the [Track call](/docs/connections/spec/track/) for event properties. Segment includes the trait value and property in the identify and track calls. +Segment sends user-level computed Traits to destinations using the [Identify call](/docs/connections/spec/identify/) for user traits, or using the [Track call](/docs/connections/spec/track/) for event properties. Segment includes the trait value and property in the Identify and Track calls. -For example, the name of a computed trait is added to the user profile as a trait, and the trait's value is set to the value of the computed trait. Segment sends an identify or track call when the trait is computed, depending on the destination configuration. If a computed trait counts the number of times a user visits your pricing page, and the user visits your pricing page five times, Segment sends an identify call with the property `pricing_page_visits: 5`. +For example, the name of a computed trait is added to the user profile as a trait, and the trait's value is set to the value of the computed trait. Segment sends an Identify or Track call when the trait is computed, depending on the destination configuration. If a computed trait counts the number of times a user visits your pricing page, and the user visits your pricing page five times, Segment sends an Identify call with the property `pricing_page_visits: 5`. Learn more about [Computed trait generated events here](/docs/engage/using-engage-data/#computed-trait-generated-events). The trait name corresponds to the snake cased name that you see in the trait settings, for example `most_viewed_page_category`. See the [list of Engage-compatible destinations](/docs/engage/using-engage-data/#compatible-engage-destinations) -For account-level computed traits, you have the option to send either a [group](/docs/connections/spec/group/) call and/or [identify](/docs/connections/spec/identify/) call. Group calls will send one event per account, whereas identify calls will send an identify call for each user in the account. This means that even if a user hasn't performed an event, Segment will still set the account-level computed trait on that user. Because most marketing tools are still based at the user level, it is often important to map this account-level trait onto each user within an account. See [Account-level Audiences](/docs/engage/audiences/account-audiences) for more information. +For account-level computed traits, you have the option to send either a [Group](/docs/connections/spec/group/) call and/or [Identify](/docs/connections/spec/identify/) call. Group calls will send one event per account, whereas Identify calls will send an Identify call for each user in the account. This means that even if a user hasn't performed an event, Segment will still set the account-level computed trait on that user. Because most marketing tools are still based at the user level, it is often important to map this account-level trait onto each user within an account. See [Account-level Audiences](/docs/engage/audiences/account-audiences) for more information. ## View compute status