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.
Datablist cross-collection workflow
Datablist compares records across several collections and lets you remove matches from the collection you select. The reference collection remains unchanged.
The automatic action is a suppression operation. It does not merge values between collections or create a new consolidated collection. Duplicate records that exist only inside one collection are also skipped during a cross-collection run.
Follow the tested deduplicate multiple files guide for column mapping, match review, and removal. Use the single-list deduplication workflow when records must be merged inside one collection.