KOCHI, KERALA, INDIA - SEPTEMBER 3, 2026: Participants attend WikiConference India 2026, the fourth national conference bringing together Wikimedians, researchers, educators, developers and stakeholders involved in Indic-language Wikimedia projects and the wider open-knowledge movement. Hosted by th
Photo by Gangulybiswarup on Wikimedia Commons, CC BY 4.0

Event Follow-Up

Part of Event campaign operations and review

Reviewing the gap between registration and attendance

Investigate the gap between event bookings and observed attendance without guessing why people were absent.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Event Operations Desk.

A gap between registrations and observed attendance tells you whom your records did not match to the event. It does not tell you why they were absent.

Reconcile the records first, then investigate the part of the attendee journey where a change could help the next event.

Establish which people are in the gap

Choose a pre-event booking cut-off and retain the extract date. Remove test records, apply a consistent rule to cancellations and transfers, and count people rather than orders that may contain several tickets. Match valid registrants to check-in or live joining records using a documented rule. Keep walk-ins, staff, speakers and uncertain matches separate.

Show the valid-registration count, matched-attendee count and unresolved records together. If a later check-in correction changes the gap, preserve the earlier snapshot and explain the change. Do not label an uncertain match a no-show.

A rate can describe the size of the gap, but the counting definitions and comparison with participation measures belong in the separate metrics review.

Investigate plausible break points

Record patternQuestion to investigateLimit on the conclusion
Cancellations rose after a changeDid the date, venue, programme or eligibility change?A cancellation reason may be missing or incomplete.
Attendees reported arrival or joining troubleWere instructions current and usable?Respondents may not represent everyone who was absent.
Check-ins cannot be matched reliablyWere tickets transferred or details entered differently?An unmatched record is not proof of absence.
The gap appears concentrated in one invitation routeDid notice, audience fit or practical commitment differ?A tracked route does not prove that its message caused attendance or absence.

These are investigation prompts, not proven causes. Compare the invitation and confirmation actually issued to the affected group with the current event facts. Look at support contacts, change records and check-in exceptions before changing the promotion plan.

If the team uses Google Analytics, tagged URLs can identify campaign traffic in its Traffic acquisition report. That traffic record does not identify a registrant or attendee without separate, appropriately connected records. A link may also be forwarded, so a tagged route is not sole credit for someone's decision.

Choose a checkable response

Use evidence that can guide the next event. A support log may reveal a repeated question about an entrance; feedback may reveal an access barrier.

State how many people reported a problem, and do not infer that silent registrants had the same experience. If missing attendance data is substantial, improve check-in recording before deciding promotion failed.

Write each conclusion as an observation, a possible explanation, a next check and an owner. For example: Several registrants asked which entrance to use; compare their arrival instructions with the venue's confirmed route before the next invitation is approved.

Keep learning and business outcomes separate from this attendance diagnosis.

More in Event Follow-Up