Merge pull request #3447 from segmentio/3428-content

Add Compute Times Note #3428

Author: pwseg

src/engage/audiences/index.md

@@ -83,6 +83,12 @@ Because most marketing tools are still based at the user level, it is often impo
 > info ""
 > When you connect a new Destination to an existing Audience, Personas will backfill historical data for that Audience to the new Destination.
 
+## Understanding compute times
+
+Because a number of factors (like system load, backfills, or user bases) determine the complexity of an Audience, some compute times take longer than others.
+
+As a result, **Segment recommends waiting at least 24 hours for an Audience to finish computing** before you resume working with the Audience.
+
 ## Real-time compute compared to batch
 
 Real-time Compute allows you to update traits and Audiences as Segment receives new events. Real-time Compute unlocks exciting use cases:

src/engage/profiles/computed-traits.md

@@ -158,14 +158,20 @@ Learn more about [Computed trait generated events here](/docs/personas/using-per
 
 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/personas/audiences/account-audiences) for more information.
 
-## Editing Realtime Traits
+## Understanding compute times
 
-Personas supports the editing of realtime Traits, which allows you to make nuanced changes to existing Traits in situations where cloning or building from scratch may not suit your use case.
+Because a number of factors (like system load, backfills, or user bases) determine the complexity of a Computed Trait, some compute times take longer than others.
 
-To edit a realtime Trait, follow these steps:
+As a result, **Segment recommends waiting at least 24 hours for a Trait to finish computing** before you resume working with the Trait.
+
+## Editing Real-time Traits
+
+Personas supports the editing of real-time Traits, which allows you to make nuanced changes to existing Traits in situations where cloning or building from scratch may not suit your use case.
+
+To edit a real-time Trait, follow these steps:
 
 1. In your Personas Space, select the **Computed Traits** tab.
-2. Select the realtime Trait you want to edit.
+2. Select the real-time Trait you want to edit.
 3. Select the **Builder** tab and make your edits.
 4. Select **Save Computed Trait** to confirm your edits.
 

src/personas/audiences/index.md

@@ -4,7 +4,7 @@ title: Personas Audiences Overview
 
 Audiences let you group users or accounts based on event behavior and traits that Segment tracks.
 
-You can build Audiences from core **tracking events**, **traits**, and **computed traits**. You can then sync Audiences to hundreds of [Destinations](/docs/connections/destinations/) or access them with the [Profile API](/docs/personas/profile-api).
+You can build Audiences from core **tracking events**, **traits**, and [**computed traits**](/docs/personas/computed-traits/). You can then sync Audiences to hundreds of [Destinations](/docs/connections/destinations/) or access them with the [Profile API](/docs/personas/profile-api).
 
 ## Building an Audience
 
@@ -80,6 +80,12 @@ Because most marketing tools are still based at the user level, it is often impo
 > info ""
 > When you connect a new Destination to an existing Audience, Personas will backfill historical data for that Audience to the new Destination.
 
+## Understanding compute times
+
+Because a number of factors (like system load, backfills, or user bases) determine the complexity of an Audience, some compute times take longer than others.
+
+As a result, **Segment recommends waiting at least 24 hours for an Audience to finish computing** before you resume working with the Audience.
+
 ## Real-time compute compared to batch
 
 Real-time Compute allows you to update traits and Audiences as Segment receives new events. Real-time Compute unlocks exciting use cases:

src/personas/computed-traits.md

@@ -4,7 +4,9 @@ title: Personas Computed Traits
 
 
 
-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 send through Segment on the [Page](/docs/connections/spec/page/) and [Track](/docs/connections/spec/track) calls.
 
 ## Types of Computed Traits
 
@@ -156,14 +158,20 @@ Learn more about [Computed trait generated events here](/docs/personas/using-per
 
 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/personas/audiences/account-audiences) for more information.
 
-## Editing Realtime Traits
+## Understanding compute times
+
+Because a number of factors (like system load, backfills, or user bases) determine the complexity of a Computed Trait, some compute times take longer than others.
+
+As a result, **Segment recommends waiting at least 24 hours for a Trait to finish computing** before you resume working with the Trait.
+
+## Editing Real-time Traits
 
-Personas supports the editing of realtime Traits, which allows you to make nuanced changes to existing Traits in situations where cloning or building from scratch may not suit your use case.
+Personas supports the editing of real-time Traits, which allows you to make nuanced changes to existing Traits in situations where cloning or building from scratch may not suit your use case.
 
-To edit a realtime Trait, follow these steps:
+To edit a real-time Trait, follow these steps:
 
 1. In your Personas Space, select the **Computed Traits** tab.
-2. Select the realtime Trait you want to edit.
+2. Select the real-time Trait you want to edit.
 3. Select the **Builder** tab and make your edits.
 4. Select **Save Computed Trait** to confirm your edits.