The event is over. The booth was busy, the scan count looks good, and someone has opened the budget review asking the awkward question: what was it worth?
There is no universal good event ROI percentage. Calculate yours with a declared return, a fully loaded cost base, a fixed measurement window, and a consistent attribution rule. Then show lead quality, follow up, progression, and influenced pipeline separately. A flattering scan total should never get to impersonate business value.
An event earns its place when the record can tell someone what happened next, not merely how many people passed through. The formula is easy. Deciding what belongs in it is the work.
Name the return before you calculate it
Before dividing anything, decide what “return” means for this event. It might be ticket or sponsorship revenue, gross margin, influenced pipeline, or a declared strategic outcome. Those measures are not interchangeable. If the definition changes halfway through the report, the result is not a comparison. It is a mood.
For a financial result, use:
((return - cost) / cost) x 100
A $50,000 event that returns $75,000 produces 50% ROI under that definition, as Whova’s example shows. If you are measuring revenue, call it revenue. If the decision depends on margin or the cost of goods, use the relevant margin instead of presenting revenue as profit.
Put the time boundary beside the return definition. A ticketed event may have a useful immediate revenue number. A business event with a long sales cycle may not. Set the window before looking at the result, and record the baseline from before the event so the next event can be compared using the same method. Guidebook’s explanation treats the time boundary and baseline as part of the analysis, not optional polish.
An event can also have a strategic return, such as customer engagement, community growth, or awareness. Keep that outcome visible as its own result. Do not turn it into a made up dollar amount and place it in the same total as closed revenue.
Put the real cost in the denominator
The denominator is where flattering event reports usually get their haircut. Include the venue or booth, travel, lodging, food and drink, technology, marketing, swag, staff time, follow up work, and analysis. Cvent’s cost list makes the point plainly: the event invoice is only one part of what the event consumed.
Separate direct costs from indirect costs so the report shows what is easy to change. Staff time and analysis after the event belong in the main view when you can measure them. Opportunity cost is different. If it is too uncertain to defend as a precise amount, keep it out of the primary denominator and show it as a scenario instead.
That gives the budget review two honest views. The main result answers what this event cost under a declared method. The scenario answers what changes if the team values that time elsewhere. Neither belongs hidden inside one neat percentage.
Write the cost rule down before comparing events. One report that counts staff time and another that ignores it are not comparable, even if both use the same formula. Umbrex’s cost guidance recommends separating direct and indirect costs and using a consistent method across historical or similar events.
Treat capture as the beginning of value
Attendance, registrations, and scans prove that something happened. They do not prove that the right people were there, that anyone understood the conversation, or that a useful next action exists.
Calculate qualified lead rate as the number of leads that meet your ideal customer profile divided by total leads captured, multiplied by 100. Then check progression into meetings, opportunities, or another agreed sales stage. A smaller set of qualified contacts with an owner and a next action can be more useful than a large scan total that nobody can identify a week later.
That is why the capture path matters. If you are choosing an exchange before worrying about ROI, choose an event lead capture path that preserves the context your later review needs.
Zapped serves one narrow part of this interaction. A Zapped card can be shared by QR code, NFC tap, or link, and the recipient opens it in a normal browser without installing an app or creating an account. That removes a piece of recipient friction at the moment of exchange.
The useful record still needs the event name, event type, contact qualification, owner, and next action. A smooth exchange is a better start. It is not a verdict.
Measure the handoff, not just the handout
The first serious question after capture is simple: did anyone do the next thing? Track the rate of contacts followed up, the response rate, the event name, the event type, and the next lifecycle stage. Integrate’s ROI measures use follow up within 48 hours as a useful example, not a universal promise for every event or sales cycle.
This is where a busy event can expose a weak process. If scans rise while qualified lead rate, response, or progression falls, buying a larger booth is probably not the first fix. Change the handoff. Give each useful contact an owner and a next action, then revisit the record after the sales cycle has had time to move.
Zapped’s analytics for each card can help review the exchange itself. The documented history is 60 days on Free, 185 days on Starter, and 365 days on Professional, so match the history window to the review you intend to run. Zapped’s statistics guidance documents those limits. The analytics can show that the card was used. They cannot prove that a contact became revenue.
Give credit according to the question
Attribution is not a magic setting that reveals one true event number. It is a rule for answering a particular question.
First touch asks whether the event introduced the buyer. Lead touch asks whether it helped create a qualified lead. Last touch asks whether it was the interaction before conversion. A W shaped model gives credit to several important points in the journey.
Bevy’s attribution guide lays out these models because each answers something different. Pick the rule that fits the decision. If the question is acquisition, first touch may help. If the question is conversion or closing, another model may be more informative. If the event helped a deal progress alongside other interactions, label that influence rather than claiming the event caused the whole result.
Keep the model fixed when comparing events. Changing attribution after seeing the outcome is how a report grows a convenient answer. If stakeholders need different views, show them as separate declared views, each with its own question.
Wait for the sales cycle, then make the call
Do not force a final ROI verdict while the evidence is still moving. When closed revenue is not ready or the CRM record is incomplete, publish a staged scorecard. Show capture, qualified lead rate, owner and next action, follow up rate, response, progression, and pipeline influenced by the event. Put a date window and a data limitation beside each measure. If you estimate lead value, label the estimate as an assumption and schedule a later review for opportunities that may close weeks or months after the event.
The final decision needs a consistent historical or similar event baseline. Repeat or scale when the declared threshold and downstream evidence hold. Change the handoff when activity outruns quality. Pause when the cost is not recovered and the strategic outcome remains unproven. Mark the result provisional when the sales cycle is still open.
In the monthly billing view checked in August 2026, Zapped lists monthly plan prices: Free at $0, Starter at $14 per month, and Professional at $49 per month. The question is not whether card analytics can stand in for event ROI. They cannot. The question is whether a direct exchange layer and its available history window fit the measurement job you actually defined.
That keeps the tool in its lane and makes the event record more useful. A scan is evidence of capture. A qualified contact with an owner, a response, and progression is evidence of movement. Revenue or a declared strategic result is the return you chose at the start.
The budget review has a cleaner ending now. If the threshold holds and the chain is intact, repeat the event. If the event was busy but the handoff broke, fix the handoff before buying more attention. If costs are not recovered and the strategic case is still unproven, pause. If the pipeline is alive but not mature, keep the result provisional and return to the scorecard on the date you set.
