Canonical Record

A practical example

Example: after syncing a CRM with a marketing platform, a contact exists with two job titles from different sources.

The team declares the CRM copy canonical, so enrichment fields and campaign membership always resolve against that version.

What to evaluate before investing

• Ask whether the platform lets you designate a system of record per object, not just globally.
• Check how downstream references behave: do campaign history and activity logs attach to the canonical record or fragment across copies?
• Confirm what happens when the canonical source deletes a record: is the deletion propagated or flagged for review?

Limitations and tradeoffs

Declaring a canonical source concentrates risk: errors in that system now propagate everywhere, so its data quality processes must be stronger than the rest.