Pipedrive is built around deals moving through a pipeline. That design is a strength for outbound sales and an awkward fit for trade show leads, which arrive in bulk and vary wildly in quality.
Getting event leads into Pipedrive well is mostly about one decision, made correctly and consistently.
The Leads Inbox decision
Pipedrive gives you two places to put a new contact:
Leads Inbox — a holding area outside the pipeline. Leads here do not appear in forecasts, do not contribute to pipeline value, and generate no automatic activity reminders.
Deals — inside the pipeline, forecastable, with stages and activities attached.
The common failure after a trade show is dumping all 200 scans into Leads Inbox. They sit there. Nobody is accountable, nothing reminds anyone, and within three weeks the inbox is background noise nobody opens.
The rule that works:
- Unqualified scans → Leads Inbox, worked or discarded deliberately
- Qualified conversations → straight to a Deal, with Person and Organization attached
That decision has to be made at capture, not later. Which means the qualification has to have been captured.
Structuring the Deal
For a qualified event lead, create:
- Person — the individual you spoke to
- Organization — their company
- Deal — the opportunity, linked to both
- Activity — the agreed next step, with a real date
That last one matters more than it looks. A Deal with no scheduled Activity has nothing driving it forward. Pipedrive's whole model assumes an open activity exists; a Deal without one is invisible to the daily workflow.
Custom fields worth creating
Pipedrive's defaults have no concept of an event. Add these as custom Deal fields:
| Field | Type | Why |
|---|---|---|
| Event name | Single option | Makes event ROI measurable |
| Conversation date | Date | Distinguishes day 1 from day 3 leads |
| Booth / session | Text | Useful for multi-location exhibitors |
| Qualification summary | Long text | What was actually said |
| Next step agreed | Text | Prevents vague follow-up |
Event name as a single option field rather than free text matters — free text produces "Hannover 2026", "hannover", "Hannover Messe" and no reportable data.
Getting data in
Three routes, in ascending order of usefulness.
CSV import. Works, and is the standard badge-scanner path. But it lands post-show, has no qualification, and creates duplicates freely.
Zapier or Make. Pipedrive has solid support in both. A form or scanner triggers a zap that creates the Person, Organization and Deal. Better — near real time — but only carries the fields the source captured, which for a badge scanner is contact details only.
API. Pipedrive's REST API creates and updates all objects directly. This is the route for anything that captures the conversation itself and needs to write structured qualification into custom fields.
The pattern that works best: contact details from the badge scan, qualification fields from the conversation, both written to the same Deal before the rep speaks to the next visitor. That is the model Confee is built around.
The duplicate problem
Trade show attendees are frequently already in your CRM — from a webinar, a download, a previous event, an outbound sequence.
Importing without matching creates a second Person record, splitting the history. Whoever picks up the follow-up sees a blank slate and opens with "great to meet you" to someone who has been in a nurture sequence for eight months.
Match on email before creating anything. Where a bulk import has already happened, use Pipedrive's Merge duplicates under the Person and Organization lists to clean up — and do it immediately, not next quarter.
Pipeline design for event leads
A frequent question is whether event leads need their own pipeline. Usually no — a separate pipeline fragments reporting and gets abandoned.
Better: use the main pipeline with the event captured as a custom field. That way event-sourced deals are comparable with every other source, which is what makes ROI measurable.
If your event leads genuinely need different stages — long capital cycles, for instance — that is a legitimate reason for a second pipeline. Volume alone is not.
Post-show workflow
- Import or sync within 24 hours. Momentum decays fast.
- Deduplicate immediately, before anyone contacts anyone.
- Triage into Deals versus Leads Inbox based on captured qualification.
- Assign an owner to every Deal — unowned deals are unworked deals.
- Schedule the first Activity on every Deal, with a real date.
- Set the Event field on all of them, so ROI is reportable later.
Steps 4 and 5 are where most event follow-up quietly fails.
Measuring event ROI in Pipedrive
Once the Event custom field is populated consistently, filter Deals by it and you can report:
- Deals created per event
- Total pipeline value generated
- Conversion rate versus other sources
- Average deal size from events
- Time to close from event-sourced deals
That is the analysis that decides whether to exhibit again — and it is impossible without the field being set at creation.
The short version
Pipedrive rewards structure. Decide at capture whether a lead is a Deal or an inbox item, attach Person and Organization, always schedule an Activity, and set a standardised Event field.
The single highest-value change most teams can make: stop dumping badge scans into Leads Inbox and hoping.
Related reading:
- Auto-Fill Salesforce and HubSpot From a Conversation — the equivalent for those CRMs
- CRM Field Mapping for Event Leads — designing the field structure
- Voice to CRM — how conversations become structured records
FAQ
How do you get trade show leads into Pipedrive?
Through Leads Inbox for unqualified contacts, or directly as a Deal when the conversation qualified. Pipedrive is deal-centric, so anything in Leads Inbox is outside the pipeline and excluded from forecasting.
Should event leads go to Pipedrive Leads Inbox or straight to a Deal?
It depends on qualification. Unqualified scans belong in Leads Inbox; conversations with real qualification should become Deals immediately, since inbox leads generate no activity reminders or forecast contribution.
What custom fields should Pipedrive have for trade show leads?
Event name (as a single-option field, not free text), conversation date, booth or session, qualification summary, and the specific next step agreed.
How do you avoid duplicates when importing event leads to Pipedrive?
Match on email before creating anything, and use Pipedrive's merge duplicates feature after bulk imports. Attendees are frequently already in the CRM, and parallel records split the history.