Results · in progress

What the data says so far.

ewent has run on 73 events. This page reports what we can evidence today and is explicit about the study that is still being written.

73
events run on ewent
verified 20 Sep 2026
67,000+
checklist steps ticked
server-side count
8
touchpoints per attendee
cp1–cp8
0
platform migrations required
overlay by design
The honest state. 67,000 ticks is a strong engagement signal — attendees open these pages and act on them. It is not the same as a published show-rate lift. That figure needs matched baselines across enough comparable occurrences, and it is being assembled now. We would rather be late than loose; the methodology page sets out exactly how it will be computed.

What we can say

Three things the ticks already tell us.

☑

Attendees use it

67,000 voluntary actions on pages nobody is obliged to open. Prep steps get ticked days ahead, not in the final hour.

◷

Local timing matters

Engagement concentrates in the attendee's own working hours, which is only possible because sends are computed per-timezone rather than broadcast.

⇄

People do cancel when asked

Given a one-click exit, some registrants take it — which frees seats instead of producing silent no-shows.

The study in progress

The club-network case study covers a recurring series with prior occurrences to baseline against — the cleanest comparison available. It will publish with the sample size, the exclusions, and the raw before/after per occurrence, so it can be argued with.

Want to be in it, or want the numbers for your own events before they publish? Ask us — we will show the working.

Stop losing the people who already said yes.

Connect the registrations you already collect. We handle the rest — per-attendee checklists, timezone-local reminders, and a live nudge when the room opens.

Request access See how it works