Analytics for a New App: The Events Worth Tracking
- Growth
- Analytics
- Product
Track the few moments that tell you whether the app works, not every tap. Fifteen good events beat three hundred noisy ones.

A newly launched app needs answers to a few questions: are people finishing sign-up, are they reaching the point where the app is useful, are they coming back, and are they paying? Tracking every tap does not answer those faster; it buries them. A short list of well-chosen events does.
Start from the questions
Write down what you need to know in the first three months. "Do people who complete onboarding come back in week two?" is a question. "Track everything just in case" is not. Each question points to the few events needed to answer it.
The events most apps need
- Sign-up started and completed, to see where new users leave.
- The first useful moment: first booking, first document, first habit logged. This is activation.
- The core action, each time it happens, so you can measure how often people use the app for its main job.
- Purchase or subscription events: started, completed, renewed, cancelled.
- Key failures: a payment declined, a search with no results, an upload that failed.
With those, you can see the funnel from install to activation and the cohorts that stay. Ten to twenty well-defined events are usually enough for a long time.
Name them once, consistently
Agree a naming scheme before launch, such as booking_completed with a few properties like the service type, and write it down. Inconsistent names ("Booked", "booking_done", "BookingComplete") are how analytics become untrustworthy.
Retention is the number that matters
Downloads feel good; retention tells you whether the product works. Look at what share of users come back after a day, a week and a month, and how that changes after each release.
Crash reporting is analytics too
A crash on one popular device can quietly lose a share of your users. Crash and performance reporting belong in the first release, next to product analytics.
Respect privacy
Collect what you need and nothing more. Do not send personal data such as names, emails or message content into analytics tools. Declare what you collect accurately in the App Store and Play Store forms, and ask for consent where the law or the platform requires it.
Instrumenting apps properly is part of how we approach growth. Once the events are in place, the first two minutes are usually the first thing worth improving.