Merge pull request #4004 from segmentio/Compute-status-bar

ROW 3.0 updates

Author: rchinn1

src/engage/audiences/account-audiences.md

@@ -39,7 +39,10 @@ A single account-level audience can incorporate any combination of the following
 - Account-level custom traits (set through a [group](/docs/connections/spec/group) call)
 
 
-To access account-level audience conditions, select Accounts in the dropdown.
+To access account-level audience conditions:
+1. Navigate to **Engage > Audiences**, and click **Create**.
+2. Select **Accounts** from the **Select Type** screen.
+3. From the **Configure** screen, select **Accounts** in the dropdown.
 
 ![Use this control to access account level audience conditions](/docs/engage/images/new-audience-type.png)
 

src/engage/audiences/computed-traits.md

@@ -66,13 +66,12 @@ User-level examples:
 - Favorite Blog Post
 - Top Purchase Category
 
-![A most frequent product-viewed trait](../images/1525836239527.png)
-
 Account-level examples:
 - Most frequent product viewed
 - Most active user
 
-![A most frequent order-completed trait](../images/1542073415630.png)
+![A most frequent product-viewed trait](../images/1525836239527.png)
+
 
 ### First
 
@@ -96,13 +95,12 @@ User-level examples:
 - Last seen at
 - Last utm parameter
 
-![The last event-seen trait builder](../images/1525836818177.png)
-
 Account-level examples:
 - Last unsubscribe timestamp
 - Last user active
 
-![An account-level last page-viewed trait](../images/1542073887657.png)
+![The last event-seen trait builder](../images/1525836818177.png)
+
 
 ### Unique List
 
@@ -124,13 +122,12 @@ User-level examples:
 - Unique products viewed count
 - Unique categories count
 
-![The unique list count builder](../images/1525837374378.png)
-
 Account-level examples:
 - Unique products viewed
 - Unique visitors count
 
-![An account-level unique list trait](../images/1542074153487.png)
+![The unique list count builder](../images/1525837374378.png)
+
 
 ## Conditions
 
@@ -162,6 +159,10 @@ Learn more about [Computed trait generated events here](/docs/engage/using-engag
 
 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
+
+After you create a computed trait, use the Overview page to view the current [compute status](/docs/engage/audiences#compute-statuses), number of users with the trait, connected destinations, and more. For real-time traits, click **Refresh Trait** to update the current number of users with the trait.  
+
 ## Editing Realtime Traits
 
 Engage 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.
@@ -171,9 +172,10 @@ To edit a real-time Trait, follow these steps:
 1. In your Engage Space, select the **Computed Traits** tab.
 2. Select the realtime Trait you want to edit.
 3. Select the **Builder** tab and make your edits.
-4. Select **Save Computed Trait** to confirm your edits.
+4. Preview the results, then select **Save Computed Trait** to confirm your edits.
+
+Engage then processes your Trait edits. While the edit task runs, the trait remains locked and you can't make further changes. Once Engage incorporates your changes, you'll be able to access your updated Trait. 
 
-Engage then processes your Trait edits. While the edit task runs, the trait remains locked and you can't make further changes. Once Engage has finished incorporating your changes, you'll be able to access your updated Trait.
 
 > warning ""
 > It is not possible to edit a trait to convert it from real-time to batch, or vice-versa. If the computation type needs to be changed, you will need to recreate the trait with the appropiate conditions.

src/engage/audiences/index.md

@@ -34,7 +34,6 @@ You can also build Audiences based on custom traits. These traits can be collect
 
 You can also use computed traits in an Audience definition. For example, you can create a `total_revenue` computed trait and use it to generate an audience of `big_spender` customers that exceed a certain threshold.
 
-![Creating an Audience from a computed trait based on the user's number of Twitter followers](/docs/engage/images/audience_builder_computed.png)
 
 ### Funnel Audiences
 
@@ -54,7 +53,7 @@ If you have a B2B business, you might want to build an Audience of accounts. You
 
 See [Account-level Audiences](/docs/engage/audiences/account-audiences) for more information.
 
-![Building an Audience of accounts where no user viewed their dashboard in the last 30 days](/docs/engage/images/1542075123519.png)
+
 
 ## Send Audiences to Destinations
 With the help of Sources and Destinations in Segment's catalog, you can create and send Audiences and computed traits to third-party services.
@@ -88,6 +87,45 @@ Because a number of factors (like system load, backfills, or user bases) determi
 
 As a result, **Segment recommends waiting at least 24 hours for an Audience to finish computing** before you resume working with the Audience.
 
+From the Overview page, you can view Audience details including the current compute status and a progress bar for real-time and batch Audiences. Engage updates the progress bar and status for real-time computations approximately every 10 minutes.
+
+> info ""
+> Engage only displays the progress bar and status updates when you create a new Audience or Trait.
+
+> warning ""
+> Engage syncs the Overview page for an individual audience more frequently than the Engage Audiences page (**Engage > Audiences**). As a result, you might see temporary discrepancies in Audience details, such as user counts, between these two pages.
+
+### Refresh real-time Audiences and Traits
+
+For real-time computations, you can click **Refresh Audience** or **Refresh Trait** to update user counts, status, and compute progress.
+
+### Compute statuses
+
+Engage displays the following compute statuses for Audiences and Traits.
+
+#### Real-time computations
+
+| Computation status        | Description                           |
+|---------------------------|---------------------------------------|
+| Preparing                 | Engage is preparing the computation.  |
+| Computing                 | Engage is computing the Audience or Trait.           |
+| Live                      | The Audience or Trait is live. Users will enter in real-time as they meet entry criteria.        |
+| Disabled                  | The Audience or Trait is disabled.                   |
+| Failed                    | The computation was cancelled or failed to compute. Please contact [Segment support](https://segment.com/help/contact/){:target="_blank"}.            |
+
+
+#### Batch computations
+
+| Computation status        | Description                           |
+|---------------------------|---------------------------------------|
+| Preparing                 | Engage is preparing the computation.  |
+| Computing                 | Engage is computing the Audience or Trait.  |
+| Live                      | The Audience or Trait is up-to-date, based on the most recent sync cadence. When you edit a batch Audience or Trait, Engage displays the compute status as `Live` and incorporates your edits in the next scheduled sync.                 |
+| Not Computing             | Engage displays this status when there are no destinations connected or `Compute without connected destinations` isn't selected.         |
+| Disabled                  | The Audience or Trait is disabled.    |
+| Failed                    | The computation was cancelled or failed to compute. Please contact [Segment support](https://segment.com/help/contact/){:target="_blank"}.    |
+
+
 ## 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:
@@ -96,22 +134,17 @@ Real-time Compute allows you to update traits and Audiences as Segment receives
 - **Instant Messaging:** Trigger messages in email, live chat, and push notifications instantly, to deliver immediate experiences across channels.
 - **Operational Workflows:** Supercharge your sales and support teams by responding to customer needs faster, based on the latest understanding of a user.
 
-To create a new Audience:
-
-1. Go to your **Computed Traits** or **Audiences** tab in Engage and select **New**.
-
-2. Create your computed trait or Audience.
-
-   A lightning bolt indicates that the computation updates in real-time.
-
-   ![A screenshot of the Audience preview in the Audience Builder](/docs/engage/images/1538693443980_image.png)
+To create a new Audience or Trait:
 
-3. To preview your Audience, select **Select Destinations**, then select **Review & Create**.
+1. Go to your **Computed Traits** or **Audiences** tab in Engage and select **Create**.
 
-   By default, Segment queries all historical data to set the current value of the computed trait and Audience. You can uncheck **Historical Backfill** to compute values for the Audience or trait without using this data. With this disabled, the trait or Audience only uses the data that arrives after you created it.
+2. Configure and preview your Audience or Trait.
+- A lightning bolt next to `Realtime Enabled` indicates that the computation updates in real-time.
+- By default, Segment queries all historical data to set the current value of the computed trait and Audience. Backfill computes historical data up to the point of audience creation. You can uncheck **Include Historical Data** to compute values for the Audience or trait without historical data. With backfill disabled, the trait or Audience only uses the data that arrives after you create it.
 
-Use the Audience Explorer to see users or accounts that enter the Audience. Segment displays the Audience as computing until at least one user or account enters.
+3. Select destinations to connect, then review and create your Audience or Trait.
 
+While Engage is computing, use the Audience Explorer to see users or accounts that enter your Audience. Engage displays the Audience as computing in the Explorer until at least one user or account enters.
 
 > warning ""
 > [Facebook Custom Audiences](/docs/connections/destinations/catalog/personas-facebook-custom-audiences/), [Marketo Lists](/docs/connections/destinations/catalog/marketo-static-lists/), and [Adwords Remarking Lists](/docs/connections/destinations/catalog/adwords-remarketing-lists) impose rate limits on how quickly Segment can update an Audience. Segment syncs at the highest frequency allowed by the tool, which is between one and six hours.
@@ -125,9 +158,9 @@ To edit a realtime Trait or Audience, follow these steps:
 1. In your Engage Space, select the **Computed Traits** or **Audiences** tab.
 2. Select the realtime Audience or Trait you want to edit.
 3. Select the **Builder** tab and make your edits.
-4. Select **Save Audience** to confirm your edits.
+4. Preview the results, then select **Create Audience** to confirm your edits.
 
-Engage then processes your realtime Audience or Trait edits. While the edit task runs, the audience remains locked and you can't make further changes. Once Engage has finished incorporating your changes, you'll be able to access your updated Audience or Trait.
+Engage then processes your realtime Audience or Trait edits. While the edit task runs, the audience remains locked and you can't make further changes. Once Engage incorporates your changes, you'll be able to access your updated Audience or Trait. 
 
 > warning ""
 > If your audience includes historical data (Historical Backfill is enabled), editing an audience creates a new backfill task. The backfill task, and therefore the edit task, take longer to process if the audience is connected to a destination with rate limits. Rate-limited destinations dictate how fast Engage can backfill. View a list of [rate-limited destinations](/docs/engage/using-engage-data/#rate-limits-on-engage-event-destinations).