Do I need to rip out my current analytics tool?

Usually not. Keep a lightweight pageview tool for traffic if you like, and add one product analytics tool as the source of truth for activation and retention. This guide shows how to audit what you already fire, keep what is accurate, and stop double-counting the same action in two places.

Can I do this with only a few hundred users?

Yes, and that is when it matters most. With small numbers you cannot trust week-to-week percentages, but you can still define activation, compare early actions of retained versus churned users, and read cohort tails. The views will be noisy, so the guide uses absolute drop counts and longer windows until volume grows.

Will this setup require a cookie banner?

It depends on what you collect and where you host. Pageviews with anonymised IP and no cross-site identifiers can often run without consent in the EU, while event tracking tied to a user ID and hosted outside the EU typically needs consent. The guide configures consent mode, IP anonymisation and EU hosting so you collect what is allowed and ask only when you must.

What if I already tracked 30 events with inconsistent names?

Do not rename them in place — you will lose history. Freeze the old events, document them as deprecated in the schema, and start the clean object-action vocabulary from the activation event outward. Old data stays queryable, new data stays comparable, and you migrate only if a decision truly needs the old series.

Do I need to become a privacy lawyer to do this correctly?

No, but as the data controller in the EU you must make deliberate choices on purpose, legal basis, retention and user rights. The guide gives you the checklist to set — anonymise IP, avoid fingerprinting, set a 12 to 14 month retention, document hosting region, and note how to delete a user — and tells you when to get legal review.

Instrument your product so the numbers mean something

A trusted product measurement setup with one defined activation event, a stable naming schema, an activation funnel, a retention cohort chart read correctly, a paid conversion path and churn signal, all collected in a consent-compatible way, plus a written list of metrics you deliberately do not track.

Fby Finito HQEchipa Finito

Created 3 weeks agoUpdated 2 weeks ago

Free preview: 4 of 21 steps

Work through them in the real run view, exactly as a buyer does. No account, no payment, nothing saved.

Try it free

Free

3 free unlocks per month — yours to keep forever

Updated Aug 2026

Start for free

Try 4 of 21 steps free

No account needed — nothing is saved.

Included with every copy

Your own copy — keep it forever
Gets better over time — free updates included
Run it on web and mobile
Invite a partner to go through it with you — you share the same progress
Make it your own — a private copy you can edit to fit your situation
The playbook's community — ask questions, get additions, and see how other buyers improve it, right on the step

Save

Part of a collection

Turn users into revenue

Guide 4 of 6

See the collection

Who it's for

Indie makers and solo developers with a live product who have either no analytics or a cluttered dashboard nobody acts on, and who can edit the codebase or direct someone who can.

About this playbook

Turn a live product with vague dashboards into a measurement setup you trust and actually use. You will define the three questions that should change a decision, isolate the single activation event that predicts retention, choose a tool on cost, ownership and EU hosting, lock a naming schema that preserves history, and build only four views that matter: activation funnel, retention cohorts, paid conversion and churn signal. You will instrument events server-side where possible, wire identity correctly, make collection consent-compatible, and learn to read cohort tails instead of vanity counts. This guide does not cover ad attribution, advanced product analytics for large teams, or A-B testing infrastructure.

What you'll do, step by stepFree preview

5 phases · 21 steps

Only a sample is open: 4 of 21 steps can be read in full. The rest unlock when you buy.

Phase 1: Define what deserves to be measured
4 steps
Phase 2: Choose the tool and lock the language
4 steps
Phase 3: Instrument the product and build the four views
5 steps
Phase 4: Verify the numbers and make them consent-compatible
4 steps
Phase 5: Decide what not to track and keep the setup alive
4 steps

Try 4 of 21 steps free

Unlock all 21 stepsFree

Details

Estimated duration18 hours 15 min

Steps21

Estimated budget€0–€50 per month depending on event volume; many solo setups stay at €0–€20

What you need first

A live web or mobile product with real users, access to the codebase or to the person who deploys it, ability to query users or database for behaviour from the last 60 to 90 days, and admin access to choose or reconfigure an analytics tool.