Skip to content

Commit 0de8bdb

Browse files
committed
Builder updates
1 parent bd6cf54 commit 0de8bdb

9 files changed

+20
-26
lines changed

src/engage/audiences/account-audiences.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,10 @@ A single account-level audience can incorporate any combination of the following
3939
- Account-level custom traits (set through a [group](/docs/connections/spec/group) call)
4040

4141

42-
To access account-level audience conditions, select Accounts in the dropdown.
42+
To access account-level audience conditions:
43+
1. Navigate to **Engage > Audiences**, click **Create**, then select **Audience**.
44+
2. From the **Select Type** screen, select **Accounts**.
45+
3. From the **Configure** screen, select **Accounts** in the dropdown.
4346

4447
![Use this control to access account level audience conditions](/docs/engage/images/new-audience-type.png)
4548

src/engage/audiences/computed-traits.md

Lines changed: 7 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -62,13 +62,12 @@ User-level examples:
6262
- Favorite Blog Post
6363
- Top Purchase Category
6464

65-
![A most frequent product-viewed trait](../images/1525836239527.png)
66-
6765
Account-level examples:
6866
- Most frequent product viewed
6967
- Most active user
7068

71-
![A most frequent order-completed trait](../images/1542073415630.png)
69+
![A most frequent product-viewed trait](../images/1525836239527.png)
70+
7271

7372
### First
7473

@@ -92,13 +91,12 @@ User-level examples:
9291
- Last seen at
9392
- Last utm parameter
9493

95-
![The last event-seen trait builder](../images/1525836818177.png)
96-
9794
Account-level examples:
9895
- Last unsubscribe timestamp
9996
- Last user active
10097

101-
![An account-level last page-viewed trait](../images/1542073887657.png)
98+
![The last event-seen trait builder](../images/1525836818177.png)
99+
102100

103101
### Unique List
104102

@@ -120,13 +118,12 @@ User-level examples:
120118
- Unique products viewed count
121119
- Unique categories count
122120

123-
![The unique list count builder](../images/1525837374378.png)
124-
125121
Account-level examples:
126122
- Unique products viewed
127123
- Unique visitors count
128124

129-
![An account-level unique list trait](../images/1542074153487.png)
125+
![The unique list count builder](../images/1525837374378.png)
126+
130127

131128
## Conditions
132129

@@ -171,7 +168,7 @@ To edit a real-time Trait, follow these steps:
171168
1. In your Engage Space, select the **Computed Traits** tab.
172169
2. Select the realtime Trait you want to edit.
173170
3. Select the **Builder** tab and make your edits.
174-
4. Select **Save Computed Trait** to confirm your edits.
171+
4. Preview the results, then select **Save Computed Trait** to confirm your edits.
175172

176173
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. Use the Overview page to view Trait details and refresh user counts for real-time computations.
177174

src/engage/audiences/index.md

Lines changed: 9 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,6 @@ You can also build Audiences based on custom traits. These traits can be collect
3434

3535
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.
3636

37-
![Creating an Audience from a computed trait based on the user's number of Twitter followers](/docs/engage/images/audience_builder_computed.png)
3837

3938
### Funnel Audiences
4039

@@ -54,7 +53,7 @@ If you have a B2B business, you might want to build an Audience of accounts. You
5453

5554
See [Account-level Audiences](/docs/engage/audiences/account-audiences) for more information.
5655

57-
![Building an Audience of accounts where no user viewed their dashboard in the last 30 days](/docs/engage/images/1542075123519.png)
56+
5857

5958
## Send Audiences to Destinations
6059
With the help of Sources and Destinations in Segment's catalog, you can create and send Audiences and computed traits to third-party services.
@@ -125,26 +124,22 @@ Engage displays the following compute statuses for Audiences and Traits.
125124

126125

127126
## Real-time compute compared to batch
128-
127+
129128
Real-time Compute allows you to update traits and Audiences as Segment receives new events. Real-time Compute unlocks exciting use cases:
130129

131130
- **Intra-Session App Personalization:** change your app experience with personalized onboarding, product recommendations, and faster funnels based on a user entering and exiting an audience.
132131
- **Instant Messaging:** Trigger messages in email, live chat, and push notifications instantly, to deliver immediate experiences across channels.
133132
- **Operational Workflows:** Supercharge your sales and support teams by responding to customer needs faster, based on the latest understanding of a user.
134133

135-
To create a new Audience:
136-
137-
1. Go to your **Computed Traits** or **Audiences** tab in Engage and select **New**.
138-
139-
2. Create your computed trait or Audience.
140-
141-
A lightning bolt indicates that the computation updates in real-time.
134+
To create a new Audience or Trait:
142135

143-
![A screenshot of the Audience preview in the Audience Builder](/docs/engage/images/1538693443980_image.png)
136+
1. Go to your **Computed Traits** or **Audiences** tab in Engage and select **Create**.
144137

145-
3. To preview your Audience, select **Select Destinations**, then select **Review & Create**.
138+
2. Configure and preview your Audience or Trait.
139+
- A lightning bolt next to `Realtime Enabled` indicates that the computation updates in real-time.
140+
- 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.
146141

147-
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.
142+
3. Select destinations to connect, then review and create your Audience or Trait.
148143

149144
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.
150145

@@ -161,7 +156,7 @@ To edit a realtime Trait or Audience, follow these steps:
161156
1. In your Engage Space, select the **Computed Traits** or **Audiences** tab.
162157
2. Select the realtime Audience or Trait you want to edit.
163158
3. Select the **Builder** tab and make your edits.
164-
4. Select **Save Audience** to confirm your edits.
159+
4. Preview the results, then select **Save audience** to confirm your edits.
165160

166161
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. Use the Overview page to view Audience details and refresh user counts for real-time computations.
167162

src/engage/audiences/sql-traits.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -225,7 +225,6 @@ Segment supports returning only 25 columns. [Contact Segment](https://segment.co
225225

226226
### I'm seeing a duplicate `user_id` error.
227227

228-
![An example of a duplicate user_id error](../images/troubleshoot3.png)
229228

230229
Each query row must correspond to a unique user. Segment displays this error if it detects multiple rows with the same `user_id`. Use a `distinct` or `group by` statement to ensure that each row has a unique user_id.
231230

-108 KB
Loading
-48 KB
Loading
-139 KB
Loading
-80.4 KB
Loading
-59.5 KB
Loading

0 commit comments

Comments
 (0)