What is a unique identifier?
A unique identifier is the value that says "this record, and no other" - the anchor for matching and integration.
Its uniqueness and stability determine how reliably you can match, dedupe, and sync records across systems.
Short answer
A unique identifier is a value that reliably distinguishes one record from all others - like an email for a contact, a web domain for a company, or a system-assigned ID. Unique identifiers are the strongest keys for matching, deduplication, and integration, because they map to exactly one entity. Choosing good unique identifiers is what makes record matching reliable.
Key takeaways
- A value that reliably distinguishes one record from all others.
- Examples: email, web domain, system ID.
- The strongest key for matching, dedupe, and integration.
- Good identifiers are unique and stable over time.
Why it matters
Matching, deduplication, and integration all rely on identifying the same entity across records or systems, and unique identifiers are the most reliable way to do it. A good identifier - unique and stable - makes matching trustworthy; matching on weak keys like name alone produces false matches and misses.
How Ardovo handles it
Ardovo uses strong unique identifiers - email for contacts, domain for accounts, plus system IDs - as the backbone of matching, dedupe, and integration. Rook relies on these reliable keys, so records match to exactly one entity across the system and connected tools.
Frequently asked questions
What makes a good unique identifier?
Uniqueness and stability - a value that maps to exactly one entity and does not change over time. Email for contacts and web domain for companies are strong because they are highly unique and reasonably stable. System-assigned IDs are perfectly unique. Names make poor identifiers because they repeat and vary.
Why are unique identifiers important for matching?
Because matching, dedupe, and integration all need to identify the same entity reliably, and a unique identifier maps to exactly one entity. Matching on strong identifiers like email and domain is reliable, while matching on weak keys like name alone produces false matches and misses real duplicates.
What is used as a unique identifier in a CRM?
For contacts, the email address; for accounts, the web domain; and system-assigned record IDs behind the scenes. These strong identifiers anchor matching, deduplication, and integration. They are chosen because they are far more unique and stable than names, which vary and repeat too much to identify reliably.