Dedupe
Duplicates come in whenever you merge sources — a Google Maps scrape, an Apollo export, and a CRM pull all describe the same company differently.
Dedupe removes repeated rows based on a column you choose.
Why it matters
- Credits. Every duplicate row runs every action column again. Two rows for the same domain is double the enrichment spend for one answer.
- Reputation. The same person receiving your sequence twice is the fastest route to a spam complaint.
- CRM hygiene. Duplicates exported into HubSpot or Salesforce take far longer to clean up there than here.
How to dedupe
- Click the ⚙️ icon in the top-right of the table
- Click Dedupe
- Choose the column to match on
- Review what will be removed
- Confirm
Dedupe before you run enrichment, not after. Deduping afterwards saves nothing — the credits are already spent.
Which column to match on
Pick the column that is unique by nature, not the one that is easiest to read.
| Match on | Use for | Watch out for |
|---|---|---|
| Domain | Company-level tables | acme.com and www.acme.com are different strings |
| Work email | Contact-level tables | Only works on rows already enriched |
| LinkedIn URL | People sourced from LinkedIn | Vanity URLs vs numeric IDs |
| Company name | Last resort | ”Acme”, “Acme Inc”, “Acme Pty Ltd” all survive |
Normalize the column first if your import is messy — a domain column derived from a URL dedupes far more reliably than raw text.
Dedupe removes rows. Export a copy of the table first if the source list is hard to rebuild.
Keeping it clean afterwards
- Dedupe as a step in your import routine, not as a cleanup job
- Filter for email is empty after deduping to see what still needs enrichment
- For records already in your CRM, dedupe against the CRM using a CRM integration rather than the table alone
Where to next
- Filter — narrow before you spend
- Lead Sourcing — where the duplicates come from