What Did That Conference Actually Bring In?

Key takeaways

• Count the full cost, not only the sponsorship fee.
• One list per event, built on the day, is the whole foundation.
• Influenced pipeline is the honest headline; sourced pipeline is the strict version.
• Measure over a full sales cycle, and read early signals in the meantime.
• Subtract the accounts that were already in a deal before the event.

View full size

The booth cost €40,000. The team came back with 300 badge scans, a dozen good conversations and a cold. Nine months later a deal closes with a bank whose head of operations stopped by on day two. Was the event worth it?

Most teams can't say, and the reason is rarely the maths. It's that the data needed to do the maths was never recorded in a way anyone can query.

Why event ROI is hard

Events break the assumptions most marketing reporting relies on.

• There's no click. Nobody arrives with a UTM. Contacts are imported from a scanner app, and the CRM marks them as an offline source.
• The touch is early. In enterprise B2B an event often starts or revives a conversation that closes months later, long after the campaign report was due.
• Many people touched the deal. By the time it closes, the account has seen emails, ads, a demo and three sales calls. Every one of them can claim the win.

So the answer has to be built deliberately, before and after the event.

Step 1: Count the full cost

Sponsorship is the visible line. The real cost is larger:

• sponsorship or ticket fees,
• booth design, shipping and printed material,
• travel and accommodation,
• the days your team spent there instead of doing something else,
• giveaways, dinners and side events,
• follow-up work, such as a sequence or an outbound sprint aimed at the attendees.

Write the total down in one currency before you look at any results, so the results can't influence what you decide to count.

Step 2: Put everyone on one list

This is the step that makes everything else possible. Within a day of the event, create one list in your CRM with every person you met: badge scans, meetings, dinner guests, people who visited the booth and later booked a call. Name it after the event and date.

If your CRM supports it, also set a contact property such as "Event attended" so the information survives if the list is changed later. Don't rely on the scanner app's export sitting in somebody's downloads folder.

Step 3: Count influenced and sourced pipeline

With the list in place, two numbers are easy to calculate:

• Influenced pipeline: the value of deals created after the event that have at least one contact from the list.
• Sourced pipeline: the value of deals whose first recorded touch was the event.

Influenced pipeline is the fairer headline for events, because events usually accelerate or open conversations rather than create brand new leads. Sourced pipeline is the stricter number, and it will be much smaller. Report both, and say which is which; influenced vs sourced pipeline explains the difference in detail.

Track won value the same way. With a long sales cycle, won revenue will lag, so report pipeline first and revenue later.

Step 4: Remove what would have happened anyway

Some of the accounts at your booth were already in a deal before the event. Counting their pipeline as event pipeline flatters the event.

Split the influenced deals into two groups: deals created after the event, and deals that already existed and were touched by an attendee. The first group is the event's new pipeline. The second is acceleration, which is real and harder to value; report it separately as "open pipeline touched".

If you go to the same event every year, compare this year with your usual range for the same period without the event. That's the closest thing to a control group most teams have.

Step 5: Report one number, and compare it fairly

The number leadership can compare across channels is pipeline per unit spent:

pipeline per unit spent = influenced new pipeline ÷ full cost

A €40,000 event with €360,000 of new influenced pipeline produced 9 times its cost in pipeline. That's comparable with the same ratio for LinkedIn ads or a partner programme, if you calculate those the same way.

When deals close, add cost per won deal and won revenue per unit spent. Judge the event on these only after a full sales cycle has passed.

Common mistakes

• Counting badge scans as results. Scans measure booth traffic, not buying intent.
• Comparing influenced pipeline from events with sourced pipeline from ads. Use the same definition for every channel.
• Judging too early. A three-month review of an event in a twelve-month cycle measures follow-up speed, not the event.
• Forgetting the follow-up cost. If a sequence and an outbound sprint followed the event, their cost belongs in the total.

Quick Q&A

How do you calculate event ROI?

Subtract the full cost from the won revenue the event influenced (or its gross margin) and divide by the cost. Until deals close, report influenced pipeline divided by cost instead.

What is a good ROI for a B2B event?

It depends on deal size and win rate. As a rule of thumb, compare pipeline per unit spent with your other channels; an event that produces less pipeline per unit spent than paid search needs another reason to justify it.

How long after an event should I measure ROI?

Read early signals such as meetings and new deals within four to six weeks, and judge pipeline and revenue after one full sales cycle.

How do I track event leads in HubSpot?

Import attendees into a static list named after the event and set a contact property for the event. Deals with a contact on the list are the event's influenced deals.

Should sponsorships be measured like events?

Yes. Treat the people you met or who engaged with the sponsorship as the list, and count the deals they appear on.

Keep reading

• Event and sponsorship ROI in HubSpot: counting deals from an attendee list automatically.
• Influenced vs sourced pipeline: which number to report when.
• HubSpot attribution reports explained: what HubSpot's own reports can and can't do.
• Did your campaign actually work?: judging any action against a usual range.