Service 13 / 14
What brought the customer, not just the visit.
Most reports count visitors. We build the one that answers the question a business actually asks: what generated this customer, and what was it worth?
In short
What this covers
Traffic dashboards answer the wrong question. A thousand visits from a blog post and three from an ad that each became a customer look backwards in a visits report.
We join the pieces that usually live apart: the visit and its source, the form or call or booking, the qualification, the customer and the revenue. Every step is an event in one schema, every lead keeps its touches, and revenue is shared between them with a model you choose and can see.
- Usually for
- Owners who want to know which marketing pays, Teams with GA4, a CRM and a phone line that do not agree, Companies spending on ads, SEO and content at once
You may recognise
Signs this is the problem
- Reports disagree with each other
- You can’t say what a customer costs
- AI assistants send visits nobody measures
The work
What we do
-
Event model
page_view to revenue_recorded: one schema for the site, the phone line, the booking engine and the portal. Personal data never travels in an event.
-
Attribution
Channel from click ids, campaign tags and referrers. ChatGPT, Perplexity, Gemini and Copilot are a channel of their own.
-
Lead record
One person from first touch to revenue, across forms, calls and bookings, with the history of each stage.
-
Revenue models
First touch, last touch, linear or position-based, stated on every report, totals exact to the cent.
-
Platform feedback
Qualified leads and customers sent back to ad platforms, so they optimize for what matters.
-
Reports
A short, readable report: customers and revenue by channel, cost where there is spend, what changed.
Architecture
How the system fits together
Privacy first: no third-party tag is needed for any of this. Platforms receive only what you choose to send, with consent.
-
Capture
First-party events and campaign tags, no cookies by default.
site/client/analytics.js -
Normalize
Validated against the event schema; personal data refused.
site/server/growth/events.js -
Join
Events, calls and bookings joined to one lead record.
site/server/growth/lead.js -
Attribute
Channels classified, revenue allocated by the chosen model.
site/server/growth/attribution.js -
Feed back
Conversions to GA4 or ad platforms where configured.
GA4 Measurement Protocol · Data Manager API
Status
What runs today, and what waits for access
Live means it runs now. Integration-ready means the code, the data model and the tests exist and it starts once your account or a platform approval is connected. Planned means not running yet: designed, or built and tested but not yet connected to a live endpoint.
-
Integration-ready
Event schema, lead record, attribution models
Implemented and unit-tested. The lead record already scores every brief this site receives.
-
Integration-ready
Event collection endpoint
Validates and stores events once the storage binding is enabled.
-
Needs your account
GA4 and ad-platform feedback
Needs the property’s secret or the platform access; the secret stays on the server.
Integrations
What it connects to
- Google Analytics 4 Needs your account
- Server-side events through the Measurement Protocol; reports through the Data API.
- Google Ads / Data Manager Needs your account
- Offline conversions with consent.
- Cloudflare Web Analytics Live
- Cookieless page analytics, already on this site.
- Your CRM Planned
- Leads, stages and revenue in and out.
Measurement
What we measure, and where the number comes from
- Customers and revenue by channel
- Lead records with recorded revenue, allocated by the stated model.
- Funnel conversion
- Normalized events, step by step.
Handover
What you end up with
- An event plan: what is tracked and why
- The lead record and attribution running on your data
- A monthly report you can read in five minutes
Limits
Where this isn’t the right fit
We track less, not more: only events that answer a business question, never personal data in analytics.
Attribution is a model, not a truth. Every report names its model and the data it stands on.
Fit
When to call us, and when not to
Worth a conversation if
- Several channels at once
- Revenue you can record per customer
Probably not if
- Too few customers to measure anything yet
FAQ
Questions about this
Does tracking mean cookies and pixels everywhere?
No. The event model is first-party and carries no personal data; this site uses no cookies and no third-party tags. Advertising platforms only receive what you choose to send them, with the visitor’s consent where the law requires it.
Whose accounts do you use?
Yours. Your Google Business Profile, ad account, Search Console, phone numbers and data stay in your name, and we get access you can remove at any time. Some connections also need an approval from the platform (Google reviews API access to Business Profiles, for example); until then the same work is done by hand, from the same rules.
Which of your channels actually pays?
Tell us what you need and by when. We read every enquiry and reply in writing, with questions, a next step, or a plain no if we’re the wrong studio.


