App analytics is the practice — and the category of tools — for measuring what users do inside a mobile app. It captures behavioral events (screens viewed, buttons tapped, levels completed, purchases made) and turns them into funnels, [[cohort-analysis]], [[retention]] curves, and segments that explain how and why people use the product.
Analytics vs attribution
These are often confused. [[install-attribution]] answers "where did this user come from?" — which ad, campaign, or channel drove the install. App analytics answers "what does this user do once inside?" — the in-app behavior. Acquisition tools ([[mmp]]s) own the first question; analytics platforms own the second. Mature teams run both and join them, so they can see not just which channels drive installs but which drive engaged, retained, high-LTV users.
The building blocks
- Event tracking — the raw record of user actions, the foundation everything else is computed from.
- Funnels — conversion through a defined sequence (e.g. onboarding → activation → purchase), exposing drop-off.
- [[cohort-analysis]] — grouping users by a shared start event to compare behavior over time.
- [[retention]] & engagement — return-rate curves, [[session-length]]/[[session-frequency]], [[dau-mau]] stickiness.
- Segmentation — slicing all of the above by user properties to find what differentiates good cohorts.
The platform landscape: Amplitude, Mixpanel, Firebase, and Heap are the common product-analytics platforms, integrated via [[sdk]] and typically paired with an MMP for the acquisition side. The strategic payoff is closing the loop — connecting acquisition source to downstream behavior so spend flows toward users who actually retain and monetize, not just install.