AARRR — Acquisition, Activation, Retention, Referral, Revenue — is a growth framework popularized in the startup world as a simple way to map every growth metric a company tracks onto one of five stages of the customer lifecycle. The name is a pun ("pirate metrics," for the string of R-sounds), but the structure behind it has held up because it forces a specific discipline: instead of a single "growth" number, every metric gets assigned to the stage it actually measures, which exposes which stage is genuinely the bottleneck instead of letting a team optimize the stage that's easiest to move while the real leak sits elsewhere.

The five stages

Acquisition — how do users first find the product (organic search, paid ads, referral, content, partnerships), measured by metrics like traffic by channel and cost per acquired visitor. Activation — do new users have a good first experience that gets them to a meaningful first value moment (an "aha moment"), measured by signup-to-activation conversion rate and time-to-first-value. Retention — do users come back and keep using the product over time, measured by day/week/month retention curves and churn rate — widely considered the stage that determines whether the other four even matter, since acquiring users who don't stick is building on sand. Referral — do existing users bring in new ones, measured by invite rate and viral coefficient (see the dedicated lesson on viral loops). Revenue — does usage convert into monetization, measured by conversion-to-paid rate, average revenue per user, and LTV.

aarrr_funnel.txt

text

ACQUISITION   -> visitor arrives (channel: organic, paid, referral)
     |
     v
ACTIVATION    -> visitor reaches "aha moment" / core value event
     |
     v
RETENTION     -> user returns on day 7 / day 30 / month 2...
     |
     v
REFERRAL      -> user invites/shares, bringing in new acquisitions
     |                                        |
     v                                        v
REVENUE       -> user converts to paid    (loops back into ACQUISITION)

Why stage order matters more than it looks like it does

A common instinct is to work the stages in the order they're listed — fix acquisition first because it's the top of the funnel. That instinct is usually backwards. If retention is broken, every acquisition improvement just means more users churning faster, often while paid acquisition costs stay fixed or rise — you're filling a leaking bucket faster, not fixing the leak. The standard practitioner guidance is to work the stages in reverse order of their position when they're all weak simultaneously: fix retention before referral, fix activation before acquisition, because improvements to a downstream stage increase the value of every unit of traffic the upstream stages bring in, while the reverse isn't true.

AARRR stage diagnostics

Stage	Core question	Typical leading metric	If broken, upstream fixes are wasted because...
Acquisition	Are people finding us?	Visitors/signups by channel, CPA	N/A — this is the entry point
Activation	Do new users get value fast?	Time-to-first-value, activation rate	Acquired users never experience the product's value
Retention	Do users come back?	D7/D30 retention, churn rate	Acquired + activated users leave anyway
Referral	Do users bring others?	Invite rate, K-factor	Retained users exist but never become a channel
Revenue	Does usage convert to $?	Conversion-to-paid, ARPU, LTV	All of the above happens with no monetization

Retention is the stage that validates all the others

If users aren't retaining, it usually means the activation experience didn't actually deliver the value the acquisition message promised — a mismatch between what you're attracting people with and what the product delivers. Retention data is often the fastest way to discover that an acquisition channel is bringing in the wrong kind of user, not that the product itself is broken.

AARRR describes a user's journey, not a strict waterfall

Real users don't move through these five stages once and stop — a retained user keeps re-entering activation-like moments (a new feature's first use), and referral can trigger at nearly any point in a user's lifecycle, not only after they're fully retained. Treat AARRR as a classification scheme for metrics, not a rigid sequential gate every user must clear in order.

Using it for a metrics audit

A practical way to apply AARRR: list every metric currently tracked on a growth or product dashboard and assign each one to exactly one stage. Teams doing this for the first time are routinely surprised to find they're tracking five acquisition metrics, one activation metric, and nothing at all for referral — a direct signal about where organizational attention has actually been going versus where the biggest unexamined risk or opportunity might sit. The framework's real value isn't the five-letter acronym; it's the forcing function of making every metric declare which stage of the lifecycle it's actually accountable for.

What's next

AARRR classifies metrics by lifecycle stage; Product-Led Growth is a strategy for how the product itself, rather than sales or marketing, drives movement through several of these stages at once.

Next: Product-Led Growth (PLG) →

I build these systems professionally.

Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.

Work With Me →

Need production AI or MarTech expertise? I build custom LLM workflows, server-side GTM tagging, and analytics infrastructures professionally.

Need custom AI or MarTech setup? Let's build together.

Let's talk →