Most trade show leads are not lost at the booth. They are lost in the gap between an unstructured conversation and a structured CRM.
Field mapping is where that gap is either bridged or not — and it is the least glamorous, highest-leverage part of event lead capture.
The test a good event lead record must pass
One question decides whether your field mapping works:
Can someone who was not at the booth act on this record?
If the answer is no, the lead will be worked badly or not at all — regardless of how good the conversation was. The rep who had it is busy, forgets, leaves, or has 200 others.
Everything below follows from that test.
The core field set
Beyond name, email, company and title:
| Field | Type | Why it matters |
|---|---|---|
| Event name | Picklist | Attribution and ROI, and it must be controlled |
| Conversation date | Date | Day 1 and day 3 leads behave differently |
| Qualification summary | Long text | What was actually established |
| Next step agreed | Text | The single best predictor of progression |
| Budget indication | Currency / picklist | Filterable, unlike a note |
| Timeline | Date / picklist | Drives sequencing |
| Incumbent | Text / picklist | Displacement versus greenfield |
| Decision roles | Multi-select | Who else must be convinced |
| Lead source detail | Picklist | Booth, session, side event |
Nine fields. That is close to the practical maximum for reliable population at an event.
Why free text destroys value
The most common mapping error is dumping the conversation into a notes field. It feels responsible — nothing is lost. But free text is:
- Not filterable — you cannot list every lead with budget over €50k
- Not sortable — you cannot sequence by timeline
- Not reportable — it contributes nothing to pipeline analysis
- Not usable in automation — no routing, scoring or alerting can read it
A note saying "budget's around fifty grand, looking at Q1" contains real information that the CRM cannot use. The same facts in a currency field and a date field drive routing, forecasting and prioritisation automatically.
Structure is not bureaucracy. It is what makes the information actionable.
The picklist discipline
Event name must be a controlled picklist, not free text. Left open, a single event becomes:
Hannover Messe 2026
Hannover 2026
hannover messe
HM26
Hannover
Five values, one event, and no reportable attribution. Multiply that across a year of exhibiting and event ROI becomes unmeasurable — which usually means the exhibiting budget gets cut on instinct rather than evidence.
The same applies to timeline, budget band and incumbent where the option set is knowable.
The two tests for adding a field
Teams over-engineer this constantly. Before creating any field, ask:
1. Would this change what someone does next? If the answer is no, it is decoration. "Favourite colour of their laptop" is an extreme example, but "industry sub-vertical" often fails the same test.
2. Will it actually be populated? A field that is empty 80% of the time is worse than no field — it creates false confidence in reports and adds friction at capture.
Eight fields always filled beat twenty-five usually empty. This is the single most common failure in CRM design for events.
Sector-specific extensions
The core set covers most cases. Some sectors need specific additions:
- Medtech — device class, regulatory status, capital budget window
- Industrial — control system, protocol, project phase
- Logistics — volume, lanes, contract end date
- Energy — project capacity, grid status, permitting stage
- Fintech — regulatory status, data residency, certifications
Add sector fields deliberately, and only where they change the next action.
Mapping the conversation to the fields
The hard part is not designing the fields. It is populating them from a conversation that did not happen in field order.
Three approaches:
1. Rep fills a form during the conversation. Reliable structure, but the rep is typing instead of listening — and technical buyers notice immediately.
2. Rep fills a form after. Better attention, worse recall, and it requires a gap between visitors that busy booths do not have.
3. Capture the conversation, extract the fields afterwards. The rep engages fully, and the mapping happens automatically. This is what Confee does — the conversation becomes populated CRM fields without anyone typing during it.
Whichever you choose, the fields must exist before the event. Creating them afterwards means the first event's data is already lost.
Validation rules worth setting
- Event name required on any lead created during event dates
- Next step required before a lead can be marked qualified
- Owner required — unowned leads are unworked leads
- Email uniqueness check — catch duplicates at creation, not later
The pre-event checklist
- Core nine fields created and tested
- Event name added to the picklist before the show
- Sector-specific fields added if needed
- Validation rules active
- Duplicate matching configured on email
- Reps briefed on which fields matter most
- A test lead created end to end and inspected
That last step catches more problems than all the others combined.
The short version
Field mapping decides whether an event lead is workable. Use a controlled event picklist, structure the qualifying facts into real fields rather than notes, and keep the set small enough to be filled consistently.
If someone who was not at the booth cannot act on the record, the mapping has failed — no matter how good the conversation was.
Related reading:
- How to Sync Trade Show Leads to Pipedrive — a worked example
- Auto-Fill Salesforce and HubSpot From a Conversation — the enterprise CRMs
- Event Lead Scoring — using the fields once you have them
FAQ
What fields should a trade show lead have in the CRM?
Beyond contact details: event name as a controlled value, conversation date, qualification summary, next step agreed, budget indication, timeline, incumbent solution, and decision roles. The test is whether someone who was not at the booth can act on it.
Why should event name be a picklist rather than free text?
Free text destroys reporting. One event becomes several different strings, fragmenting any ROI analysis. A controlled picklist keeps values consistent so pipeline can be attributed properly.
What is the most common CRM mapping mistake for event leads?
Dumping the conversation into a single notes field. Free text is not filterable, sortable, reportable or usable in automation — a note about budget cannot drive routing the way a numeric field can.
How do you decide which fields are worth creating?
Two tests: would this change what someone does next, and will it be populated consistently? Eight fields always filled beat twenty-five usually empty.