Skip to main content
Question

how does canonical_segment_id is survived when profiles are merged

  • April 9, 2025
  • 3 replies
  • 126 views
K
Forum|alt.badge.img+2

We are in the processing of utilized Profile Sync and ran into this question: how does canonical_segment_id is survived when profiles are merged?
There is no straightforward documentation explaining the merging algorithm to determine the surviving canonical_segment_id when two profiles (with two different segment_id) are merged. We have performed some tests and noticed the first-created canonical_segment_id remained but would like to have a definite confirmation. 

K
A
R

3 replies

Chauntel Greaves
Segmenter
Forum|alt.badge.img+3

Hi there ​@kzheng! You can find an overview of how merges occur in this section of our Profile Sync docs. When a merge happens, the first canonical_segment_id remains and the second is dropped. This last table shows how profile_2 is merged away to profile_1. 

~Chauntel
K
Forum|alt.badge.img+2
  • kzheng
  • Author
  • April 22, 2025

​@Chauntel Greaves that’s what I have observed and tested as well. However, I would like to get a definite confirmation that the First-Created canonical_segment_id always remains when merging occurs. If not, what would be the scenarios that the first id would be merged into a new one? 

Chauntel Greaves
Segmenter
Forum|alt.badge.img+3

Hi ​@kzheng confirming that if theres an existing id and we get an identifier that recognizes the same profile at a later date/time, the canonical id gets dropped and merged into the existing id. Adding two more links from our docs that might be useful: here and here. Hope this helps.

~Chauntel
Terms & ConditionsAccessibility statement