25 to 35% of Google Ads accounts have broken or incomplete conversion tracking (depending on sector and size). Without a clean signal, Smart Bidding optimizes on noise and no strategy compensates — this guide lays the 2026 foundations: GTM, Enhanced Conversions, Consent Mode v2, verifications.
If you manage a Google Ads account and you're not absolutely certain that all your conversions are tracked correctly, this guide is for you. Across the accounts we observe, 25 to 35% have broken or partial tracking (depending on sector and size) — and in most cases, no one notices before months of wasted budget.
The problem is silent: Google Ads keeps reporting conversions, Smart Bidding keeps "working," dashboards stay green. But under the hood, the algorithm is optimizing toward an incomplete or false signal, and your real CPAs run 2 to 4 times above what's displayed.
This guide covers everything a dev or marketer needs to know in 2026: the 3 tracking methods (gtag, GTM, server-side), the 5-step GTM setup, Enhanced Conversions (+30% precision), Consent Mode v2 (mandatory in EEA since March 2024), how to verify everything works, and the 5 pitfalls to avoid.
Why is tracking the Google Ads foundation?
Google Ads runs on a simple feedback loop: you send traffic, some users convert, Google records the signal, Smart Bidding learns "this click converted, those didn't" and adjusts bids accordingly. If that signal is broken — missing, duplicated, mis-attributed — the entire optimization chain collapses.
Concretely: without clean tracking, Smart Bidding optimizes "into thin air." The algo sees 100 clicks, 0 conversions (or 10 false positives), and concludes either that your campaigns are bad (it cuts volume) or excellent (it raises bids on random signals). Either way, real CPA drifts: we regularly observe real CPAs 2 to 4× above the Google Ads reported CPA on poorly tracked accounts.
It's also the difference between an account that scales and an account that plateaus. With reliable tracking, you can apply our 10 levers to cut CPA with confidence. Without it, it's like flying a plane without an altimeter. In fact, error #3 in our top 10 Google Ads errors is precisely "broken tracking" — it's problem #1 on the accounts we audit.
Which tracking method to choose: gtag, GTM, or server-side?
Three technical approaches exist for sending your conversions to Google Ads. Each trades off simplicity, flexibility, and precision. Here's how to choose:
Verdict: for 90% of accounts, GTM is the right choice. That's the method we detail in the next section. Reserve server-side for high volumes (>50,000 conversions/month) or high client-side loss rates (adblockers, Safari ITP).
How do you configure GTM tracking in 5 steps?
Budget 30 to 60 minutes for a clean setup. The steps below assume you have Google Ads access and can modify your site's code (or work with a dev).
Step 1 · Create the GTM container
Head to tagmanager.google.com. Create an account (your company name), then a container (type "Web," your site's URL). GTM gives you two snippets to paste: one in <head>, the other right after the opening <body>. On a Next.js site, use next/script with the afterInteractive strategy.
Step 2 · Create the conversion action in Google Ads
In Google Ads → Tools → Measurement → Conversions → New action → Website. Set: name ("Purchase," "Lead form"…), category (Purchase, Lead…), value (fixed or dynamic), counting (One for leads, Every for purchases), attribution window (30 days by default). Carefully note the Conversion ID (format AW-XXXXXXXXXX) and the Conversion Label — you'll need them in GTM.
Step 3 · Configure the Google Ads tag in GTM
In GTM → Tags → New → Type "Google Ads Conversion Tracking." Paste Conversion ID + Label. For a dynamic value (e-commerce), use a data layer variable: {{DLV - transaction_value}}. Trigger: "Page View" on /thank-you for a simple conv., or "Custom Event" for a code-side dataLayer push event.
Step 4 · Push events from your code
After a confirmed purchase, your code pushes the event into the data layer:
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: "purchase",
transaction_id: "ORDER-12345",
transaction_value: 89.90,
currency: "USD",
customer_email: "user@example.com" // for Enhanced Conversions
});
On the GTM side, the "Custom Event" trigger with event = purchase fires the Google Ads tag, which sends the conversion.
Step 5 · Test in Preview mode, then publish
In GTM → Preview (top-right corner). Connect to your site, reproduce a test purchase. Verify that the Google Ads tag appears in "Tags Fired." Once validated: click "Submit" → version name → Publish. The tag is live.
How does Enhanced Conversions boost precision by +30%?
Enhanced Conversions is the most underrated Google Ads feature of the past two years. The principle: you send Google, along with the conversion itself, hashed first-party data (email, phone, name). Google matches that hashed data against its connected Google accounts and recovers conversions that would have been lost to blockers, Incognito mode, or cross-device (mobile → desktop).
According to Google officially, Enhanced Conversions delivers +30% precision on average on conversions reported, up to +50% in heavily mobile sectors (B2C e-commerce).
On an account already tracked with GTM, enabling Enhanced Conversions literally takes 5 to 15 minutes. In GTM → your Google Ads Conversion tag → "Include user-provided data" → select the dataLayer variables (email, phone). In Google Ads: Tools → Conversions → your action → Enhanced Conversions → enable and validate. It's the best time ROI available today.
GDPR prerequisite: you need user consent to send their hashed data (see next section). Without consent, no user data is sent — Google only works with the anonymous conversion.
How do you implement Consent Mode v2 since March 2024?
Since March 2024, Google has mandated Consent Mode v2 for all advertisers serving in the European Economic Area. If you haven't implemented it, your remarketing and personalized-audience campaigns are already degraded — and will be more so in the coming months.
Consent Mode v2 manages 4 consent signals that your CMP (Cookiebot, OneTrust, Axeptio…) must pass to Google:
ad_storage— advertising cookies (remarketing)analytics_storage— GA4 cookiesad_user_data— new in v2, sending user data to Googlead_personalization— new in v2, ad personalization
By default (user hasn't clicked the banner yet), all these signals are denied. When the user accepts, the CMP pushes a consent update event that flips signals to granted. Google uses conversion modeling — a statistical model that fills the gaps — to estimate missing conversions from users who declined.
If your CMP isn't configured for Consent Mode v2, Google treats all your EEA visitors as refusers, which drops your reported conversion volume by 30 to 60% — with no visible error in Google Ads. Many accounts audited in 2025 have this exact problem: green dashboards, skewed CPAs. Test with the Tag Assistant Companion extension that your consent is properly transmitted.
Official documentation: Consent Mode — Google guide.
How do you verify your tracking works?
Tracking you don't test is tracking you can't trust. These 3 tests take under 5 minutes each, to redo after every deployment.
Test 1 · Tag Assistant Companion
Install the Google Tag Assistant Chrome extension. Activate it on your site, trigger a test conversion. The extension shows all fired tags, parameters sent, and potential errors (invalid ID, missing value, consent refused…). It's the fastest test to validate a setup.
Test 2 · Google Ads diagnostic
In Google Ads → Tools → Conversions → click your action → "Diagnostics" tab. Google lists: "Recording conversions," "No recent conversions," "Tag issue detected"… If the status is green for more than 7 days, the tag is operational. Any other value = investigate.
Test 3 · Continuous monitoring and alerts
A frontend deployment can break tracking without warning. The solution: monitoring that compares daily conversion count to the trailing 30-day baseline and alerts on a sudden drop. That's exactly what SteerAds anomaly detection does automatically: alerts in under an hour as soon as a conversion counter drops more than 40% vs baseline.
What are the 5 most common tracking mistakes?
Here's the standard path of a conversion, from the end user to Smart Bidding, with the most common break points:
The 5 errors that silently break the chain:
- Double tracking. You kept the old direct gtag tag in the code AND added GTM. Result: every conversion is counted twice. Displayed CPA is halved, Smart Bidding over-bids, real CPA explodes.
- Conversion on confirmation page view that refreshes. If the user reloads
/thank-you, the tag fires again. Solution: use apurchaseevent with a uniquetransaction_idand deduplication on the Google Ads side. - Consent Mode missing. All your EEA visitors are treated as "refused" by Google. Reported conversion volume -30 to -60% with no alert (see callout above).
- Hard-coded value instead of dynamic. Your tag sends
value: 50on every conversion instead of the real cart value. Impossible to optimize in Target ROAS, Smart Bidding confuses a $20 cart and a $500 cart. - Tag broken after frontend deployment. The dev team refactors the checkout component, forgets to re-wire the dataLayer. Zero conversions reported for 2 weeks. Without monitoring (anomaly detection), no one notices before the monthly review.
How do you add offline conversions to advanced tracking?
For businesses with long sales cycles (B2B, real estate, education…), the real conversion doesn't happen on the site but weeks later, in the CRM: contract signed, first invoice paid, demo converted to customer. That's where Offline Conversions come in.
The principle: your form captures a gclid (Google Ads click identifier) at submission, stored with the lead in your CRM. When the lead actually converts (contract signed), you send the gclid back to Google Ads via Google Sheets, the API, or a HubSpot/Salesforce connector, with the real deal value.
Result: Smart Bidding optimizes toward real profitable conversions (signed contracts), not filled forms that never close. It's the most powerful lever for B2B with a low CPA-lead but a high real CAC. Budget 2 to 5 days of setup depending on CRM maturity. Covered in detail in our Smart Bidding guide.
Sources
Official sources consulted for this guide:
FAQ
Is tracking mandatory for Smart Bidding?
Yes, absolutely. Smart Bidding (Target CPA, Maximize Conversions, Target ROAS) cannot work without a reliable conversion signal. The algorithm needs at least 30 conversions over 30 days to exit its learning phase. Without clean tracking, it optimizes into thin air: observed CPAs drift 2 to 4× above target, volume collapses, and budgets are wasted on the wrong clicks.
GTM vs direct gtag: which to pick in 2026?
Google Tag Manager in 90% of cases. GTM centralizes all your tags (Ads, GA4, Meta, LinkedIn…) in a single interface, without touching code for every addition. Direct gtag only makes sense for ultra-simple sites with a single tag, or when internal IT policy forbids third-party scripts. The GTM entry cost (30 min) is easily recovered by the 2nd modification.
How long to implement Consent Mode v2?
Budget 2 to 4 hours if you already have a CMP (Cookiebot, OneTrust, Axeptio): v2 activation, signal mapping for ad_storage, analytics_storage, ad_user_data, ad_personalization. Between 1 and 2 days if you're starting from zero: CMP selection, integration, testing. Implementation has been mandatory since March 2024 for serving personalized ads in the EEA.
When do you switch to server-side tracking?
Switch to server-side when you have more than 50,000 conversions/month, or when your client-side loss rate exceeds 15% (adblockers, Safari ITP, mobile blockers). Server-side improves precision by 10 to 25% and secures your first-party data. Cost: 1 to 3 days of setup + ~$25/month of Cloud Run hosting or equivalent. Otherwise, client-side GTM + Enhanced Conversions are enough.