Whova | Event Stats Dashboard

Cross-event Analytics

Cross-event Analytics

Turning year-over-year event data into insights and timely actions for recurring event organizers.

Whova | Event Stats Dashboard

Cross-event Analytics

Turning year-over-year event data into insights and timely actions for recurring event organizers.

Whova | Event Stats Dashboard

Cross-event Analytics

Turning year-over-year event data into insights and timely actions for recurring event organizers.

Whova | Event Stats Dashboard

Cross-event Analytics

Turning year-over-year event data into insights and timely actions for recurring event organizers.

PLATFORM

Event management dashboard (admin)

Event management dashboard (admin)

TIMELINE

Q2 2025 - Q3 2025

Q2 2025 - Q3 2025

TEAM

1 Product Manager, 2 Engineers

1 Product Manager, 2 Engineers

Cross-event Analytics helps organizers compare event performance, understand what changed, and take action.

Cross-event Analytics helps organizers compare event performance, understand what changed, and take action.

Cross-event Analytics helps organizers compare event performance, understand what changed, and take action.

Whova already provided organizers with detailed reports on registration, attendee demographics, and engagement. But for organizers running recurring events, comparing performance meant navigating between different event dashboards, exporting data, and building comparisons manually.

I led the end-to-end design of the first release, from data visualization and report structure to contextual recommendations.

I led the end-to-end design of the first release, from data visualization and report structure to contextual recommendations.

I led the end-to-end design of the first release, from data visualization and report structure to contextual recommendations.

Working with PM and engineering, I focused on simplifying comparisons across 10+ metrics, making insights easier to share, and developing a strategy for surfacing relevant next steps throughout the event lifecycle.

Working with PM and engineering, I focused on simplifying comparisons across 10+ metrics, making insights easier to share, and developing a strategy for surfacing relevant next steps throughout the event lifecycle.

Problem

Problem

Problem

Comparing two events meant doing twice the work.

Comparing two events meant doing twice the work.

Even for a single event, organizers had to navigate multiple reports to find the information they needed. Comparing events added another layer of manual work, especially when preparing performance report for leadership.

EVENT STATS ACROSS DIFFERENT FEATURES

The opportunity went beyond comparison.

The opportunity went beyond comparison.

As I worked through the requirements, I saw three layers of opportunity. Together, these would make Whova more valuable throughout the recurring event lifecycle.

Existing behavior

New Value

Scoping

Scoping

Scoping

What was worth comparing in the first release?

With data spread across the platform, bringing everything into one report wasn't realistic or necessarily useful. Working with the PM, I prioritized 10+ core metrics using organizer interviews, existing requirements, and frequently exported reports.

We focused on three areas:

01

Registration

Registration

Are tickets selling better?

Gross/net sales

Tickets, add-ons sold

Whova contributed revenue

Registration sources

02

Attendee demographics

Who is coming?

Unique attendees

Returning attendees

Attendee categories

Industries

Affiliations

Locations

03

Event engagement

Are attendees participating more?

Session RSVPs vs. check-ins

Session feedback

Scoping

Scoping

Scoping

Designing with real constraints

Designing with real constraints

Before exploring layouts, I aligned with engineering on what we could realistically support. These constraints pushed me toward a more focused, scalable reporting experience.

01

Charting

Google Charts library

→

DESIGN IMPLICATION

Use existing chart types instead of custom visualizations.

02

Historical data availability

No past snapshots

→

DESIGN IMPLICATION

Compare event-level results rather than day-by-day trends.

03

Performance cost

Loading all metrics at once is costly

→

DESIGN IMPLICATION

Prevent having all metrics on one page

01

Charting

Google Charts library

→

DESIGN IMPLICATION

Use existing chart types instead of custom visualizations.

02

Historical data availability

No past snapshots

→

DESIGN IMPLICATION

Compare event-level results rather than day-by-day trends.

03

Performance cost

Loading all metrics at once is costly

→

DESIGN IMPLICATION

Prevent having all metrics on one page

Design decision 1

Design decision 1

Design decision 1

Organizers already compare years, by hand.

How might we make nuanced constraints feel lightweight to configure?

How might we make comparing events faster without overwhelming organizers with data?

How might we make comparing events faster without overwhelming organizers with data?

The initial requirement was to show all metrics on one page. But once I mapped everything into Whova's admin layout, the report became difficult to navigate. Engineering also confirmed that loading all metrics at once would be costly.
I explored three directions:

Full report

❌

Everything visible, but too much scrolling and higher loading costs.

Tabbed report

Picked

✅

Keeps related metrics together, with room to add more later.

Metric drill-down

❌

More focused, but adds navigation and hides relationships between metrics.

Design decision 1

Design decision 1

Design decision 1

DATA PRESENTATION

Choosing the right comparison for each metric
Choosing the right comparison for each metric

Not every metric needed the same treatment. I looked at what organizers were trying to understand and chose the presentation that made each answer easiest to find.

With the review steps set to live in the modal, I moved into designing the flows. The review flow had to work differently for the two AI-assisted cases, as the maps had different levels of information to work with:

  1. Color/size maps → Booths can be group booths by colors/sizes; organizers can assign groups to tiers in bulk.

  2. Numbers-only maps → no preliminary group suggestion; organizers assign booths individually.

The two criteria I designed against:

  • One decision at a time — every step asked for the smallest ask that moved the assignment forward.

  • Flexibility at the right moments — organizers could adjust their work at key steps, but not everywhere.

“How much did it change?”

When the exact number matters

→ Tables + delta

“What needs attention?”

When current performance matters most

→ Current event first, past event for reference

“Which event performed better?”

When visual comparison is needed

→ Bar charts

“What was popular?”

When the stats differs year to year

→ Ranked lists

FINAL SOLUTION

An overview with focused tabs.

01

At-a-glance overview:
Surface key metrics across all three categories, with direct links to each tab.

02

Focused tabs:
Keep detailed comparisons easy to navigate without loading everything at once.

How we landed here

Tabs made navigation easier, but my PM raised concerns about data discoverability. I added an overview to address that concern, then walked through both directions with her in prototypes to align on the final approach.

How we landed here

Tabs made navigation easier, but my PM raised concerns about data discoverability. I added an overview to address that concern, then walked through both directions with her in prototypes to align on the final approach.

How we landed here

Tabs made navigation easier, but my PM raised concerns about data discoverability. I added an overview to address that concern, then walked through both directions with her in prototypes to align on the final approach.

Design decision 2

Design decision 2

Design decision 2

Organizers try to turn the comparison into a clear story they can share.

How might we make the comparison easier to report?

Comparing numbers was only part of the job. Organizers still had to identify the key takeaways and put together reports to share with others.

DATA INSIGHTS

Highlighting what changed

I added lightweight insights to help organizers spot meaningful differences without digging through every chart. Since we couldn't always tell why something changed, I kept the insights factual rather than making assumptions.

REPORT EXPORT

Making reporting accessible throughout the event

Generating full PDFs during an event would add significant backend load. After discussing the constraint with engineering, I kept export available through two alternatives rather than disabling it:

  1. Need something now? Download individual charts.

  2. Need the full report? Request the finalized PDF by email after the event.

Design decision 3

Design decision 3

Design decision 3

Organizers may not realize Whova already has features that can help

How might we make nuanced constraints feel lightweight to configure?

How might we surface the right next step at the right time?

How might we surface the right next step at the right time?

Sometimes the data pointed to problems Whova already had solutions for. I wanted to connect organizers with those features without turning the report into a promotional surface.

I established three principles for recommendations:

  1. Contextual: Place suggestions near the relevant metric.

  2. Relevant: Don't recommend features already in use.

  3. Focused: Recommend one useful action at a time.

DESIGNING FOR THE EVENT LIFECYCLE

What matters changes as the event progresses.
What matters changes as the event progresses.

I mapped when different metrics become available and what organizers need at each stage. This helped me decide when a recommendation would actually be useful.

EXAMPLE · POPULAR SESSIONS CARD

The same card, different needs as the event progresses
The same card, different needs as the event progresses

No RSVPs yet

Set expectations for when data becomes available

RSVPs start coming in

Encourage reminders to collect headcounts earlier

Sessions start filling up

Suggest session caps to prevent overcrowding

Impact.

Impact.

Impact.

Organizers compared, shared, and requested more.

Organizers compared, shared, and requested more.

32%

32%

32%

of eligible recurring-event organizers adopted Cross-event Analytics.

53%

53%

53%

exported a report or chart during their event cycle.

19%

19%

19%

click-through rate on contextual feature recommendations.

CUSTOMER REQUEST

"The insights about app adoption, doc views, personal messaging, etc.↵
I have to manually create this for my CEO after every event."

"Would love way more information in this report — Are our attendees sending more messages? Are our exhibitors and sponsors getting more impressions than the year before? Impact of passport contest?"

"I would like to see more than two events compared to each other. Four or more would be great so we can make a trend line."

"Percent of attendees who used the event app".

" Registered vs. attended."

San Diego, CA.

© 2026  Xiaochen(Iris) Shi

San Diego, CA.

© 2026  Xiaochen(Iris) Shi

San Diego, CA.

© 2026  Xiaochen(Iris) Shi

© 2026  Xiaochen(Iris) Shi