We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.
The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ...
Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.
Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.
Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.
Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet.
Lessons from International Confex on turning event data into decisions leaders can stand behind.
A couple of weeks ago, I hosted my first event since joining Explori, at International Confex in London.
Not my first event 'ever', but my first time being the person responsible for the whole thing: the invitations, the logistics, the run of show, the "will anyone actually show up?" nerves, and then the part that matters most, sitting in a room with people who do this at scale and hearing what's really going on.
Our activation had three connected parts:

The "why" behind all of it was simple.
Event leaders aren't short of data. They're short of air cover.
Across the roundtable, the panel, and the booth conversations, the most revealing moments weren't about dashboards or "which metrics should we track?" They were about pressure.
Pressure to justify spend in tougher budget cycles. Pressure to defend decisions in rooms where not everyone believes in the value of events. Pressure to prove an event "worked" beyond a handful of numbers, or a few anecdotes.
And what stood out most to me was the candour. Senior leaders openly admitted where their measurement still feels fragile, where systems don't connect, and where reporting still feels reactive. That honesty matters, because it's easy to assume other teams have "solved measurement" and you're the only one struggling.
That's not a tooling issue. It's a maturity issue.
It also reinforced something bigger for me: the industry does not need more event reporting. It needs event intelligence: a way of measuring events that is comparable, decision-useful, and strong enough to travel across the business. That's a higher bar than post-event feedback. But it's also the standard events will increasingly be held to.
That phrase landed because it describes the lived reality.
Most teams can produce metrics. The challenge is whether those metrics actually explain what changed because of the event.
The real gap isn't always missing data. It's missing signals about what people experienced, felt, and decided as a result of being there.
Without that human layer, reporting tends to default to activity numbers:
Those numbers are useful, but they rarely answer the question leadership actually cares about: Did the event move anything meaningful? Did brand trust increase? Did brand perception shift? Did the conversation progress?
When that signal is missing, teams fall back on operational explanations:
Those issues matter, but they're symptoms of a deeper gap: the story between the interaction and the outcome is invisible.
What makes measurement credible is being able to show the movement that happens between attendance and revenue, such as the shifts in sentiment, intent, and relationships that events are uniquely good at creating.
Once that layer is visible, the rest of the reporting becomes much easier to defend.

When the group was asked who has someone in their team that owns measurement, only a small number did.
Where organisations had made progress, it wasn't just a better dashboard. It was someone taking ownership of the framework, the definitions, and the narrative.
In practice, ownership looks like:
Without that, measurement becomes inconsistent. And inconsistent measurement rarely stands up to scrutiny.
Different stakeholders want different answers, and the biggest mistake is trying to serve everyone with a single, sprawling report.
It sounds efficient. It usually isn't. What you end up with is a report that tries to be complete instead of one that informs future event strategy.
One practical tip that stuck with me: keep leadership reporting to a small number of headlines with a clear call to action, otherwise people switch off.
A second tip: separate "decision reporting" from "performance analysis." Leadership often needs the first. The second is what enables you to improve.
Common attribution models can undervalue events, especially first-touch and last-touch models that over-credit digital channels.
What felt more useful were leading indicators that reflect how events actually create value:
Events teams shouldn't be judged purely on closed revenue. They're often responsible for movement, not closure.
I also heard a practical warning: if you only measure lagging outcomes, you create the wrong incentives. Teams will optimise for what is easiest to count, not what is strategically valuable.

It was striking how often leadership is swayed by specific customer soundbites and anecdotes, especially when paired with the right quantitative context.
The best examples weren't long case studies. They were short moments that made impact real. A direct quote. A before-and-after shift. A specific "this is what changed in our thinking."
Used well, qualitative evidence does two jobs:
Response rates came up as a practical constraint, but also a solvable one.
The best practices were consistent:
One extra nuance I took away: response rate tends to follow trust. If attendees believe the feedback loop is real, they respond.

If I had to summarise Confex in one line, it would be this:
Event data isn't scarce. What's scarce is the number of credible signals being tracked to measure what actually moved the needle.
And if events are going to shape growth and strategic direction, not just "activity reporting," measurement has to step up, and it has to hold under pressure.
That means doing the unglamorous work: agreeing definitions, assigning ownership, designing leading indicators, capturing the human signal between interaction and outcome, and telling a compelling story that stands up to leadership scrutiny. That is what separates the events function shifting from an operational delivery function to a strategic growth lever for the business.
Explori operationalises measurement methodology proven across thousands of events. The questions, the framework, the benchmarks, all built in, all defensible to leadership.