Analytics events

Before you can measure anything, something has to be worth measuring. This screen is the list of moments your app is able to report: a booking confirmed, a file uploaded, a search that found nothing.

A catalogue of events — "booking_confirmed", "file_uploaded" — each with the count of details it carries and where it was defined. A panel on the right lists the details of the selected event.

This is a menu, not a measurement

The most important thing on this page is the line the screen itself puts at the top: declared, not counted.

Everything here is what your app may report. Nothing here tells you whether it ever did, or how often. A brand-new project and a project with a million visitors show exactly the same list.

That is worth sitting with, because the screen looks like a dashboard and is not one. If you came here to find out how many people booked something this week, this is the wrong page — but it is the right page for finding out whether "booked something" is a thing your app is even able to tell you about yet.

What each event carries

Open an event and you see the details that ride along with it — for a confirmed booking, perhaps which room and how many nights. Those details are what let you ask interesting questions later. An event with none is still useful, but it can only ever answer how many, never which kind.

The panel also shows where the event was defined, which is how you find the part of the app that reports it.

If the list is empty, the app has not declared any events yet. That is a change to make in the app, not a setting on this screen.

Where to go next

• Logs — what your app actually did, as it happened.
• Overview — the health of the running app.
• Everything your app offers — the same declared-not-observed idea, applied to the ways in.