Note
Updated May 2026. Conversion tracking is the highest-leverage Google Ads setup decision and the most frequently broken setup in operator audits. This guide covers the Google Tag vs GA4 import decision (Google renamed Conversions to "Key Events" in GA4 in March 2024), Enhanced Conversions with real lift figures from Google's published case studies, Server-side GTM via Stape or self-hosted, offline conversion imports with the 90-day attribution window, the Consent Mode v2 deadline that hit EEA + UK in March 2024, and the audit checklist we run on every new account. Real numbers, real Google docs references, real fix order.
Conversion tracking is the foundation of every Google Ads account that scales. Get it right and the algorithm has the signals it needs to bid accurately. Get it wrong and every dollar of optimization budget gets wasted. Most accounts we audit have at least one conversion tracking flaw - usually quiet, usually expensive.
This guide is the full 2026 setup: choosing between Google Tag and GA4 imports, configuring Enhanced Conversions, importing offline conversions, configuring Consent Mode v2, and the audit checklist we run on every new account.
Why conversion tracking matters more in 2026
Note
Conversion tracking definition. Conversion tracking is the practice of recording user actions after an ad click (purchases, leads, signups, calls) and reporting them back to Google Ads so its bidding algorithms can optimize toward those outcomes. Accurate conversion data is the input to every bid strategy more sophisticated than manual CPC. Google publishes the official setup docs at support.google.com/google-ads/answer/6095821.
The gap between accounts with strong conversion tracking and accounts with weak tracking has widened in 2026 for four documented reasons:
- iOS App Tracking Transparency has been ~70-80% opt-out since the 2021 launch, per Adjust and Branch's published industry data
- Chrome's third-party cookie deprecation rolled out fully in 2024, eliminating cross-site tracking for the largest browser segment
- Apple's Intelligent Tracking Prevention (ITP) caps first-party cookies at 7 days, limiting client-side attribution windows
- Server-side signal loss compounds - every step (browser to client SDK to platform attribution) drops some events
Smart Bidding strategies have published volume thresholds. Per Google's Smart Bidding documentation:
- Target CPA needs at least 15 conversions in the last 30 days
- Target ROAS needs at least 50 conversions in the last 30 days, ideally with conversion values
- Maximize Conversions can run lower but performs best above 30 conversions/30 days
Accounts with weak tracking now hit a hard ceiling - bidding algorithms cannot optimize what they cannot see, and they cannot reach Smart Bidding minimums when 30-50% of real conversions are lost to attribution gaps.
Google Tag vs GA4 Key Events import
The two ways to send conversions to Google Ads:
| Method | Best for | Tradeoff |
|---|---|---|
| Google Tag (gtag.js) | Direct e-commerce purchases, lead form submits, calls | Requires per-event implementation; reports within hours |
| GA4 Key Events import | Sites already using GA4 with event setup | Easier setup; 24-48hr reporting delay; secondary tier |
| Both (deduplicated) | Mature accounts wanting redundancy | Must use the same event_id or transaction_id to dedupe |
Important naming change: Google renamed "Conversions" to "Key Events" in GA4 in March 2024 to reduce confusion with Google Ads conversions. The mechanism is the same; only the UI label changed. In GA4 you "mark events as Key Events"; in Google Ads they remain "conversions" when imported.
For most accounts, the right call is Google Tag for the primary conversion (purchase or lead) and GA4 Key Events import for secondary signals (page views, cart adds, video watches, scroll depth) used as micro-conversion data feeding Smart Bidding.
Setting up Google Tag
- In Google Ads, go to Goals > Conversions > New conversion action
- Choose Website (or App, Phone, Import)
- Define conversion settings: count (every vs one), value (specific or dynamic), click-through window (default 30 days, max 90), view-through window (default 1 day, max 30), include in "Conversions" column (yes for primary)
- Install the tag via GTM (preferred) or directly via gtag.js
- Verify with Google Tag Assistant Companion (Chrome extension)
- Wait up to 24 hours for the conversion column to populate
Setting up GA4 Key Events import
- In GA4, mark events as Key Events (Admin > Data display > Events > toggle "Mark as key event")
- Link GA4 to Google Ads (Admin > Property > Google Ads links)
- In Google Ads, go to Goals > Conversions > New conversion action > Import > Google Analytics 4 properties
- Select the imported events; verify within 24-48 hours
Enhanced Conversions (the free 5-10% lift)
Enhanced Conversions send SHA-256-hashed first-party data (email, phone, name, address) alongside conversion events, allowing Google to match conversions to signed-in user data and recover signal lost to cookie restrictions and iOS ATT opt-out.
Enhanced Conversions
Any account doing 50+ conversions per month with email or phone available at conversion time
- Best for
- Any account doing 50+ conversions per month with email or phone available at conversion time
- Pricing
- Free
Pros
- Google's published case studies show 5-10% conversion recovery on average; some retail accounts see up to 17%
- Improves Smart Bidding model accuracy on iOS opt-out and Safari ITP traffic
- Enables better cross-device attribution
- Required for the most accurate Customer Match audience matching
- Free; only requires user data on the conversion page (email at minimum)
- Hashing happens client-side before transmission (privacy-preserving)
Cons
- Requires email or phone available on conversion page
- Privacy review required for some industries (HIPAA-regulated health, financial services)
- Implementation via gtag.js, GTM, or Google Ads API; pick one and stay consistent
Enhanced Conversions setup paths
- Via Google Tag (recommended). Add user-provided data fields to your gtag.js conversion event. Hashing happens automatically.
- Via GTM. Use the Conversion Linker tag plus a User-Provided Data variable referencing your form fields.
- Via Google Ads API. Programmatic setup for enterprise accounts; bulk-load already-hashed data.
In either case, ensure you have user consent and the page actually has email or phone available at conversion time.
Server-side GTM via Stape or self-hosted
Server-side Google Tag Manager (sGTM) is the highest-leverage tracking improvement for accounts that can support it. Instead of firing tags from the browser, the server sends conversions to Google Ads from your own infrastructure - bypassing browser-side blocking, ad blockers, and ITP.
| Path | Setup time | Monthly cost | Tradeoff |
|---|---|---|---|
| Stape (managed sGTM) | 1-2 hours | 20-100 USD | Easiest; managed hosting; popular with SMB to mid-market |
| Google Cloud sGTM (self-hosted) | 1-2 days | 120 USD typical (App Engine) | Cheaper at scale; more control; requires GCP knowledge |
| Custom server-side endpoint | 1-2 weeks | Variable (engineering) | Maximum control; only worth it for enterprise |
Operator-side benefits we see in audits after sGTM rollout: 8-15% additional recovered conversions on iOS-heavy accounts, ad-blocker traffic recovery (5-10% in some niches), faster page load (client-side tags removed), and Enhanced Conversions stability (server-side hashing is more reliable than client-side).
Offline conversion imports
For lead-gen accounts, the conversion that matters is not the form submit - it is the closed-won deal 30-90 days later. Offline conversion imports send those deals back to Google Ads.
Three setup paths
- GCLID upload. Capture GCLID at form submit, store with the lead, upload to Google Ads with conversion details when the deal closes. Manual via Conversions > Uploads, or programmatically via the Google Ads API.
- Salesforce/HubSpot integration. Native CRM connectors push closed-won deals back to Google Ads automatically. Salesforce's offline conversion import was launched in 2017; HubSpot's in 2018.
- Webhook + Zapier/Make. Custom pipeline if your CRM is not natively supported.
The window: every closed-won deal back in Google Ads within 90 days of original click - that's the maximum click-through attribution window Google supports for offline imports. Smart Bidding then optimizes toward closed-won deals, not just form submits, dramatically improving lead quality over time.
Consent Mode v2 (mandatory in EEA + UK)
Google Consent Mode v2 became mandatory for advertisers running ads to EEA and UK users on March 6, 2024. Without consent mode, ads don't fully attribute and remarketing audiences shrink.
Two modes:
- Basic Consent Mode: tags don't fire until consent given. Conversions only count from consented users.
- Advanced Consent Mode: tags load but signal-loss with consent-declined users; Google models the lost data using consented-user patterns. Recovers 30-65% of lost conversions per Google's published modeling case studies.
Implementation:
- Configure your Consent Management Platform (CMP) - OneTrust, Cookiebot, CookieYes, Iubenda, etc.
- Pass consent signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) via gtag or GTM
- Verify in Google Tag Assistant Companion that consent signals are present on tag fires
- Monitor Consent Mode reporting in Google Ads (Admin > Account access > Consent overview)
Most US-only accounts can skip this. EEA/UK or globally distributed accounts must run it.
Conversion windows and Smart Bidding thresholds
The conversion window is the maximum time between ad click and conversion that Google attributes to the ad. Defaults vs business reality:
| Use case | Recommended window | Rationale |
|---|---|---|
| Impulse e-commerce (under 100 USD) | 7 days click + 1 day view | Short consideration; longer windows add noise |
| Considered e-commerce (100-1,000 USD) | 30 days click (default) | Standard; matches typical research-to-purchase |
| High-ticket DTC (1K+ USD) | 30-60 days click | Longer consideration; capture full journey |
| B2B / SaaS lead gen | 60-90 days click | Sales cycle length; matches CRM lifecycle |
| App installs | 1 day post-install | Default for app campaigns; SKAdNetwork constraints on iOS |
Smart Bidding thresholds (per Google's documentation):
- Target CPA: 15+ conversions in last 30 days (account level for Performance Max; ad group level for Search)
- Target ROAS: 50+ conversions in last 30 days, ideally with conversion values
- Maximize Conversions: works at lower volume; performs best above 30/30 days
- Enhanced CPC: legacy strategy; works with any volume but sub-optimal vs Smart Bidding strategies
The audit checklist
This is the audit we run on every new Hyper customer Google Ads account. We catch issues in 80%+ of new audits.
What we check
- One primary conversion per goal (e.g., "Purchase" for e-commerce; not Purchase + Lead Form + Newsletter as primary)
- Enhanced Conversions enabled and verified via Diagnostics tab
- GCLID captured at form submission and stored with the lead in CRM
- Conversion windows match real business behavior (not the default 30-day click for everything)
- Conversion values populated (not flat 1.00 USD across all conversions)
- Cross-account conversions configured correctly if running multiple accounts
- Tag firing verified via Tag Assistant in production (not just preview mode)
- Conversion column in Google Ads populated within 24-48 hours of test conversion
- Consent Mode v2 implemented if running ads in EEA/UK
- Server-side GTM running on accounts with 50K+ USD/month spend
- Offline conversion import pipeline running for lead-gen accounts
- No double-counting from both Google Tag AND GA4 import on the same event without dedup
Common findings
The five issues we catch most often on first audit:
- Multiple primary conversions per campaign (Smart Bidding can't optimize toward two goals; pick one)
- Missing Enhanced Conversions - free 5-10% lift sitting on the table
- No GCLID capture on lead forms - closes never get back to Google Ads; Smart Bidding optimizes toward forms, not deals
- Conversion value left at 1.00 USD - algorithm cannot prioritize high-value conversions because they all look equal
- Cross-domain tracking broken - conversions on a separate checkout domain attributed as direct, not paid
Conversion tracking decision tree
Do this
Recommended: One primary conversion per goal. Enhanced Conversions enabled. GCLID captured at form submission. Conversion windows match business reality (90 days for B2B, 30 for considered, 7 for impulse). Conversion values populated. Server-side GTM running for accounts above 50K USD/month spend. Consent Mode v2 if running EEA/UK. Tag firing verified via Tag Assistant in production. Re-audit every 90 days.
Avoid
Recommended: Counting both 'lead form' and 'purchase' as primary conversions in the same campaign. Setting up conversions and never auditing again. Letting the conversion window default to 30 days for a 7-day buying cycle product. Stuffing every micro-conversion as primary (signups, page views, scrolls). Forgetting GCLID storage on lead forms. Importing GA4 conversions and Google Tag conversions for the same event without deduping via transaction_id.
Autonomous marketing
Grow your business faster with AI agents
- Automates Google, Meta + 5 more platforms
- Handles your SEO end to end
- Improves website conversions
- Runs social media for you
How Hyper helps
Hyper's Google Ads agent runs a daily check on the conversion tracking setup - flagging tag misfires, missing GCLIDs, conversion value drops, stale offline conversion imports, Enhanced Conversions misconfigurations, and Consent Mode v2 issues. Most accounts find a 5-15% recovery just by fixing tracking flaws on day one. The case study at /blog/ai-marketing-case-study shows the audit and remediation flow.
Across 1,000+ customer accounts and 10M+ USD/month managed ad spend, conversion tracking issues are the most common cause of underperformance we catch in the first 30 days of a new customer onboarding - usually before the customer realized anything was wrong.
Autonomous marketing
Grow your business faster with AI agents
- Automates Google, Meta + 5 more platforms
- Handles your SEO end to end
- Improves website conversions
- Runs social media for you
Frequently asked questions
Q: What is the difference between Google Ads conversions and GA4 conversions?
Google Ads conversions are tracked specifically for ad attribution and bidding. GA4 conversions (now called 'Key Events' in GA4 since March 2024) are tracked for analytics across all traffic sources. They can both fire from the same user action, but the data flows to different destinations. Importing GA4 Key Events into Google Ads bridges the two; deduplication via transaction_id prevents double-counting.
Q: How do I know if my conversion tracking is working?
Three checks: (1) Google Tag Assistant Companion shows the tag firing on the conversion page in production (not just preview), (2) the conversion column in Google Ads shows data within 24-48 hours of a test conversion, (3) the conversion count roughly matches what your CRM or back-end shows within +/- 10%. Larger gaps signal a tracking issue.
Q: Should I count every micro-conversion as primary?
No. Mark only the conversion that represents real business outcome (purchase, qualified lead, booked call) as primary. Track micro-conversions (page views, video watches, cart adds) as secondary. Smart Bidding optimizes toward primary; secondary feeds the model as additional signal without controlling the optimization target.
Q: What is a conversion window and what should I set it to?
The conversion window is the maximum time between ad click and conversion that Google attributes back to the ad. 30 days is the default click-through window and works for most. Use 7 days for impulse buys, 60-90 days for considered purchases (B2B, big-ticket retail). Match the window to real customer behavior in your CRM.
Q: Do I still need conversion tracking with Consent Mode?
Yes. Consent Mode adjusts what data flows but does not replace conversion tracking. With Consent Mode v2 advanced enabled, Google models the conversions of consent-declined users using the data of consented users. The accuracy of that modeling depends on having enough consented conversions to model from - making conversion tracking even more important. Google's published modeling case studies show 30-65% recovery of consent-declined conversions when properly configured.
Q: What is server-side GTM and do I need it?
Server-side Google Tag Manager (sGTM) sends conversions to Google Ads from your own server instead of from the browser - bypassing ad blockers, ITP, and iOS opt-out. We recommend it for accounts spending 50K+ USD/month on Google Ads, where the 8-15% additional conversion recovery pays back the 20-100 USD/month Stape hosting cost many times over.
Q: How do offline conversion imports work?
Capture the GCLID (Google Click ID) at the moment of click, store it with the lead in your CRM, and when the deal closes (within 90 days max), upload the conversion via the Google Ads API or manually via Conversions > Uploads. Native Salesforce and HubSpot connectors do this automatically. Smart Bidding then optimizes toward actual closed deals instead of just form submits.
Q: What happened to GA4 conversions becoming Key Events?
Google renamed 'Conversions' to 'Key Events' inside GA4 in March 2024 to reduce confusion with Google Ads conversions. The mechanism is identical; only the UI label changed. In GA4 you 'mark events as Key Events'; when imported to Google Ads they appear as 'conversions' there. No setup change required for accounts that already had conversions configured.