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
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.
17
17
18
-

18
+

19
19
20
20
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.
21
21
@@ -27,33 +27,33 @@ You can also build audiences based on custom traits. These traits can be collect
27
27
28
28
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.
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
35
35
36
-

36
+

37
37
38
38
### Dynamic Property References
39
39
40
40
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.
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`.
47
47
48
48
See [Account-level Audiences](/docs/personas/audiences/account-audiences) for more information.
49
49
50
-

50
+

51
51
52
52
## Connecting your Audience to a Destination
53
53
54
54
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.
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.
59
59
@@ -74,20 +74,20 @@ Realtime Compute allows you to update traits and audiences as Segment receives n
74
74
To create a new audience:
75
75
76
76
1. Go to your **Computed Traits** or **Audiences** tab in Personas and click **New**.
3. To preview your audience, click **Select Destinations**, then click **Review & Create**.
87
87
88
88
By default, Segment queries all historical data (or "[replays](/docs/guides/what-is-replay/)" 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.
@@ -121,7 +121,7 @@ You can read the [full Profile API docs](/docs/personas/profile-api/) to learn m
121
121
## Downloading your Audience as a CSV
122
122
123
123
You can download a copy of your audience by visiting the the audience overview page.
124
-

124
+

125
125
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:
126
126
127
127
-**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]({{site.url}}/docs/personas/files/audience_csv_format_a.csv)
0 commit comments