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/personas/audiences/index.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,11 +84,19 @@ Because most marketing tools are still based at the user level, it is often impo
84
84
85
85
Personas provides dynamic ETAs for Audiences that you sync to downstream tools. Once an Audience that you've created finishes computing, Personas will display a progress bar in a Destination's tile that indicates how much time remains before the sync completes.
86
86
87
-
To view this sync information, navigate to **Personas > Audiences > Overview**. Personas displays the latest sync information in the **Destinations** section of the Audience Overview tab. In the Destinations section, you'll also find information about any sync issues, including failed syncs.
87
+
To view this sync information, navigate to **Personas > Audiences > Overview**. Personas displays the latest sync information in the **Destinations** section of the Audience Overview tab.
88
88
89
89
> info "Real-time and batch syncs"
90
90
> Personas doesn't display sync ETAs for real-time Audiences, because events for real-time Audiences sync to Destinations on a continual basis. Sync ETAs within Personas correspond only to non-real-time Audiences.
91
91
92
+
#### Sync event generation
93
+
94
+
You can use Personas event generation to view information about any issues that occur **before** Segment syncs an Audience to a downstream Destination. Event generation shows a sync history that displays common errors, like broken permissions, terms of service issues, and failed syncs.
95
+
96
+
To access event generation, select the sync Destination's tile in the Audiences Overview tab, then select the **Syncs** tab from the overlay pane.
97
+
98
+
For information on any **delivery** issues that might occur when Segment attempts to sync your Audience with a Destination, access the Destination's [event delivery tool](/docs/connections/event-delivery/).
99
+
92
100
## Understanding compute times
93
101
94
102
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.
Copy file name to clipboardExpand all lines: src/personas/faqs.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,8 @@ Lookback windows are precise down to the hour, so a 90-day lookback window will
68
68
69
69
The trait and audience will automatically update going forward as historical events exceed the lookback window.
70
70
71
+
<!--PW 9/6/22
72
+
71
73
## How does Personas handle identity merging?
72
74
Each incoming event is analyzed and external IDs are extracted (`user_id`, `anonymous_id`, `email`, and so on). The simplified algorithm works as follows:
73
75
@@ -81,7 +83,7 @@ Each incoming event is analyzed and external IDs are extracted (`user_id`, `anon
81
83
82
84
83
85
84
-
![Identity graph merging](images/merging_3.png"Flowchart of Segment merging profiles")
86
+
-->
85
87
86
88
## Is all matching deterministic, or is there any support for probabilistic matching?
87
89
All Profile matching is deterministic and based on first-party data that you've collected.
@@ -117,7 +119,7 @@ The audience in the image below includes all users that have Product Added in th
117
119
## What happens to conflicting and non-conflicting profile attributes?
118
120
If two merged user profiles contain conflicting profile attributes, Segment selects the newest, or last updated, attributes when querying the profile.
119
121
120
-
## How does Personas perform merge protection?
122
+
<!--PW 9/6/22 ## How does Personas perform merge protection?
121
123
122
124
Segment uses the Personas space's [identity resolution settings](/docs/personas/identity-resolution/) to prevent inaccurate profile merges. Segment uses identifier priorities and limits to determine how to add new merges and mappings to profiles.
123
125
@@ -127,7 +129,7 @@ In the following example, the identity resolution settings for `user_id` are `Pr
127
129
128
130
In this example, `anonymous_id: a1` is not reset during a `User Logout`. Without merge protection rules, Segment would merge `user_id u1` and `user_id u2`. Instead, the identity resolution algorithm detects that such a merge would break `user_id` uniqueness and prevents the merge.
129
131
130
-
This is especially helpful for preventing "blob users" that are merged together by non-unique anonymous IDs or by common group emails like `[email protected]`.
132
+
This is especially helpful for preventing "blob users" that are merged together by non-unique anonymous IDs or by common group emails like `[email protected]`.-->
131
133
132
134
## Which destinations support syncing the identity graph?
133
135
Most destinations on the Segment Platform are built up around a user model. They assume that a user will have a single userId. Further, most Destinations are not built to handle anonymous traffic.
| Identity Merges | 100 merges | Personas supports up to 100 merges per profile in its identity graph. Merges occur when a common `external_id` joins two existing profiles. For example, if a user initiates a mobile session but then signs in through a web application, a common identifier like `user_id` will join the two user profiles. No additional merges will be added once the profile reaches this limit. Event resolution for the profile, however, will continue. |
34
-
| Identity Mappings | 1000 mappings | Personas supports up to 1000 mappings per profile in its identity graph. Mappings are external identifier values like a `user_id`, email, mobile advertising `id`, or any custom identifier. No additional mappings will be added once the profile reaches this limit. Event resolution for the profile, however, will continue. |
33
+
| Identity Merges | 100 merges | Personas supports up to 100 merges per profile in its identity graph. Merges occur when a common `external_id` joins two existing profiles. For example, if a user initiates a mobile session but then signs in through a web application, a common identifier like `user_id` will join the two user profiles. Segment drops additional message merge attempts, which usually indicate corrupt profiles. Once the limit is reached, Segment rejects additional events. |
34
+
| Identity Mappings | 1000 mappings | Personas supports up to 1000 mappings per profile in its identity graph. Mappings are external identifier values like a `user_id`, email, mobile advertising `id`, or any custom identifier. Segment drops additional message mapping attempts, which usually indicate corrupt profiles. This limit counts mappings across all merged profiles. |
35
35
| Identify calls | 300 traits | Personas rejects Identify events with 300 or more traits. If your use case requires more than 300 traits, you can split the traits into multiple Identify calls. |
0 commit comments