How to Configure Lead Matching Before Your Next Event

The import finished at 9 p.m. By 9:15, a RevOps manager is staring at 200 duplicate records in Salesforce and realizing the badge scan data from the show floor had no email addresses. No email means the standard matching rule never ran. Every scanned contact came in as a net-new Lead, regardless of whether that person was already a known Contact, an open opportunity, or a customer.

The culprit is lead matching in a CRM, the step where the system compares each incoming record against existing data, using match keys such as email address or Contact ID, to decide whether to update an existing Lead or Contact or create a new one. When the key field is missing, matching breaks before it starts.

This scenario plays out at events constantly, and configuration causes it. Fix it before the event instead of after the debrief.

This post gives RevOps, marketing operations, and sales operations teams a framework for that configuration: matching strategy, field-write rules, duplicate prevention, and ownership assignment.

Key takeaways

• Email-first matching fails event leads because badge scans frequently arrive without email addresses, leaving CRM matching rules with no key to evaluate.
• Choosing between Leads-only, Leads-and-Contacts, and Accounts-and-Contacts matching is a data model decision your team makes before the event, ahead of the CSV landing.
• Unmatched event leads are the highest-risk records in any post-event batch: New records with no assigned owner get no follow-up, and a new record for a lead already in your CRM creates a duplicate and leaves the in-person data unattached to what you already know about that lead.
• Write-if-Blank field rules stop lower-quality scanned values from overwriting manually curated CRM data during event lead sync.
• Clean lead matching is what makes event attribution work: Mismatched records break campaign influence reporting and make event ROI impossible to verify.

Why event leads break standard matching logic

Your inbound matching rules expect complete form submissions. Badge exports arrive incomplete, inconsistent, and in high-volume bursts. The three sections below cover the failure modes that follow: missing match keys, duplicate-producing volume, and processing delay.

Incomplete badge data defeats email-first matching

Badge exports frequently omit email addresses entirely, or deliver attendee-submitted addresses that registrants entered to avoid marketing. Salesforce's standard matching rule evaluates email on an exact, 100% threshold, but it also offers fallback paths: name plus company, name plus phone. Thin badge records strip those paths too, because they lack a verified company name and phone number and capture titles inconsistently. Every match path collapses at once.

Enriching at the point of capture, before CRM sync, supplies verified identifiers, and scoring leads at capture shows reps which records deserve follow-up first.

Volume spikes multiply duplicate risk fast

Each matching failure in a high-volume event batch becomes a potential duplicate. A booth team that scans 200 leads over a three-day trade show can add 200 new records to your CRM before the team is back at the office.

A third-party analysis of Salesforce deduplication shows that native Matching Rules work within an object by default (Lead-to-Lead or Contact-to-Contact), so matching a Lead to a Contact takes added configuration. Without it, data gets contaminated when someone exists in both objects. At event volume, manual cleanup turns into a backlog.

Delayed matching turns warm leads cold

Matching delay hurts event follow-up because every hour an unmatched, unowned record sits in the queue is an hour lost on a conversation that already happened in person.

In the typical post-event chain, a badge export arrives as a CSV, ops cleans and uploads it, matching runs, duplicates surface, someone resolves them manually, and a rep gets the record. By then, the conversation is days old.

An inbound form submission matches and lands in the CRM within seconds. Event leads need a different capture-to-sync architecture from the start to match that speed.

What matching decides for every captured lead

Every incoming event capture resolves to one of three outcomes: updating an existing Lead or Contact, creating a new record, or landing in the wrong place entirely. No error message fires in that third case. The CRM quietly produces a duplicate, an orphaned record, or an overwritten field. Each failure traces back to one of three configuration choices you control: matching strategy, identifier evaluation order, and field-write rules.

Choose your matching strategy first

Your matching strategy should follow your CRM data model. Whether your team runs a Lead-first, mixed Lead-and-Contact, or Account-based structure determines which objects the CRM checks incoming event records against. The three options below each map to one of those models.

Leads only: Simplest, lowest object complexity

Leads-only matching routes every incoming event record to the Salesforce Lead object and skips Contact checks and Account lookups. That single-object scope makes the configuration easy to audit and simple to troubleshoot.

The tradeoff is cross-object duplicate risk. If a scanned person already exists as a converted Contact in your CRM, Leads-only matching creates a new Lead rather than updating the existing record. Prevent that with a dedicated sync tool or a configured cross-object Duplicate Rule.

Leads and contacts: Right for most B2B teams

Leads-and-Contacts matching checks both CRM objects before creating a new record, which prevents the most common event-lead duplicate, a scan that recreates a known Contact as a Lead.

Most B2B CRMs are mixed. Some prospects converted to Contacts months ago; others are still sitting as Leads. If your matching logic only checks the Lead object, a rep who scans a badge at a trade show can push a brand-new Lead record for someone your account executive already converted into an open opportunity. That duplicate then competes with the real Contact in your reporting and your nurture flows.

Cleaner object matching also pays off downstream. When every event capture lands on the right record, your lead segmentation reflects actual buyer stage rather than an artifact of which object the matching logic happened to check first.

For most B2B teams, Leads-and-Contacts is the right default.

Accounts and contacts: Best for ABM-oriented data models

Accounts-and-Contacts matching is the right choice when company identity matters as much as the individual Contact. Instead of checking only for a matching person, this strategy also matches against existing Account records by domain or company name, then creates a new Contact underneath the matched Account rather than as a disconnected record.

Before enabling this strategy, audit your Account domain field coverage in the CRM. If Account records have inconsistent or missing domain data, domain-based matching produces more mismatches than it prevents. Treat clean domain coverage as a prerequisite.

Set your matching order and priority logic

Evaluate match keys from most specific to weakest fallback: Contact ID first, then Contact email, then Lead ID, then Lead email.

The sequence changes outcomes because a weaker identifier that runs early can override a more certain one. A shared email alias or a reused company domain can match the wrong record if email runs before ID. Contact ID is unambiguous. Lead email is ambiguous.

This order catches legitimate repeat contacts without producing false matches.

Configure field-level write rules

Set write behavior per field. When enriched event data syncs to an existing record, an overwrite rule replaces whatever is in the field regardless of quality.

Write if Blank populates a field only when it is currently empty. Overwrite replaces the existing value unconditionally.

Consider a rep who corrected a contact's job title in Salesforce after a discovery call. A badge scan at the next event returns the title printed on the badge, which may be outdated. Write if Blank keeps the corrected value; Overwrite replaces it.

Verified email and phone from enriched capture data can generally accept overwrite. Lead Status, Account Owner, and custom qualification fields should always be Write if Blank. See how this maps to a full event sync configuration.

Prevent duplicates from repeat event captures

Prevent repeat captures from becoming duplicates by tagging each scan with a stable interaction ID upstream, before the CRM write occurs, so the sync layer logs a second touchpoint rather than creating a new record.

Field-based CRM matching rules weren't built to catch the same person scanned at two different booths on two different days. Each scan triggers a separate matching evaluation comparing name, email, and company at the moment of write. If those field values don't clear the matching threshold both times, you get two Lead records for one person.

Assign ownership for every unmatched lead

Every matching strategy needs a fallback ownership rule so a net-new event Lead has a responsible rep the moment it reaches the CRM.

Net-new records are the highest-risk records in any event batch. They're contacts your team has never worked, which makes them the most valuable leads you captured.

Configure one of three fallback options before the event: a default owner, a shared queue, or round-robin assignment. Pick one, set it, and confirm it fires on a test record. Learn more about enriching and routing event leads automatically.

How Mobly Capture feeds cleaner data into matching

Mobly Capture enriches each scanned lead before it reaches your CRM, so your matching rules have more to evaluate.

Mobly Intelligent Enrichment routes each contact field, including work email, to the provider most likely to return an accurate result for that field and industry. Email-first matching gets a usable key instead of a blank field.

Capture also scores each lead against your ideal customer profile (ICP) at the point of scan, and the tags and notes your rep adds travel with the lead into the CRM. Enriched, tagged, attributed leads sync into Salesforce, HubSpot, or your marketing automation platform (MAP) in near real time. Leads captured offline sync when connectivity returns.

Test your matching logic before the event floor opens

Run three tests before the floor opens: sync a record that matches an existing Contact, sync a record for a brand-new contact, and sync a record with a blank email field. Confirm the Contact updates correctly, the new Lead gets the right owner, and the blank-email record falls back to the next match key rather than failing silently.

Test against your configured strategy. A Leads-and-Contacts setup needs records that exist as both a Lead and a Contact to confirm priority resolves in the right order. On the Salesforce side, each duplicate rule supports up to three matching rules, with five active matching rules allowed per object. If your badge data includes phone numbers with inconsistent country codes, add a custom fuzzy-match rule now, before the event closes.

Clean matching is what makes event ROI provable

Matching strategy, field-write rules, duplicate prevention, and fallback ownership determine whether you can attribute your event spend to pipeline at all.

When a scanned lead lands on the wrong record, or on no record, or on a record owned by no one, campaign influence breaks. The lead exists in Salesforce, but the pipeline story doesn't. That separates a CRM that looks clean from one that supports event ROI measurement.

Before your next event, open your Salesforce integration settings and confirm your matching order, your write rules, and your fallback owner. Do it before anyone scans the first badge, and you skip the reconciliation queue on Monday morning.

Mobly Capture hands your CRM enriched, scored leads in near real time, so your attribution reporting rests on cleaner data. Connect each event campaign in Salesforce to a Mobly event record, and a deal that closes 90 days later traces back to the booth conversation and the rep who scanned the contact. Once the data is clean, the ROI math is straightforward.

Run it yourself in the event ROI calculator.