What to track in a mobile app

Most apps need 10 to 20 events. Each guide lists the events that answer real questions for one part of your app, the calls for Swift, Kotlin, Flutter and React Native, and what Respectlytics shows you from them.

Start free Try the live demo

Free for one app and 20,000 events a month, no card needed. The demo runs on sample data, no signup.

The event plans

Pick the part of your app you want to understand first. Each plan works on its own.

Subscriptions and paywalls Which paths lead to a purchase Onboarding and signup The step where new users give up Shopping and checkout Where carts are left behind Engagement and features Which features go with converting

Three rules for event names

Respectlytics stores the name and no free-form properties, so the name has to carry the meaning.

One pattern everywhere. Lowercase words joined by underscores, object then action: paywall_viewed, checkout_completed.
A fixed list. Write the names down before you ship and never build one from user input, so no personal detail can end up in a name.
Split only what you will compare. If annual and monthly purchases matter separately, use purchase_annual and purchase_monthly. Otherwise keep one name.

What you see in Respectlytics

All of it comes from the five stored fields and only the properties you declare. Nothing about who the user is.

Conversion paths

The most common sequences of events in sessions that converted, found for you once you name your conversion events.

Drop-offs

The steps where sessions end, ranked by how many sessions each one loses.

Funnels

Any sequence of events you choose, with the conversion and the time taken at each step.

Conversion drivers

The events that sessions which converted did more often than the rest, with the size of the difference.

Segments

Conversion compared by platform, country, session depth and hour of day.

Open the live demo

Every view above, running on sample data. No signup.

Questions buyers ask

Straight answers to what teams ask before they choose.

How many events should an app track?

Usually 10 to 20. More events make paths harder to read, because every session starts to look unique. Start with the steps that lead to the thing you want users to do.

How should I name events?

Lowercase words joined by underscores, object then action or action then object, and the same pattern everywhere: paywall_viewed, trial_started, checkout_completed.

Comparisons, design choices, event plans and industries.

Alternatives Firebase, Mixpanel, Amplitude and PostHog, compared Why Respectlytics Four design choices, enforced in code Industries Health, finance, education and dating apps

Try it on your own app

Free for one app and 20,000 events a month, no card needed. Unlimited apps on every paid plan.

Start free Read the SDK docs