Attribution you can defend
Event ROI built from firsthand notes instead of inferred touchpoints — what writing it down lets you claim, the math, and the limits stated honestly.
For field marketers & booth teams · sales managers · marketing ops · 3 min read · Updated July 10, 2026
There are two ways to answer “was the show worth it.”
The first is inferred attribution: export the badge scans, match emails against the CRM, run a multi-touch model, and present a number nobody in the room quite believes — least of all the reps who were there. Inference has its place, but for field events it’s built on the weakest possible input: a list of people who walked past a scanner.
The second is reading back what was written down. If every conversation was captured and labeled — in the moment, by the person who had it — then attribution isn’t modeling. It’s arithmetic.
What writing it down lets you say
With the interactions your team captured at a wrapped-up Event, these are plain statements of fact, each traceable to named people on named days:
How many conversations happened at the show. How many were with engaged decision makers or influencers. How many asked for a concrete next step, and how many of those follow-ups were completed inside the week. How many are now open pipeline.
Fill those four sentences from your own Event and compare them to what a badge export supports: a count of badges scanned. The difference isn’t polish — it’s that the first version survives questioning. Which conversations? Here are the names. Says who? The rep who talked to them, same day. What did we promise? It’s in the note.
Numbers you can trace back to firsthand notes don’t fall apart in a QBR.
The napkin math
The core Event economics need one division:
| Metric | Formula |
|---|---|
| Cost per conversation | budget ÷ conversations |
| Cost per qualified conversation | budget ÷ qualified |
| Goal attainment | qualified ÷ lead goal |
“Qualified” is whatever your labels say it is — that’s the point of designing them deliberately. Set the lead goal and budget on the Event during prep, and the denominator and target are fixed before the show, which keeps the math honest afterward.
Do this per Event, consistently, and the portfolio conversation changes: the regional show at $600 per qualified conversation earns a bigger booth next year; the flagship conference at $4,000 gets a hosted dinner instead. You’re managing events like a channel, with unit economics, instead of renewing sponsorships on vibes.
Where the numbers live
- In Athel — Reports. Activity by Event and time period: contacts created, cards snapped, notes recorded, emails sent, QR scans and unique visitors. This is the operational view — is capture actually happening, per Event, per rep.
- In Athel — the Event itself. The contact list with every interaction label, which is the qualified-conversation count and the roster behind it.
- In HubSpot — pipeline and revenue. Synced contacts arrive with Event list membership and association labels attached, so lists, reports, and revenue attribution run on segments built from what your reps actually captured: contacts labeled Decision maker at the fall show, not emails matched from a CSV. The plays cover building these views.
The limits, stated honestly
A playbook that oversells attribution becomes the thing it replaced. So, plainly:
- This is contribution, not causation. Your notes prove the conversation happened and what it was; they don’t prove the deal wouldn’t have closed anyway. No event attribution does. The difference is that your claim — “we had these qualified conversations, these follow-ups, this resulting pipeline” — is at least true.
- The notes are only as complete as the wrap-up. Uncaptured conversations don’t exist downstream. This is why the wrap-up ritual is a non-negotiable stage of the loop rather than a nice-to-have.
- Long cycles need patience. A March conversation that closes in November looks like nothing for eight months. What you wrote down in March is what lets you connect those dots later — but the dots connect at deal-close, not at wrap-up. Report conversations and follow-through now; claim pipeline when it exists.
- Buying committees are plural. One deal may trace to several people across several Events. That’s not noise to deduplicate — it’s the actual shape of B2B buying, and per-person, per-Event notes are what make it visible instead of collapsing it into a single “first touch.”
Attribution is the Prove stage — the last one in the loop. It only works if the stages before it ran. Which brings us to the ritual that makes sure everything actually got written down: the wrap-up.