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/profiles/faqs.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,13 +26,15 @@ Each incoming event is analyzed and external IDs are extracted (`user_id`, `anon
26
26
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.
27
27
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.
28
28
29
-
<!-- PW, 12/5/22
29
+
{% comment %}
30
30
31
31
![Identity graph merging](images/merging_1.png"Flowchart of Segment receiving an incoming event")
32
32
33
33
![Identity graph merging](images/merging_2.png"Flowchart of Segment searching for profiles by external ID")
34
34
35
-
-->
35
+
![Identity graph merging](images/merging_3.png"Flowchart of Segment merging profiles")
36
+
37
+
{% endcomment %}
36
38
37
39
##Is all matching deterministic, or is there any support for probabilistic matching?
38
40
All Profile matching is deterministic and based on first-party data that you've collected.