Skip to content

Commit e5c8c0c

Browse files
pwsegpwseg
authored
Merge pull request #3907 from segmentio/events-at-limits-updates
Add Events at Limits Updates
2 parents 0e3f4e5 + 9431cd8 commit e5c8c0c

File tree

3 files changed

+12
-9
lines changed

3 files changed

+12
-9
lines changed

‎src/engage/faqs.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,14 +66,14 @@ The audience in the image below includes all users that have Product Added in th
6666
> info ""
6767
> Funnel Audiences compute based on all instances of the parent event within the lookback period. This means that if you have a user that Product Added ⟶ Order Completed ⟶ Product Added, this user would be entered into the Abandoned Cart state despite having previously completed an order.
6868
69-
<!--PW 9/6/22 ## What is Engage Merge Protection?
69+
## What is Engage Merge Protection?
7070
Engage merge protection algorithm protects your identity graph from unnecessary merges by finding and removing untrusted external IDs. Here's an example:
7171

7272
![Merge protection](images/merge_protection.png "An image representing the merge protection flow")
7373

7474
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.
7575

76-
This is especially helpful for preventing "blob users" that are merged together by non-unique anonymous IDs or by common group emails like `team@company.com`. -->
76+
This is especially helpful for preventing "blob users" that are merged together by non-unique anonymous IDs or by common group emails like `team@company.com`.
7777

7878
## Which destinations support syncing the identity graph?
7979
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.

‎src/profiles/faqs.md‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,6 @@ Identity Graph automatically collects a rich set of external IDs without any add
1717

1818
If you want Identity Graph to operate on a different custom ID, you can pass it in using `context.externalIds` on an `identify()` or `track()`. If you're interested in this feature, contact your CSM to discuss the best way to implement this feature.
1919

20-
<!--PW 9/6/22
2120
## How does Profiles handle identity merging?
2221
Each incoming event is analyzed and external IDs are extracted (`user_id`, `anonymous_id`, `email`). The simplified algorithm works as follows:
2322

@@ -27,11 +26,15 @@ Each incoming event is analyzed and external IDs are extracted (`user_id`, `anon
2726
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.
2827
5. Segment then applies [Profile limits](/docs/profiles/profile-api-limits/) 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.
2928

29+
{% comment %}
30+
3031
![Identity graph merging](images/merging_1.png "Flowchart of Segment receiving an incoming event")
3132

3233
![Identity graph merging](images/merging_2.png "Flowchart of Segment searching for profiles by external ID")
3334

34-
![Identity graph merging](images/merging_3.png "Flowchart of Segment merging profiles") -->
35+
![Identity graph merging](images/merging_3.png "Flowchart of Segment merging profiles")
36+
37+
{% endcomment %}
3538

3639
## Is all matching deterministic, or is there any support for probabilistic matching?
3740
All Profile matching is deterministic and based on first-party data that you've collected.

‎src/profiles/profile-api-limits.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,8 @@ redirect_from:
1515

1616
## Identity
1717

18-
| name | Limit | Details |
19-
| ----------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
20-
| Identity Merges | 100 merges | Engage 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. |
21-
| Identity Mappings | 1000 mappings | Engage 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. |
22-
| Identify calls | 300 traits | Engage 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. |
18+
| name | Limit | Details |
19+
| ----------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
20+
| Identity Merges | 100 merges | Engage 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. |
21+
| Identity Mappings | 1000 mappings | Engage 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. |
22+
| Identify calls | 300 traits | Engage 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

Comments
 (0)