Getting trade fair leads into your CRM without going through Excel

You collected 200 badges in three days. Now they’re photos, business cards and a CSV from the fair app. The problem isn’t capture: it’s that between that pile and a clean CRM record — with event tag, owner and dedup sorted — there are usually five lost days and a couple of arguments about who calls whom.

In short:

• Trade fair leads into the CRM almost always fail in the last metre: from capture to assigned record, not in the collection itself.
• Three non-negotiable patterns: unique event tag, a dedup rule on email/domain, an owner assigned before the fair.
• The event tag (e.g. fair:SPS-Italia-2026) is what lets you compute per-event ROI without polluting your other channels.
• Excel works below a certain volume. Above 3 events a year and hundreds of contacts it becomes the bottleneck — a volume call, not a religion.
• Linkly automates the badge→CRM chain with event tags, enrichment from 30+ data sources and CRM activation right at the fair.

The real breaking point isn’t capture

Every sales team knows how to scan a badge. Almost none has decided what happens in the 5 minutes after. The lead lands in a fair app, a Google Sheet, a photo on a rep’s phone. From there to the CRM there’s a manual jump someone has to make — usually “Monday”.

From our experience with clients at fairs like SPS Italia, the time between event and first post-fair contact in Italian manufacturing is measured in days, not hours. Every lost day is a day the prospect spends talking to a competitor.

If you want the foundational part first, start with what Linkly is and the comparison with Excel/CSV export.

Pattern 1 — The unique event tag

Every lead captured at the fair must enter the CRM with a unique event tag, applied automatically at capture. Not “fair”, but fair:SPS-Italia-2026. Add the channel (fair) and, if useful, the stand or the day.

What it’s actually for:

• Per-event ROI: filter the campaign and see pipeline generated by a single event.
• Clean reports: fair leads don’t pollute inbound or outbound metrics.
• Targeted follow-up: run different sequences per event without touching other contacts.

If you apply the tag by hand afterwards, you’ll forget it on 30% of records. Automate it at the source.

Pattern 2 — The dedup rule

After every fair, duplicates show up: the prospect was already a customer, or you met them last year. You need a dedup rule decided in advance:

1. Primary match on email.
2. Secondary match on company domain + first/last name.
3. On a match: don’t create a new record, enrich the existing one and add event tag + conversation note.

HubSpot, Salesforce and Pipedrive all have dedup mechanisms, but they only work if incoming data is consistent. A badge with just a name + company won’t match reliably until you enrich it with the real email. That’s where automatic enrichment (email, phone, LinkedIn, company info from 30+ data sources) changes the maths of dedup.

Pattern 3 — The owner assigned before the fair

A lead with no owner on return is a lead nobody calls. Assignment has to be decided before the event, with a clear rule:

• by territory (who covers that geography),
• by segment/ICP (who runs that vertical),
• or by who had the conversation at the stand.

Write the rule, don’t improvise it. At the Tuesday-evening debrief no one wants to negotiate who gets lead number 87.

How this maps to HubSpot, Salesforce, Pipedrive

The principle is identical across all three; only the field names change.

Concept	HubSpot	Salesforce	Pipedrive
Event tag	Custom property/List	Campaign + Lead Source	Label + custom field
Dedup	Duplicate management	Matching + Duplicate Rules	Merge duplicates
Owner	Contact owner + rotation	Assignment Rules	Deal/person owner

If capture already happens inside a flow that writes to the CRM with these fields populated, Sales Ops touches nothing by hand. If it happens outside (fair app, Excel), someone will have to remap everything — and that’s where time is lost and duplicates are born. See the comparison with mobile CRM to understand where manual mobile capture holds and where it doesn’t.

When Excel is perfectly fine (and when it isn’t)

Let’s be honest: if you do one fair a year and collect 20 badges, a clean Excel with tag and owner columns is more than enough. You don’t need infrastructure.

Excel stops working when:

• you do 3+ events a year with hundreds of contacts,
• you have to enrich partial badge data,
• you have dedup and assignment rules nobody applies consistently by hand,
• you need a per-event report within days, not a raw CSV.

It’s a volume threshold. The 40Factory case study is an example of an Industrial IoT company where the badge→CRM chain has to run at scale, not by hand.

The Linkly pattern, in one line

Linkly is a SaaS of 6 AI agents orchestrated by a dedicated human consultant: capture (OCR on badges/QR), enrichment from 30+ sources, qualification, activation into the company CRM with an event tag, email follow-up and an executive report. The badge→CRM chain becomes automatic, no Excel step.

Next step

If you want to see how event tags, dedup and owner land in your CRM, book a demo or read what Linkly is. No pressure: if you do one fair a year, a good Excel is still the right answer.