How to Get Tradeshow Leads into Salesforce
The pattern that works is simple: clean the file, match it to existing CRM context, filter ICP first, enrich only the rows that matter, then import as Leads and Campaign Members before you activate follow-up.
Short answer
If you dump raw badge scans straight into Salesforce, you will usually create duplicates, waste enrichment spend, and make the SDR team clean up the mess later.
- Match before you import.
- Filter ICP before you enrich.
- Import with campaign attribution intact.
- Activate only the approved subset after the CRM write is done.
The pattern that works
This is the sequence FoundryOps uses when a tradeshow file has to become usable Salesforce pipeline input instead of another cleanup project.
Normalize the file first
Start with names, emails, and company values that are clean enough to match. Raw badge scans are usually too messy to import directly.
Match against existing CRM context
Before you create anything new, identify which rows already map to known accounts or contacts so you do not spray duplicates into Salesforce.
Filter ICP before enrichment
Do not burn enrichment credits on the whole file. Segment the list first so you only enrich the rows your team will actually work.
Enrich only the approved subset
Fill the missing fields you need for routing and follow-up after the file has been matched and prioritized.
Import as Leads plus Campaign Members
Preserve campaign attribution while keeping the resulting records usable for SDR follow-up and reporting.
Activate the approved rows
Push the ICP-approved subset into the sequencer or outbound workflow your team actually uses after the CRM import is complete.
What FoundryOps does
- Matches badge-scan rows to Salesforce context before import.
- Flags ICP rows so enrichment spend is focused where it matters.
- Supports the import and activation flow across CRM and sequencer surfaces.
What FoundryOps does not do
- It does not resell data or force you into a bundled data vendor.
- It does not assume every row deserves enrichment.
- It does not replace CRM governance with blind bulk writes.
Where the proof lives
This guide is the short answer. These pages show the workflow and the execution evidence.
Tradeshow use case
The product-level walkthrough for matching, filtering, enriching, importing, and activating a tradeshow file.
Open use caseTradeshow playbook
The prompt, commands, execution log, requirements, and results for the urgent tradeshow sprint workflow.
Open playbookTradeshow Import for Sheets
Fuzzy-match badge scans against Salesforce, auto-resolve 80%+, review exceptions in a real spreadsheet, and commit with campaign membership.
See how it worksFAQ
Should I enrich a tradeshow file before importing it into Salesforce?
Usually no. Match first, segment first, and enrich only the rows you plan to work. That keeps costs down and reduces noisy data.
How do I avoid duplicates when importing tradeshow leads into Salesforce?
Match the file against your existing account and contact context before import. If you skip that step, duplicates are almost guaranteed.
Should these records be Leads or Campaign Members?
In most event workflows they should become Leads while also being attached to the event campaign as Campaign Members so attribution and follow-up stay intact.
What does FoundryOps do in this workflow?
FoundryOps handles the operator layer: matching, ICP filtering, selective enrichment, Salesforce import support, and outbound activation. It does not resell data and it does not ask you to enrich the full file blindly.
What is the difference between the Salesforce guide, the use case page, and the playbook?
This guide is the short answer. The use case page explains the workflow in product terms. The playbook shows the full prompt, commands, and execution pattern.
Keep the conversation going
These pages are meant to help operators solve real problems. If you want the next guide, grab the low-friction option. If you need the implementation, not just the guide, book time.
Get the next guide when it ships
I publish architecture guides grounded in real implementations. No generic AI filler.
Use your work email so I can keep the list useful and relevant.
Need the implementation, not just the guide?
Book a 15-minute working session with Mike right on his calendar. Tooling, consulting, or a mix of both is fine.
Open Mike's calendarIf you want me to come in with context, leave your email and a short note before the call.