You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/engage/audiences/index.md
+56-43Lines changed: 56 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,98 +7,111 @@ engage: true
7
7
8
8
9
9
10
-
Audiences allow you to define cohorts of users or accounts based on their event behavior and traits that Segment then keeps up-to-date over time. Audiences can be built from your core **tracking events**, **traits**, or **computed traits**. These audiences can then be synced to hundreds of destinations and are available using the [Profile API](/docs/personas/profile-api).
10
+
Audiences let you group users or accounts based on event behavior and traits that Segment tracks.
11
+
12
+
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).
11
13
12
14
## Building an Audience
13
15
14
-
When building an audience you can use existing events, traits, computed traits or audiences.
16
+
You can build an Audience from existing events, traits, computed traits, or other Audiences.
17
19
18
20
### Events
19
21
20
-
You can build an audience from any of the events that are connected to Personas. This includes any [track](/docs/connections/spec/track), [page](/docs/connections/spec/page), or [screen](/docs/connections/spec/screen) calls. You can use the `property` button to refine the audience on specific event properties as well. Select `and not who` to indicate users that have not performed an event. For example, you might want to look at all users that have viewed a product above a certain price point, but not completed the order.
22
+
You can build an Audience from any events that are connected to Personas, including [Track](/docs/connections/spec/track), [Page](/docs/connections/spec/page), and [Screen](/docs/connections/spec/screen) calls. You can use the `property` button to refine the audience on specific event properties, as well. Select `and not who` to indicate users that have not performed an event. For example, you might want to look at all users that have viewed a product above a certain price point but not completed the order.
21
23
22
-
24
+
23
25
24
-
You can also specify two different types of time-windows, `within` and `in between`. Within lets you specify an event that occurred in the last `x` number of days. In-between lets you specify events that occurred over a rolling time-window in the past. A common use case is to look at all customers that were active 30 to 90 days ago, but have not completed an action in the last 30 days.
26
+
You can also specify two different types of time-windows, `within` and `in between`. The `within` property lets you specify an event that occurred in the last `x` number of days, while `in between` lets you specify events that occurred over a rolling timewindow in the past. A common use case is to look at all customers that were active 30 to 90 days ago, but have not completed an action in the last 30 days.
25
27
26
28
### Custom Traits
27
29
28
-
You can also build audiences based on custom traits. These traits can be collected from your apps when a user completes a form, or signs up, using an [identify](/docs/connections/spec/identify) call. You can also check out the Personas user explorer to see examples of these traits.
30
+
You can also build Audiences based on custom traits. These traits can be collected from your apps when a user completes a form or signs up using an [Identify](/docs/connections/spec/identify) call. You can view these traits in the Personas user explorer, as well.
29
31
30
32
### Computed Traits
31
33
32
-
You can also use computed traits in an audience definition. For example, if you have created a `total_revenue` computed trait, you can use this to generate an audience of `big_spender` customers that exceed a certain threshold.
34
+
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.
35
37
36
38
### Funnel Audiences
37
39
38
-
Funnel audiences allow you to specify strict ordering between two events. This might be the case if you want an event to happen or not happen, within a specific time window, as in the example below
40
+
Funnel audiences allow you to specify strict ordering between two events. This might be the case if you want an event to happen or not happen within a specific time window, as in the following example:
39
41
40
-
42
+
41
43
42
-
### Dynamic Property References
44
+
### Dynamic property references
43
45
44
-
Dynamic Property references give you more flexibility over funnel audiences. Instead of specifying a constant value in both events, like product_id = '123' for both Product Viewed and Order Completed events, you can specify that a child event references an event property of a parent event. You can also compare an event property to a trait variable.
46
+
Dynamic Property references give you more flexibility over funnel audiences. Instead of specifying a constant value in both events, like `product_id = 123` for both Product Viewed and Order Completed events, you can specify that a child event references an event property of a parent event. You can also compare an event property to a trait variable.
47
49
48
-
### Account-Level audiences
50
+
### Account-level audiences
49
51
50
-
If you are a B2B business, you might want to build an audience of accounts. You can use both account-level traits that you've sent through the [group](/docs/connections/spec/group) call, or user-level traits and events. For example, you might want to re-engage a list of at-risk accounts defined as companies which are on a business tier plan and where none of the users in that account have logged in recently. When incorporating user-level events or traits, you can specify `None of the users`, `Any users`, or `All users`.
52
+
If you have a B2B business, you might want to build an Audience of accounts. You can use both account-level traits that you've sent through the [Group](/docs/connections/spec/group) call, or user-level traits and events. For example, you might want to re-engage a list of at-risk accounts defined as companies which are on a business tier plan and where none of the users in that account have logged in recently. When incorporating user-level events or traits, you can specify `None of the users`, `Any users`, or `All users`.
51
53
52
54
See [Account-level Audiences](/docs/personas/audiences/account-audiences) for more information.
53
55
54
-
56
+
57
+
58
+
## Send Audiences to Destinations
59
+
With the help of Sources and Destinations in Segment's catalog, you can create and send Personas Audiences and computed traits to third-party services.
60
+
61
+
Segment's Connections pipeline first collects and sends events from your Source to your Destination. Built on top of Connections, Personas then uses the same Source events to let you create Audiences and computed traits within Segment. You can then send the Audience or computed trait you've built to your Destination(s).
55
62
56
-
## Connecting your Audience to a Destination
63
+
> info ""
64
+
> Because Personas only sends Audiences and computed traits to Destinations, it doesn't replace a standard event pipeline. Connect a Source directly to a Destination if you want the Destination to receive all events that Segment gathers.
65
+
66
+
### Connect your Audience to a Destination
57
67
58
68
> warning "Audience Keys"
59
69
> Avoid using the same Audience key twice, even if you've deleted the original Audience.
60
70
61
-
Once you have previewed your audience, you can choose to connect a destination, or simply keep the audience in Segment and download a csv. If you already have destinations set up in Segment, you can import the configuration from one of your existing sources to Personas. Note that you can only connect one destination configuration per destination type.
71
+
Once you've previewed your Audience, you can choose to connect it to a Destination or keep the Audience in Segment and export it as a CSV file download.
72
+
73
+
If you already have Destinations set up in Segment, you can import the configuration from one of your existing sources to Personas. You can only connect one Destination configuration per Destination type.
64
76
65
-
When you create an audience, Segment starts syncing your audience to the destinations you selected. Audiences are either sent to destinations as a boolean user-property or a user-list, depending on what the destination supports. Read more about [which destinations are supported](/docs/personas/using-personas-data/#compatible-personas-destinations) in the Personas documentation.
77
+
When you create an Audience, Segment starts syncing your Audience to the Destinations you selected. Audiences are either sent to Destinations as a boolean user-property or a user-list, depending on what the Destination supports. Read more about [supported Destinations](/docs/personas/using-personas-data/#compatible-personas-destinations) in the Personas documentation.
66
78
67
-
For account-level audiences, you can 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, we 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.
79
+
For account-level audiences, you can 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.
68
80
81
+
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.
69
82
70
83
> info ""
71
-
> When you connect a new destination to an existing audience, Personas will backfill historical data for that audience to the new destination.
84
+
> When you connect a new Destination to an existing Audience, Personas will backfill historical data for that Audience to the new Destination.
72
85
73
-
## Real-time Compute vs. Batch
86
+
## Real-time compute compared to batch
74
87
75
-
Real-time Compute allows you to update traits and audiences as Segment receives new events. Real-time Compute unlocks exciting use cases:
88
+
Real-time Compute allows you to update traits and Audiences as Segment receives new events. Real-time Compute unlocks exciting use cases:
76
89
77
90
-**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.
78
91
-**Instant Messaging:** Trigger messages in email, livechat, and push notifications instantly, to deliver immediate experiences across channels.
79
-
-**Operational Workflows:** Supercharge your sales and support teams by responding to customer needs faster, based on the latest understanding of a user
92
+
-**Operational Workflows:** Supercharge your sales and support teams by responding to customer needs faster, based on the latest understanding of a user.
80
93
81
-
To create a new audience:
94
+
To create a new Audience:
82
95
83
-
1. Go to your **Computed Traits** or **Audiences** tab in Personas and click**New**.
92
105
93
-
3. To preview your audience, click**Select Destinations**, then click**Review & Create**.
106
+
3. To preview your Audience, select**Select Destinations**, then select**Review & Create**.
94
107
95
-
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.
108
+
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.
98
111
99
112
100
113
> warning ""
101
-
> [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)have rate limits on how quickly we can update an audience. We sync at the highest frequency allowed by the tool, which is between 1 hour and 6 hours.
114
+
> [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.
102
115
103
116
### Editing Realtime Audiences and Traits
104
117
@@ -116,15 +129,15 @@ Personas then processes your realtime Audience or Trait edits. While the edit ta
116
129
> warning ""
117
130
> 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 Personas can backfill. View a list of [rate-limited destinations](/docs/personas/using-personas-data/#rate-limits-on-personas-event-destinations).
118
131
119
-
## Accessing your Audiences using the Profiles API
132
+
## Access your Audiences using the Profiles API
120
133
121
-
You can access your audiences using the Profile API by querying the `/traits` endpoint. For example, if you can query for the `high_value_user` with the following GET request:
134
+
You can access your Audiences using the Profile API by querying the `/traits` endpoint. For example, you can query for `high_value_user`property with the following `GET` request:
You can read the [full Profile API docs](/docs/personas/profile-api/) to learn more.
143
156
144
-
## Downloading your Audience as a CSV
157
+
## Download your Audience as a CSV file
145
158
146
-
You can download a copy of your audience by visiting the the audience overview page.
147
-
148
-
Audience CSVs are generated on demand. Before you can download the CSV, you will need to generate it. There are three different options for formatting:
159
+
You can download a copy of your Audience by visiting the the Audience overview page.
160
+
161
+
Before you can download the CSV, you will need to generate it. There are three different options for formatting:
149
162
150
163
-**Unformatted:** Contains two columns. The first contains the user or account key and the second is a JSON object containing the external IDs. Generating this CSV is faster than the formatted option below. [Download example unformatted CSV](/docs/personas/files/audience_csv_format_a.csv)
151
164
-**Formatted (with indexed columns for ID types with multiple values):** Contains the same first two columns as the unformatted CSV. Additional columns are added for each distinct external ID type. When a given external ID type has more than one value, for example a user with three email addresses, _additional columns with indexed headers are added_, (`email`, `email_1`, `email_2`). [Download example formatted CSV with indexed columns](/docs/personas/files/audience_csv_format_b.csv)
@@ -155,7 +168,7 @@ Audience CSVs are generated on demand. Before you can download the CSV, you will
<td width="45%">Generating a CSV can take a substantial amount of time for large audiences (around 30 seconds for a formatted CSV with 1 million rows). For CSVs that are expected to take over 20 seconds, the Segment app displays an estimated generation time. After clicking Generate, it is recommended that you leave the modal open while the CSV is created.
171
+
<td width="45%">Generating a CSV can take a substantial amount of time for large audiences (around 30 seconds for a formatted CSV with 1 million rows). For CSVs that are expected to take over 20 seconds, Segment displays an estimated generation time. After you generate the CSV file, leave the modal window open while Segment creates the file.
159
172
(If the audience recalculates between when you click Generate and when you download the file, you might want to regenerate the file. The CSV is a snapshot from when you clicked Generate, and could be outdated.)</td>
0 commit comments