Merging duplicates can bring conflicting data together. For example, an older record may show that someone unsubscribed, while a newer duplicate reflects more recent consent to resubscribe. Once the records are merged, both solicit codes may appear on the same record without any obvious explanation of how that happened.

A simple "Records merged on [date]" entry would alert users that the conflicting information may have resulted from a merge and prompt them to review the consent history before deciding which value is correct.

This small piece of history would make merged data much easier to understand and help users make better decisions around consent, communications and data quality.