App Analytics: Measuring Activation, Retention, and Feature Use

App Analytics: Measuring Activation, Retention, and Feature Use

Three numbers tell you most of what you need to know about an app: activation – the share of new users who complete the first useful action; retention – the share of a group of new users who come back after a day, a week or a month; and feature use – the share of active users who use each important feature. Measuring them takes a short written plan of events tied to business questions, not hundreds of automatically tracked taps. In the EU you also need a legal basis before an analytics SDK reads or sends information from the user's phone – often consent. Below is how to define each number, what to record, where the stores' own reports help, and what to check for privacy.

Start with questions, not with a tool

Every event you track should answer a question someone will act on:

  • How many new users reach the point where the app is useful to them – and where do the others stop?
  • Do people come back? Does the newest version keep them better than the previous one?
  • Which features are used, by how many people, and which are almost never touched?
  • Where do errors and abandoned tasks happen?

If nobody will change anything based on an answer, don't track it. Every extra event is also extra data to explain in your privacy documents.

Activation: did new users reach the first useful action?

Activation needs a definition specific to your app: the action that shows the user got value. For a booking app, a confirmed booking; for a catalogue, a saved search or an opened product page; for a measuring app, the first completed measurement. Measure the share of new users who complete it within a chosen window – say, the first day or the first three days – and the steps before it:

StepExample event
First openUsually logged automatically by the analytics tool
Sign-upsign_up_started, sign_up_completed
Preparationprofile_completed, first_vehicle_added
First useful actionfirst_booking_confirmed

The drop between steps shows where to work. The design side – fewer steps, permissions asked at the right moment – is covered in app onboarding: helping new users reach their first useful action.

Retention: do they come back?

Retention is measured in cohorts: groups of users who started on the same day, week or month. Google Analytics' cohort exploration is a typical example of how this works. You choose an inclusion criterion – such as first open – and a return criterion – any event, or a specific one – plus daily, weekly or monthly granularity. With daily granularity, the "day 1" value for the 1 January cohort counts users who met the inclusion criterion on 1 January and the return criterion on 2 January. Results can be standard (returned in that period), rolling (returned in that period and every earlier one) or cumulative (returned in any period up to then).

Two choices make retention meaningful:

  • What counts as returning. Opening the app can be accidental – a tap on a notification. Returning to do the core task is a stronger signal. Track both, but decide on the second.
  • The right rhythm. Use daily retention for something people use daily, weekly for a weekly task, monthly for something like a service reminder. An app used once a month will look terrible on day-1 retention and may be perfectly healthy.

Be careful with "industry averages" found online – their definitions rarely match yours. Compare your app with itself: cohort by cohort, version by version.

Feature use: what people actually use

For each important feature, log one event when it is used successfully, with a few parameters for context. Then measure the share of active users who used it in a period. A small event plan, agreed before development, keeps this manageable:

EventWhen it firesParametersQuestion it answers
search_performedResults shownnumber of results, filters usedDo people find what they look for?
report_exportedFile createdformatIs the export feature worth maintaining?
order_submittedServer confirms the orderpayment methodHow many orders come through the app?
error_shownError message displayedscreen, error typeWhere do users get stuck?

Keep names consistent from day one. Firebase, for example, allows up to 500 different event types per app and treats names that differ only in letter case as separate events, so "Search" and "search" would split your data.

Many business numbers already live in your own system: orders, bookings, payments. Count those on the server, which sees every transaction, rather than in app analytics, which may only see users who consented. Use app analytics for what only the app can see – steps, screens, abandoned tasks.

Use what the stores already give you

Before adding any SDK, look at the free reports. App Store Connect shows sessions, active devices, crashes and deletions; Apple notes that usage data comes only from users who opted in to share it with developers. In Google Play Console, Android vitals shows stability and performance data collected from users who allow it. These numbers are partial, but they need no extra code in your app.

Consent and privacy in the EU

  • It's not only about cookies. Article 5(3) of the ePrivacy Directive allows storing or accessing information on a user's device only with consent or where necessary for specific purposes. In its Guidelines 2/2023, the European Data Protection Board explains that this covers "similar technologies" too – including software on the device that proactively calls an API endpoint, and SDKs that make the device send information. Exemptions, such as what is strictly necessary to provide a service the user explicitly requested, must be assessed case by case; the EDPB stresses that the rule applying doesn't automatically mean consent is required.
  • In practice, whether your analytics can rely on an exemption depends on what is collected and why, which is why many apps ask for consent before starting an analytics SDK. Firebase documents how to keep Analytics collection disabled until the user consents, and Google's consent mode for apps uses four settings – analytics_storage, ad_storage, ad_user_data and ad_personalization – with no values set by default.
  • GDPR principles apply to what you collect. In the European Commission's summary, personal data should only be processed where it isn't reasonably feasible to do it another way, stored for the shortest time possible, and for a known purpose. Don't send names, emails or phone numbers as event parameters, and set short retention periods in the analytics tool.
  • Apple's App Tracking Transparency is a separate question. On iPhone, you need ATT permission to track users or access the advertising identifier. Apple defines tracking as linking data from your app with data from other companies' apps, websites or offline properties for targeted advertising or advertising measurement, or sharing it with data brokers. Asking for ATT permission and asking for consent under EU rules are two different things.
  • Store disclosures must match. Apple's privacy details and Google Play's Data safety form must include data collected by analytics SDKs.

This is not legal advice. For anything beyond standard product analytics – advertising, combining data across services, health or precise location data – involve a data protection specialist.

Read the numbers honestly

  • Consent changes the sample. If only some users accept analytics, the numbers describe them, not everyone. Watch trends rather than treating totals as exact.
  • Small numbers move a lot. With a few hundred new users a month, a change of a few percentage points can be chance.
  • Segment by app version and platform. A drop that appears only in the newest version points to the release.
  • Combine with what people say. Reviews and support requests explain the "why" behind the numbers.

If you are planning an app, agree the measurement plan – activation action, retention rhythm, key features and consent flow – before development starts; adding it later means another release. We can help define and build it, including the server side and consent screens, as part of our mobile app development service. Get in touch.

Sources

← All articles

Have an idea for a website, app or system?

Tell us briefly what you need – we will get back to you for a short call and a clear quote.