Merge pull request #553 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/personas/audiences/index.md

@@ -80,12 +80,22 @@ Because most marketing tools are still based at the user level, it is often impo
 > info ""
 > When you connect a new Destination to an existing Audience, Personas will backfill historical data for that Audience to the new Destination.
 
+### Audience sync ETAs
+
+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.
+
+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.
+
+> info "Real-time and batch syncs"
+> 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.
+
 ## Understanding compute times
 
 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.
 
 As a result, **Segment recommends waiting at least 24 hours for an Audience to finish computing** before you resume working with the Audience.
 
+
 ## 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:

src/personas/faqs.md

@@ -69,14 +69,13 @@ Lookback windows are precise down to the hour, so a 90-day lookback window will
 The trait and audience will automatically update going forward as historical events exceed the lookback window.
 
 ## How does Personas handle identity merging?
-Each incoming event is analyzed and external IDs are extracted (`user_id`, `anonymous_id`, `email`). The simplified algorithm works as follows:
+Each incoming event is analyzed and external IDs are extracted (`user_id`, `anonymous_id`, `email`, and so on). The simplified algorithm works as follows:
 
-- Segment first searches the Identity Graph for incoming external IDs.
-- If Segment find no users, it creates one.
-- If one user is returned, then that user is chosen.
-- If multiple users are returned, merge protection kicks in and checks the validity of all of the provided external IDs.
-  - If the merge protection checks pass, Segment creates a new merge connection between those two users. The first user profile ever created becomes the parent profile, and all merged users become child profiles.
-  - If the merge protection checks fail, Segment discards the lowest precedence external ID and re-run the algorithm.
+1. Segment first searches the Identity Graph for incoming external IDs.
+2. If Segment finds no matching profile(s), it creates one.
+3. If Segment finds one profile, it merges the incoming event with that profile. (This means that Segment adds the external IDs on the incoming message and resolves the event to the profile.)
+4. If Segment finds multiple matching profiles, Segment applies the identity resolution settings for merge protection. Specifically, Segment uses identifier limits and priorities to add the correct identifiers to the profile.
+5. Segment then applies [Personas default profile limits](/docs/personas/product-limits/#identity) to ensure profiles remain under these limits. Segment doesn't add any further merges or mappings if the profile is at either limit, but event resolution for the profile will continue.
 
 ![Identity graph merging](images/merging_1.png "Flowchart of Segment receiving an incoming event")
 
@@ -118,19 +117,22 @@ The audience in the image below includes all users that have Product Added in th
 ## What happens to conflicting and non-conflicting profile attributes?
 If two merged user profiles contain conflicting profile attributes, Segment selects the newest, or last updated, attributes when querying the profile.
 
-## What is Personas Merge Protection?
-Personas merge protection algorithm protects your identity graph from unnecessary merges by finding and removing untrusted external IDs. Here's an example:
+## How does Personas perform merge protection?
+
+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.
+
+In the following example, the identity resolution settings for `user_id` are `Priority 1` and `Value Limit 1`:
 
 ![Merge protection](images/merge_protection.png "An image representing the merge protection flow")
 
-In this example, `anonymous_id: a1` is not reset during a `User Logout`. Without merge protection, Segment would merge `user_id u1` and `user_id u2`. Instead, the Merge Protection algorithm detects that such a merge would break user_id uniqueness and prevents the merge.
+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.
 
 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]`.
 
 ## Which destinations support syncing the identity graph?
 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.
 
-By default, Segment doesn't sync the output of the Identity Graph to Destinations. However, Segment computed traits and audiences are based on the entire user profile, including anonymous and merged data. We sync the value of these computations (e.g. `blog_posts_ready_30_days: 10`) using all `userIds` on the profile.
+By default, Segment doesn't sync the output of the Identity Graph to Destinations. However, Segment computed traits and audiences are based on the entire user profile, including anonymous and merged data. Segment syncs the value of these computations (for example, `blog_posts_ready_30_days: 10`) using all `userIds` on the profile.
 
 For Destinations that support an `alias` call (for example, Mixpanel), you can emit an `alias` call on merge.
 

src/personas/product-limits.md

@@ -30,8 +30,8 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
 
 | name              | Limit         | Details                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | ----------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 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. |
-| 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.                                                                                                                    |
+| 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. |
+| 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.                                                                                                                    |
 | 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.                                                                                                                                                                                                                                                                                                   |
 
 
@@ -63,4 +63,4 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
 | Step Name       | Maximum length of 170 characters | Once the limit is reached, you cannot add additional characters to the name. |
 | Key             | Maximum length of 255 characters | Once the limit is reached, you cannot add additional characters to the key.  |
 | Journey Name    | Maximum length of 73 characters  | Once the limit is reached, you cannot add additional characters to the name. |
-| Compute credits | Half a credit for each step      | Each step in a published Journey consumes half of one compute credit.        | 
+| Compute credits | Half a credit for each step      | Each step in a published Journey consumes half of one compute credit.        |