ChatGPTClaudePerplexityGoogle
View as Markdown

TL;DR

  • Short forms create contacts with an email and little else.
  • Many of those people already exist in the CRM under another email or with more details.
  • Match the thin records on email first, then on email domain plus name where they have one.
  • When merging, keep the full record as the primary so its details and owner stay.
  • In Dedupely, blank values never overwrite filled-in ones, so the full record keeps its data.

A newsletter form asks for one thing: an email address. A content download asks for an email and a first name. Each sign-up creates a contact with almost nothing in it.

Many of those people are already in your CRM. A customer subscribes with their personal email. A prospect a rep is working downloads a guide. The result is a thin record sitting next to a full one, and two versions of the same person in your reports and lists.

This post covers how to find those thin records' duplicates and how to merge them so nothing is lost.

Why email-only records duplicate

A form usually checks whether the email already exists. If it does, it updates that contact. If it doesn't, it creates a new one. Email-only duplicates happen when:

  • The person uses a different email. A personal address for the newsletter, a work address for sales conversations.
  • The email was typed differently. A typo or a different capitalization that the form treats as new.
  • The form doesn't check at all. Some form tools and integrations always create a new contact.

Why web forms create duplicate contacts in your CRM covers how each form setup behaves.

How to find the full record

Email-only records give you very little to match on, so work from the strongest signal down:

What the thin record has Match on Confidence
Same email as a full record Email High; these are usually typo or case differences
Work email at a known company Email domain plus first name Medium; review
Personal email plus first and last name Name plus phone or company, if the full record has them Low to medium; review
Personal email only Usually can't be matched safely Leave it

A personal email with no other data can't be connected to a work record reliably. Leave those as they are until the person gives you more, like a name or company on a later form.

Merge into the full record

When you find the pair, the full record should be the primary:

  • It has the owner, so the rep working the contact keeps it.
  • It has the history, like calls, deals and notes.
  • It has the details, like company, phone and job title.

The thin record adds what it has: the newsletter subscription, the form submission, and possibly a second email address. If your CRM has an additional email field, keeping the personal address there means the next newsletter form finds the right contact.

Make sure empty fields on the thin record don't overwrite the full record's data, and that the subscription and opt-in status from the thin record carry over.

Reduce new email-only duplicates

  • Ask for a name on forms where it doesn't hurt sign-ups.
  • Pre-fill forms for known contacts, so they don't type a different address.
  • Use one form tool that updates by email instead of several that each create contacts.

How Dedupely merges thin records into full ones

In Dedupely, each field gets its own match option, so you can match on email, or on email domain with Domain Root plus first name for work addresses. When records merge, blank values never overwrite filled-in ones, so the full record keeps its company, phone and other details. The Primary Record setting decides which record survives, and "Most Field Data" picks the record with the most information.

Activities and associations move to the surviving record, and Append keeps every unique value in your CRM's multi-value fields, like additional email addresses.

Fold your thin records into full ones

Thin records belong with full ones

Email-only sign-ups are useful: they're people who chose to hear from you. They just shouldn't live apart from the full record of the same person.

Match them on email first, then on domain and name, and leave personal-email-only records alone until they give you more. When you merge, keep the full record as the primary and carry over the subscription.

Frequently asked questions

Why do newsletter forms create duplicate contacts?

The person signs up with a different email from the one in your CRM, or the form doesn't check for existing contacts. Either way, a new contact is created.

Which record should survive the merge?

The full one. It has the owner, history and details. The thin record contributes its subscription and any extra email address.

Can I match a personal email to a work record?

Only with another shared field, like name plus phone. A personal email alone can't be connected to a work record safely.

Will merging remove the newsletter subscription?

It shouldn't, but check how your CRM handles consent on merge before merging in bulk.

How do I stop email-only duplicates?

Ask for a name, pre-fill forms for known contacts and use form tools that update existing contacts by email.