Conversion tracking your ads can learn from.
If a sale, call or enquiry isn't recorded, the ad platform can't learn from it and your report can't show it. I set up GA4 and Google Tag Manager, the Meta Conversions API, TikTok events, and call and WhatsApp tracking, then connect leads to the CRM or inbox your team already uses. Available alongside ad management or as a project on its own.
From the ad to the sale, and back to the ad platform.
- 01AdMeta · Google · TikTok
- 02Landing pagebuilt or fixed
- 03TrackingGA4 · GTM · CAPI
- 04CRM / WhatsApplabels, reply in minutes
- 05Automationfirst reply, hand-off
- 06Reportwhat sold, what next
↩ Outcome sent back to the ad platform, so it finds more people who buy.
Measure everything first, then automate what happens after the lead.
Built in the tools your business already uses, so nobody has to switch CRM to work with me.
GA4 and Google Tag Manager
One container, every tag managed from it, events for the actions that matter, consent handled, and Google Ads and GA4 agreeing with each other. On a single-page app that includes page views on every route and UTM parameters that survive the first screen.
Meta Conversions API
Server-side events alongside the pixel, deduplicated, with match quality checked. The single biggest fix on most Meta accounts since iOS 14.
TikTok Pixel and Events API
Same discipline on TikTok, so cost per result is real rather than a view count.
Calls and WhatsApp as conversions
Call tracking with a minimum duration, and WhatsApp conversations labelled new, qualified, quoted, booked.
CRM hand-off
Leads into HubSpot, WATI, Bitrix24, Kommo or a shared inbox, with the source and campaign attached, so sales can tell you which ads bring buyers.
Automation and AI
First reply in minutes, reminders for unanswered leads, and AI used for sorting and drafting where it saves your team time, never for talking to customers unsupervised.
Every event received, every tag fired.
This is the screen I want to see before a campaign goes live: events arriving from the browser and the server, deduplicated and matched, and every tag firing on the right trigger.
- ✓PageViewBrowser + ServerDeduplicated
- ✓ViewContentBrowser + ServerMatched
- ✓AddToCartBrowser + ServerMatched
- ✓InitiateCheckoutServerMatched
- ✓LeadBrowser + ServerMatched
- ✓Contact (WhatsApp)ServerLabelled: qualified
- ✓Purchase · £64.00ServerMatched · value sent
- ✓Call · 2m 14sCall trackingCounted
Set up before the first campaign, not after the first report.
Tag Manager containers I've built: a B2B SaaS funnel measured from free check to paid plan, a services website feeding five platforms behind consent, and an architecture studio with every enquiry route tracked.
CQC AI Auditor
8 funnel events, first check to purchase Read → Fast foodCheezious
36.88 average ROAS, tracked purchase by purchase Read → Architecture and interiorsArsyn
5 enquiry routes tracked, from one container Read → Digital servicesDigital Genix
5 platforms fed from one data layer Read →Is your ad account set up to learn?
Six yes-or-no questions. They're the first things I look at in any new account.
- 01
Is the Meta Conversions API (or server-side tagging) sending events alongside your pixel?
- 02
Are WhatsApp chats and phone calls tracked as conversions?
- 03
Is every campaign optimised for a lead or a sale, rather than traffic or engagement?
- 04
Do you test new creative at least every two weeks?
- 05
Do you exclude existing customers and recent converters from prospecting?
- 06
Does your reporting tie ad spend to actual sales, not only platform leads?
