Services / 01
Know your customer
Right now your best customer and your worst one look identical in your reports. This work makes them different.
What you can answer afterwards
Outcomes, not features.
- Who your best customer is
- By what they did, not by what they filled in on a form.
- Where people give up
- The exact step, on the exact device, on the exact day it started.
- Which channel actually pays
- Measured through to revenue, not to clicks or to what the platform reports about itself.
- Who comes back, and why
- Return visits tied to what happened on the first one, so retention becomes something you can act on.
- What a customer costs you
- One number, defensible, updated every month.
- Whether this month was good
- Once a month, in writing: what changed, what caused it, and the first thing worth doing about it.
What we actually set up
For the person who wants to check the work.
Everything above is in your language. This is the same work in ours, so you can hold it against anyone else’s quote.
- A Google Analytics 4 property, configured from scratch rather than inherited
- Google Tag Manager on the website, with a written tag plan
- Firebase Analytics in the Android or iOS app, sharing the same event names
- A named event for every step that matters, in your business's own words
- Custom dimensions for your vocabulary: plan, region, account type, whatever you sort customers by
- Funnel and retention reports built around those events, not the defaults
- Conversions reconciled against the revenue you actually banked
- Consent handled properly, with consent mode where your customers' law requires it
- A written event map, so the setup survives us leaving
- A monthly read: one page, plain language, what changed and what to do
What lands with you. A sample, so the shape is honest before the figures are yours.
We did this to our own apps first.
Zip VPN: Our own app, measured the way we would measure yours.
Questions people ask
The ones that actually arrive.
Will this slow my website or app down?
No. Measurement scripts load after the page, and an app event is a few bytes sent in the background. We check the page speed figures before and after, and publish both to you.
Do I lose the setup if we stop working together?
No. Every property, container and account is created under your ownership, and the event map is a document you keep. If we leave, nothing we built leaves with us.
What do you need from my team?
Access to the website and app code, or to whoever changes it, and about two hours of one person's time in the first week to agree the questions and the vocabulary. After that, very little.
Is this legal where my customers live?
It is set up to be. Consent is asked for where the law requires it, and nothing is recorded before it is given. If your customers are in the European Union or the United Kingdom, the setup follows the rules there, and we will tell you if something you have asked for cannot be done lawfully.
We already have analytics installed. Is this still useful?
Usually more so. Most installs record page views and nothing else, which is why they cannot answer the questions above. We start by reading what is there, keep whatever is honest, and rebuild the rest.
Next / 02
Get more customersGoogle and Meta campaigns run against what the measurement says, not against what the platforms report about themselves.