What actually broke, and when
Until 2021, most small businesses got by with one Meta pixel and one Google Ads conversion tag, and that was genuinely enough. Two separate shifts changed that:
- In 2021 Apple launched App Tracking Transparency (ATT) with iOS 14.5, requiring apps to request explicit consent before tracking across other apps and websites. Meta itself said on its February 2022 earnings call that the change was expected to cost roughly $10 billion in 2022 revenue alone (source: cnbc.com).
- Adjust's Q2 2025 data shows the opt-in rate among iOS users shown the tracking prompt sitting at around 35% - a slow, modest rise over three years (source: adjust.com). In practice, most iPhone users - a sizable share of visitors in Western markets - block tracking by default, and no browser pixel can see them.
- At the same time, as of March 6, 2024, Google made Consent Mode v2 a requirement for anyone who wants to keep using Google Marketing Platform features (remarketing, audiences) on traffic from the EEA and UK - without proper consent signals, Google simply excludes those users from audience data (source: cardinalpath.com).
The practical result: even with a cookie banner in place, and even with the pixel "installed" and firing, measurement still misses a large number of visitors before a single data point is ever written.
The other gap: "form submitted" isn't "deal closed"
Even a business that solved the technical blocking problem is left with a second, more business-critical problem: standard pixel-based measurement stops at "form submitted" or "call booked." But not every lead who fills out a form becomes a paying customer - some get filtered out, some never close, some cancel. If ads are optimized toward "form submitted" rather than "deal closed," Meta's or Google's ad algorithm learns to bring you more people who fill out forms - not more people who buy. Those are often two different audiences, usually at two different acquisition costs.
How to actually set this up
- GA4 - set up conversion event tracking (not just page_view), with the Google tag wired to Consent Mode v2 parameters (
ad_user_data,ad_personalization) on page load, before the visitor makes a choice. - Meta Conversions API - an event fired from the server, not just the browser, matched with a shared
event_idagainst the Pixel so Google and Meta don't count the same conversion twice. - GoHighLevel as the bridge between ad spend and the actual sale - a workflow triggered when a lead card's pipeline stage changes (for example, to "deal won"), which fires a matching conversion event from the server to Meta's Conversions API and GA4's Measurement Protocol. This is what closes the loop between an ad click and a deal that was actually paid for, instead of stopping at "lead came in."
The common mistakes that ruin the data
- Turning on Conversions API without deduplication - the same conversion gets counted twice, and the reported cost-per-conversion looks better than it actually is.
- Switching the conversion event to "deal closed" before enough historical data has accumulated - ad algorithms need event volume to learn, and a sudden switch with no transition period breaks optimization that was already working.
- A cookie consent banner that never actually fires
gtag('consent', 'update', ...)on "accept" - the banner exists, but as far as Google is concerned, consent was never given.
Not sure if your tracking is accurate?
We build and audit conversion tracking - GA4, Meta CAPI, and a GoHighLevel connection - as part of a website or automation project, not as an afterthought bolted on at the end.
Get started