Conversion tracking that tells you where your enquiries actually come from.
Most businesses have analytics installed and still cannot answer the only question that matters: which page, campaign or click produced that enquiry. Usually the tracking was never set up for that — or it was, and nobody ever tested it.
This is the single most common reason people get in touch, and the symptoms are consistent.
01
The ad platform claims forty conversions. You received nine enquiries.
Often the conversion is firing on a button click rather than on a successful submission, so every abandoned form, every validation error and every double-tap is counted as a lead.
02
Analytics shows traffic, but nothing about outcomes.
GA4 was installed and left at defaults. Sessions, page views and bounce rate are all there. No key events, so no page, source or campaign can be tied to an enquiry.
03
Phone and WhatsApp enquiries are invisible.
For many service businesses most enquiries never touch a form. If taps on the phone number and the WhatsApp link are not tracked, the majority of your demand is missing from every report you look at.
04
The same enquiry is counted two or three times.
A browser pixel and a server-side event both reporting the same action without a shared identifier, plus a thank-you page that fires again on refresh. The numbers look healthy and mean nothing.
THE SYSTEM
Where tracking sits in the chain.
Measurement is the stage the other three depend on. Without it, the site, the search work and the ad spend are all judged on a guess.
BUILD. FIND. MEASURE. CONVERT.
not four unrelated services — one connected chain.
01 / BUILD
BUILD
A site whose forms, phone links and thank-you states can actually be measured.
02 / FIND
FIND
Search Console linked to GA4, so queries are judged by the enquiries they produce.
03 / MEASURE — THIS SERVICE
MEASURE
GA4, Tag Manager and conversion events that fire once, on genuine success, tested.
04 / CONVERT
CONVERT
Ad platforms fed clean conversion data, so they optimise toward real enquiries.
WHAT GETS SET UP
The work, item by item.
Scope varies. This is the full list; yours will say which of it applies.
Foundations
Google Analytics 4 — property configured, data retention, time zone, internal traffic excluded
Google Tag Manager — a single container with a documented naming convention
UTM conventions — written down, so campaign traffic is attributable
Conversions
Form submissions — fired on genuine success, not on a button click
Phone and WhatsApp taps — tracked on real devices, not assumed
Key events in GA4, limited to actions that are actually business outcomes
Google Ads — conversion import from GA4, enhanced conversions where consent allows
Meta Pixel and Conversions API — with a shared event ID so they deduplicate
Documentation — what fires, when, and what each parameter means
TECHNICAL DETAIL
The event specification for this website.
Every site gets one of these. It is the difference between a tag manager somebody can maintain and a container nobody dares touch. Below is the real specification running on this site, which is also the shape of what you would receive.
DATALAYER SPECIFICATIONTHIS SITE, LIVE
Event
Fires when
Parameters
Business conversion?
form_submit
A submission genuinely succeeds — AJAX success callback or the thank-you page loading. Never on button click.
service_interest, budget_band, page_path
Yes
whatsapp_click
Any WhatsApp link or button is tapped, on mobile and desktop.
location, page_path
Yes
phone_click
A tel: link is tapped on a real device.
location, page_path
Yes
form_start
First interaction with any field in the enquiry form.
form_id, page_path
No — diagnostic
form_step
Advancing between steps of a multi-step form. Shows where people give up.
step, form_id
No — diagnostic
primary_cta_click
Any primary call to action is clicked, with its position on the page.
location, label, page_path
No — diagnostic
pricing_view
The pricing table is at least half visible for three seconds.
page_path
No — intent signal
faq_open
An FAQ item is expanded. Tells you which objections matter most.
question, page_path
No — research
Three conversions, not eleven. Marking every interaction as a conversion is how reporting becomes decorative — if everything is a conversion, the ad platform optimises toward noise and you lose the ability to compare channels honestly.
THE DISTINCTION THAT MATTERS
A tracked event is not a confirmed lead.
SIGNAL
Tracked event
A signal your website recorded
Includes spam, test submissions and duplicates
Includes phone taps where nobody actually called
Affected by ad blockers, consent choices and browser restrictions
Useful for comparing pages and campaigns
≠
REALITY
Confirmed lead
A real enquiry sitting in your inbox or WhatsApp
Counted by hand, or from your CRM
The number your revenue actually relates to
Always lower than the tracked number, sometimes much lower
The one to judge a channel on
Both get reported, separately, with the gap visible. Any report that shows only the tracked number is flattering itself. Watching that gap over time is also the fastest way to catch a tracking problem — when it suddenly widens, something has broken.
VALIDATION
How you know it is right.
Tracking work is easy to fake, because nothing visibly breaks when it is wrong. The check is whether it was tested, and whether you were shown the test.
Every event is verified in Tag Manager preview mode and GA4 DebugView, with a real submission sent end to end and the resulting notification email confirmed as arriving. Meta events are checked in Events Manager, including that browser and server events deduplicate rather than double-count. You receive the screenshots and the specification, so the setup is auditable by whoever comes next — including someone replacing me.
HANDOVER CHECKLISTevery event
Tag Manager previeweach tag fires once, on the right trigger
GA4 DebugViewevents arrive with their parameters
Real submission, end to endform sent, notification email confirmed
Meta Events Managerbrowser + server deduplicate, not double-count
Screenshots + specificationhanded over, auditable by whoever comes next
FIT
Who this suits.
A good fit
Anyone spending on ads without trustworthy conversion data
Businesses where most enquiries arrive by phone or WhatsApp
Sites where GA4 was installed years ago and never configured
Agencies and marketers who need the technical side handled properly
Businesses that need an existing setup audited rather than rebuilt
Not a good fit
Enterprise data warehousing and custom BI pipelines
Server-side tag manager infrastructure, which is not offered at launch
Anyone wanting tracking that ignores consent requirements
Sites on locked platforms where no custom script can be added
Projects are published as case studies only once the client has agreed to be named and shown. That is slower than filling a portfolio grid, and it means what is on the site can be taken at face value.
If you want to see relevant work before deciding, ask and it can be walked through directly — including the parts that did not go to plan.
Yes, and it is usually cheaper than starting again. An audit establishes what fires, what double-fires, and what was never connected. Sometimes the fix is small. Sometimes the container has thirty tags of which four work, and rebuilding is faster than untangling it — you will be told which.
Do I need Google Tag Manager, or is GA4 enough?+
GA4 alone handles basic page tracking. Anything else — a form success, a phone tap, sending the same event to Meta and Google without duplicating it — is far cleaner through a tag manager. It also means future changes do not require a developer touching site code.
What is the Conversions API and do I need it?+
It sends conversion events to Meta from a server rather than the browser, so events are not lost to ad blockers and browser privacy restrictions. If you spend meaningfully on Meta, it is worth having. It must share an event ID with the browser pixel, otherwise you simply count everything twice.
Can you track phone calls?+
Taps on a phone number, yes — that is standard. Whether the call connected and how long it lasted needs call tracking software with dedicated numbers, which is a third-party subscription. It can be integrated if you want it, but it is an extra cost and worth it only at volume.
Will this still work with cookie consent?+
Yes, and it is built to. Consent Mode v2 signals are passed so Google tags behave correctly when consent is declined. Requirements in New Zealand and Australia are lighter than the EU, but sites get European visitors and being built for it costs nothing extra.
Do you offer server-side tagging?+
Not at present. It adds hosting cost and ongoing maintenance that only pays off at significant ad spend. Meta's Conversions API, which covers the most common reason people ask, is available now.
Find out what your tracking is actually recording.
Send your site address and what you are running ads on. You will get a straight answer about what is working, what is double-counting, and what was never connected.