Duplicates appear when records arrive without a shared match key, when an import bypassed dedup, or when identity resolution couldn't confidently merge them. Golden DB's two-tier matching catches most; the rest can be merged manually.
How dedup works
Golden DB matches deterministically first (exact email, or domain+name) and then probabilistically (fuzzy) for the rest (see Identity resolution explained). Records that share no reliable key — a personal email vs work email, a typo'd domain — can slip past automatic matching.
Common causes
A CRM import or API upsert that keyed on a field turgo couldn't match; two records with different emails for the same person; a company entered under two domain variants; or a merge the resolver flagged as low-confidence and left separate on purpose.
Fixes
Merge duplicates manually from the record view — turgo preserves provenance and the audit trail through the merge (see Auditing Golden DB updates). For API writes, POST upserts by email/domain by default, so send a match key to stay duplicate-safe (see Core endpoints reference).
Prevention
Standardize inbound data (consistent domain format, work emails where possible), let turgo's upsert handle matching rather than blind-creating, and periodically run a dedup review so duplicates don't accumulate.
