Skip to main content

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. 

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


 

 


hello


@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? 


Reply