What Your Event Analytics Dashboard Actually Shows You
TIME&SPACE · Organiser's Playbook
Scans, matches, downloads, shares, upload velocity by hour: every event plan includes analytics. Here is exactly what the numbers mean and where each one comes from.
What Your Event Analytics Dashboard Actually Shows You
In short: Every paid event plan, starting at Starter, includes an analytics dashboard. It counts scans, matches, downloads, shares and upload speed, broken down by tag, by uploader and by hour. None of it is a guess: each number comes from an actual action a guest took.
An event gallery fills with photos, and then with activity: guests scanning, finding themselves, downloading, sharing. The analytics dashboard is where that activity becomes numbers an organiser can actually use, during the event and after it.
Who can see it
Analytics is gated by two things, not one. The person has to hold a role with access: an organiser or a collaborator, never a view-only invite. And the event has to be on an active paid plan, because analytics is a feature of the plan, not a separate add-on. It is included from Starter up, so there is no tier where an organiser pays for an event and gets no numbers back.
Scans and matches
A scan is counted the moment a guest's selfie is checked against the event. A match is a scan that found at least one photo. The gap between those two counts is the honest read on how well the gallery is actually working for guests: a high scan count with a low match count means people are trying and not finding themselves, which is worth noticing before the event ends, not after.
Downloads and shares, and who they can be attributed to
Every download and every share is logged as an event action. Since 11 October 2026, both are also linked to the session that performed them, which is what makes a per-person view possible: how many distinct people downloaded at least one photo, how many shared at least one, not just a raw tally of taps. Actions from before that date still count toward the totals, they just cannot be tied to a specific person retroactively. Shares also break down by destination, so an organiser can see whether guests are actually choosing Instagram, WhatsApp, or simply copying a link, rather than assuming.
Photos, by tag and by uploader
If an event uses tags, the dashboard counts photos per tag, which is the fastest way to see whether a specific moment, sponsor activation, or stage got covered. The same breakdown exists per uploader, so a multi-photographer event can see each contributor's output side by side rather than one undifferentiated pile.
Upload velocity, hour by hour
The dashboard also plots how many photos landed in each hour of the event, for up to a week of hours. This is less about any single number and more about the shape of the graph: a flat line usually means something stopped uploading, and a late spike is often just the photographer offloading a card after the fact rather than shooting live. Reading the shape catches problems a single total never would.
What it is not
Analytics describes what already happened in this event's own gallery. It is not a competitive benchmark against other organisers, and it is not a prediction. The dashboard also respects the same filters an organiser applies while viewing it, tag and uploader included, so the numbers on screen always match the scope actually selected.
The short version
If guests are scanning, finding photos, downloading and sharing, there is a dashboard that shows exactly how much of that happened, who did it, and when, without an organiser having to guess from the gallery view alone.
Founder, TIME&SPACE