Your conference ROI lives in one number: contact-activation rate.
Badge scans measure volume and pipeline shows up months late. The number that decides whether a trip paid off is the share of new contacts you followed up with inside 72 hours.
The Tuesday after the conference
The Tuesday after a conference, someone always asks how it went. The answer is almost always a count. Triple-digit badge scans. A stack of cards thick enough to need a rubber band. A few people who said "let's grab time next month."
Nobody asks the follow-up question.
It's the only one that matters, though: how many of those people have heard from you since? By Friday, most of that stack is anonymous. The scans are rows in a spreadsheet with no memory attached, and the cards carry a name and a title while whatever got said in the coffee line is already gone. Whether the trip produced anything was decided in the 72 hours after you flew home, and almost nobody measured it.
Contact-activation rate, defined
Call it contact-activation rate. It's the share of new contacts from an event who got a meaningful follow-up from you within 72 hours of meeting them.
The math fits on a napkin. Count every new person you captured at the event, whether by scan, card, or note. That's the denominator. Count the ones you followed up with inside 72 hours. That's the numerator. Divide.
"Meaningful" carries most of the weight, so be strict about it. A LinkedIn connect request with no note doesn't count. Neither does a mail-merge "great meeting you" blast. A follow-up counts when it references something specific from the conversation and proposes a next step, even a small one.
And the window isn't arbitrary. Seventy-two hours is roughly the stretch where both of you still remember the conversation, which we covered in [the 72-hour memory cliff](/articles/72-hour-memory-cliff/). After that, you're writing to a stranger who happens to have your card.
The formula
Contact-activation rate = new contacts who got a specific, next-step follow-up within 72 hours, divided by total new contacts captured at the event. Everyone you scanned goes in the denominator, including the ones you'd rather forget.
Why is conference ROI so difficult to measure?
Because the standard frameworks count what's easy to count, and the easy numbers all sit at the wrong end of the timeline.
Badge scans and cards collected measure how much of the room you touched. They say nothing about what you did next. A high scan count is fully compatible with zero follow-ups, and on plenty of trips that's closer to the truth than anyone admits in the recap.
Pipeline attributed in a CRM has the opposite problem. It's real money, but it shows up months later, it gets credited to whichever touchpoint the attribution model favors, and by the time it lands you can't change anything about the trip that produced it. It's a verdict, not a gauge.
Contact-activation rate sits in the gap. You know it within a week of flying home. It's entirely in your control. So it's upstream of every pipeline number you'll eventually report, because a contact who never heard from you can't turn into a deal.
Metric
What it counts
When you know it
Can you still change the outcome?
Badge scans
Contacts touched, including passersby
Day of
No. It only measures volume.
Cards collected
Contacts touched who handed you something
Day of
No. Same problem, better paper.
Pipeline attributed
Deals the CRM credits to the event
Months later
No. The window has closed.
Contact-activation rate
New contacts who got a specific follow-up within 72 hours
Within a week
Yes, while the 72 hours are open.
What each common conference metric actually measures, from the attendee's side.
What attendees keep asking
Look through Reddit threads, LinkedIn posts, Quora answers, or the comments under conference-ROI explainers on YouTube and the same question keeps coming back from the attendee side: how do I tell whether this trip was worth it? Google's People Also Ask box still surfaces "why is ROI so difficult to measure?" as an open question.
Much of the published ROI advice answers something else. It's written for exhibitors and organizers, so it counts booth traffic, leads per dollar, and sponsorship value. Useful if you paid for a booth. If you paid for a ticket and a flight, it's noise.
The attendee's job is narrower. You go to start relationships. The metric should measure whether relationships started, and one starts the first time you write back with something specific.
Twenty conversations versus two hundred scans
Take two people at the same three-day event.
The first has 20 real conversations. Names, context, one thing each person cares about. By the middle of the next week, 8 of them have a follow-up that picks up the thread. Contact-activation rate: 40%.
The second scans 200 badges at booth lines, happy hours, anywhere someone stood still long enough. They send 10 follow-ups, to the handful they can still place. Contact-activation rate: 5%.
On raw count the second person wins, 10 to 8. That's the trap. The 8 follow-ups continue a conversation with someone who remembers the person writing. The 10 are thinner, a few lines to people who barely remember the booth. And the other 190 scans sit in a spreadsheet, looking like pipeline in the trip report while producing nothing at all.
The rate exposes what the count hides. Five percent says the capture ran far ahead of the follow-up and most of the room was wasted effort. Forty percent on a small denominator says the trip was spent on people the attendee could actually follow through with.
Attendee A
Attendee B
Approach
20 real conversations
200 badge scans
Followed up within 72 hours
8
10
Contact-activation rate
40%
5%
Contacts left dormant
12
190
Illustrative scenario to show the arithmetic, not survey data.
What changes when you track it
You don't need new software to get the number. Pull the new contacts from the event, whether that's your card pile, a scanner export, or your phone's contacts sorted by date added. Search your sent mail and messages for each name. Count the ones with a specific follow-up inside the window. For most trips that takes less time than writing the recap.
The number changes behavior fast. You stop scanning people you'll never write to, since every idle scan drags the rate down. You block follow-up time before the trip, the evening of each event day and the morning after you land. And you capture context in the moment, because a follow-up without context is just a slower cold email.
We haven't seen a credible published benchmark for attendee-side activation, so don't borrow one. Measure this trip. Beat it on the next. That comparison is honest, and it's the one you control.
Where the rate gets won or lost
The rate is decided in two places: the moment you meet someone, and the hours right after. Most capture tools stop at the first and treat the saved card as the finish line.
Met was built for the stretch in between. Event Mode keeps the room captured while you keep talking, so the context lands next to the name instead of evaporating somewhere between the expo hall and the hotel. The follow-up draft starts from the context you captured Met's in-app follow-up drafts are generated from the context notes users add after a scan, where they met, the event, what was discussed, tags, and availability, combined with the captured contact details, so each draft reflects the specifics of that encounter rather than a generic template., which is the difference between a message that counts toward your rate and one that doesn't. Contacts stay in your own iCloud, not on someone else's server.
None of that sends the follow-up for you. It just removes the reasons a 40% trip turns into a 5% one.
Track one number after your next event. Make it this one.
Get Met before your next event and raise your activation rate.
Met is built around the 72 hours after you meet someone: Event Mode captures context while the conversation is still happening, follow-ups start from what was actually said, and your contacts stay in your own iCloud. No ads, no data sold, no nags.
