Cleaning a Trade Show Attendee List Before Follow-Up Emails

To clean a trade show or event attendee list before follow-up, split the export by how each lead was captured (badge scan, manual entry, business card), deduplicate across booth staff, verify every address, and repair what you can from the other fields. Do it within a day or two, while conversations are fresh.

Event leads are some of the most valuable contacts a sales team gets all year, and some of the messiest. The export from a lead retrieval app looks clean, but each row came in through a different route, and each route introduces its own errors.

Where event lead data comes from

An event lead export mixes three capture methods, and each has its own kind of error.

Capture method	Who typed the email	Typical errors
Badge scan (QR or barcode)	The attendee, at registration	Typos, personal vs work address, colleague registered on their behalf
Manual entry in the app	Booth staff, on a phone, in a noisy hall	Misheard names, missing letters, wrong domain
Business card scan	OCR software	Character confusion (0/o, 1/l, rn/m), wrong field picked up

This is a known risk, not a hunch. M3AAWG's guidance on spam traps, Help! I Hit a Spam Trap! (February 2023), lists "lists of trade show participants" among the ways traps end up on mailing lists, and notes that typo traps can come from "transcription or scanning errors" made when the address was collected.

The badge scan feels authoritative because it comes from the organiser's system. It is not. A badge scan copies whatever was entered at registration. If the attendee typed jsmith@acme.cmo when they registered six weeks ago, that is what your lead export contains.

Manual entry is the riskiest route. Cvent LeadCapture, for example, lets booth staff tap Enter Manually to add a lead who is not wearing a badge, typing the details on their own device (Cvent exhibitor guide). That is useful and error-prone in equal measure.

Step 1: get the full export, from everyone

Make sure every device has synced before you export, or you will clean an incomplete list. In Cvent LeadCapture, booth staff must connect each device to Wi-Fi after the event to sync leads; unsynced leads cannot be exported, and only the exhibitor admin can export, as an Excel file, from the exhibitor portal. The same guide notes that booth staff cannot see leads their colleagues collected.

That last point causes duplicates. Two colleagues talk to the same visitor, both scan, and the lead appears twice with different notes. Other lead retrieval apps (Swapcard, Bizzabo, iCapture and the organiser's own tools) have their own export steps; the principle of "sync everything, then export once" applies to all of them.

Before cleaning, add a column for capture method if the export does not already have one. You will want it later.

Step 2: deduplicate, keeping all the notes

Deduplicate on email address, but merge the notes and qualification answers rather than discarding the second row. The notes are often the most valuable part of an event lead ("wants a demo in Q1", "talk to their CTO").

1. Lower-case and trim the email column.
2. Sort by email, then by scan time.
3. Where an email appears twice, keep one row and combine the notes and ratings from both.
4. Also check for the same name and company with different emails. That is often a badge scan (registration address) plus a manual entry (the address they told you at the booth). Keep both for now; verification will tell you which works.

Our guide to removing duplicates from a CSV has formulas and a short script.

Step 3: verify every address

Verify the whole export, then use the result together with the capture method to decide what to do with each lead. A few hundred to a few thousand event leads is a small file for any verifier.

Result	Badge scan	Manual or card scan
Valid	Send	Send
Invalid	Look for a typo you can fix from the company name and website	Same, and check the booth staff's notes
Risky	Small separate send; often a catch-all corporate domain	Same
Disposable	Attendee did not want to be contacted; respect it	Probably a mistake; check
Role (info@, events@)	May have been registered by an assistant or events team; find the person	Check notes for the real contact

The invalid column is where event lists are different from other lists. An invalid address on a cold list is just dropped. An invalid address on an event list belongs to someone you actually spoke to, and you usually have enough other information to fix it.

Step 4: fix the invalid addresses you can

Use the name, company and notes to repair invalid addresses, then verify the correction. This is where an hour of work recovers your best leads.

Common fixes:

• Domain typos. acme.cmo, acmee.com, gmial.com. Compare against the company's real website domain. See catching email typos for the common ones.
• OCR confusion. j.smith@acrne.com is almost certainly acme.com. Check the company name field.
• Wrong person's address. A colleague registered on the attendee's behalf, or the badge was swapped. If the name in the export does not match the local part of the email, find the right address.
• Missing address. Some manual entries have a name and company but no email. Use the company's email pattern and the email finder to find it.

After every fix, verify again. A corrected address that is still invalid should go to the sales rep as a call task, not into the email sequence.

Step 5: check what you are allowed to send

Lead retrieval terms and data protection law both limit what you can do with event contacts, so check before adding them to anything beyond follow-up. This is not legal advice.

Organisers set their own terms. The ISC High Performance conference's exhibitor GDPR FAQ, for example, likens a badge scan to handing over a business card, but limits exhibitors to contacting scanned attendees about their participation in the event, and attendees can revoke consent through the registration platform. Other events are more or less permissive. Read the lead retrieval agreement you signed.

In the US, the FTC's CAN-SPAM guide applies to B2B email, including a working opt-out honoured within 10 business days. In the UK and EU, your basis for emailing depends on what attendees agreed to and whether they are corporate or individual subscribers.

Practical rule: send one relevant follow-up about the conversation you had. Add people to ongoing marketing only where the event terms and your consent basis allow it, and make unsubscribing easy.

Step 6: send in a way that does not concentrate the bounces

Send event follow-up from the reps' normal inboxes in batches, not as one blast from a single address. Event follow-up can easily go out as one big send on the Monday after the show, which concentrates every remaining bounce on one inbox on one day.

• Spread the follow-up over two or three days.
• Send risky addresses last and in small numbers.
• Watch the first batch's bounces before sending the rest. If bounces are high, stop and re-check the list.

If your team sends event follow-up from a marketing platform instead, the same platform thresholds apply as for any campaign; see bounce rate limits by platform.

A 48-hour checklist after the event

When	Task
Last day of event	Every device synced to Wi-Fi
Day 1	Export once; add capture method column; deduplicate and merge notes
Day 1	Verify the full list
Day 2	Fix invalid addresses from company and notes; re-verify fixes
Day 2	Check lead retrieval terms; tag leads by what you may send
Day 2-4	Send follow-up in batches; risky last

The takeaway: an event list is not a cold list. Every invalid address belongs to someone you met, so do not just drop it. Verify, repair what you can from the other fields, and get the follow-up out within the week while the conversation is still remembered. To check a handful of addresses straight away, use the free verifier.