Cross-list deduplication means finding records that appear in two or more separate lists.

It is useful when you have CSV files, CRM exports, campaign lists, or scraped datasets and need to know which records overlap.

Common cross-list use cases

Use cross-list matching to:

  • Remove contacts from a campaign list when they already exist in your CRM.
  • Remove existing customers from a prospecting list.
  • Compare a new scrape with URLs processed in an earlier run.
  • Compare event registrations with a reference contact list.
  • Prevent the same account from entering two outreach campaigns.

🔍 Example

If CRM Export and Event Registrations share an email, remove the matching row from Event Registrations while preserving the CRM collection.

How cross-list deduplication works

Keep each list in a separate collection. Map properties that describe the same identifier, even when their names differ:

  • CRM Export has Email.
  • Event Registrations has Attendee Email.

Then select the comparison algorithm and processor. Use Exact or Smart matching for stable identifiers such as email, domain, URL, or LinkedIn profile.

Review matches before removing records

Open Clean > Match across collections, select the collections, and map their identifier properties. Cross-collection matching requires a paid plan. Review the matched groups before deciding which rows should be removed. Matching an event registration with a CRM contact does not itself update your CRM. To update a Datablist collection from the reviewed file, use the unique-key bulk-update workflow and check whether unmatched rows should be skipped.

You can inspect the overlap without deleting anything. Open Result files and choose the Source collection, such as Event Registrations. The source choice determines which list's rows appear in these CSVs:

  • Matched records: source rows in groups that meet the current automatic processing confidence threshold, with their strongest match and explanation.
  • Needs-review records: source rows in lower-confidence groups.
  • Unmatched records: source rows outside the current match groups, using their original columns.
  • Match crosswalk: every source-to-other-collection relationship, useful for checking source IDs or a row with several possible matches.

An unmatched row means no match was found with the selected properties, algorithms, and thresholds. It is not proof that the person is absent from the CRM: a blank email or a changed identifier can hide an overlap. Check those cases before treating the export as a list of new leads.

For suppression, keep the CRM rows and remove only confirmed matches from the campaign or registration collection. If you need one consolidated list with merged values, import the files into a single collection and use the single-list deduplication workflow.

See the multiple-file deduplication guide for a complete workflow.