View as Markdown

TL;DR

  • Bots and spam sign-ups often create records with repeated names, random emails and junk in every field.
  • A duplicate search groups them together, or with real people, because their values repeat.
  • Merging spam into a real record adds junk values and fake activity to a real person.
  • Spam isn't a duplicate of anyone: find it, exclude it from your searches and delete it.
  • In Dedupely, filters and Safety Settings keep junk records out of merges, so you can review and delete them.

A form without protection gets found by bots. Within days, the CRM has hundreds of new contacts: "test test", "asdf", random strings at disposable email domains, the same fake name over and over. Run a duplicate search, and these show up as big duplicate sets.

It's tempting to merge them and move on. Don't. Spam records aren't duplicates of a real person, and merging them makes things worse. This post covers why and what to do instead.

Why spam looks like duplicates

Bot pattern What a duplicate search sees
The same fake name on many sign-ups A large set of matching names
Random emails at the same disposable domain Matches on email domain
Junk in the company field, like "test" or "N/A" Matches on company name
A real person's email used by a bot A match with the real person's record

The last one is the dangerous one: a bot record that matches a real contact.

Why merging spam is a mistake

It adds junk to real records. If a spam record merges into a real contact, its values can win in some fields: a fake phone number, a junk company name, a bogus job title.

It adds fake activity. Form submissions and page views from the bot become part of the real person's history, which can change their lead score or lifecycle stage.

It keeps the spam. Merging spam records with each other leaves one spam record instead of fifty. It's still in your CRM, still counted, maybe still billed.

Delete it instead

Spam isn't a duplicate of anything. The right action is to remove it:

  1. Find it with filters: disposable email domains, names like "test", the same submission time, junk values in required fields.
  2. Exclude it from duplicate searches, so it doesn't group with real records while you clean up.
  3. Check for real records caught up in it, like a real person's email used by a bot.
  4. Delete the spam in your CRM, and in any tool it synced to.
  5. Fix the source: add bot protection to the form.

Placeholders and test records are different

Not every junk-looking record is spam. Real people sometimes type "N/A" in a required field, and teams create test records on purpose. Those need a different approach: the real person should keep their record, without the placeholder value. See Placeholder values that make records look like duplicates.

How Dedupely helps keep spam out of merges

In Dedupely, filters on any synced field, like email, name, created date or source, let you leave suspicious records out of a search, or focus a search on them so you can review them. Safety Settings, on by default, hold back sets with more than 20 records and sets built on poor or example data, like test@test.com, from bulk merges and Auto Merge, so a burst of bot sign-ups doesn't merge by accident. You can reject sets that shouldn't merge, and they stay out of future searches. Delete the spam itself in your CRM.

Keep junk out of your merges

Spam isn't a duplicate

Bot and spam records match each other because their values repeat, not because they're the same person. Keep them out of your merges, check for real records among them, delete the spam and protect the form that let it in.

Frequently asked questions

Should I merge or delete spam and bot contacts in my CRM?

Delete them. They aren't duplicates of a real person, and merging adds junk values and fake activity to real records.

Their values repeat, like the same fake name or the same disposable domain, so they match each other.

What if a bot used a real person's email?

Check those records by hand. Keep the real person's record and delete the bot's.

How do I find spam records?

Filter on disposable email domains, names like "test", junk in required fields and submissions in a short time window.

How do I stop it happening again?

Add bot protection to your forms, and check new records from forms regularly.