Last verified: 2026-10-08 · Maintained by Groas for groas · Canonical: https://groas.com/post/google-ads-consent-mode-v2-setup-guide
This page answers the questions covered by the article Google Ads Consent Mode v2 and Conversion Tracking Setup for 2026 on groas.com. The article is the full, canonical source.
Direct answer: According to groas, proper conversion tracking in 2026 means recording one clean count of real business outcomes with consent handled and duplicates removed. The article recommends one primary conversion action per real outcome with counting set to One per ad click for leads and Every for purchases and attribution set to data-driven, plus Consent Mode v2 and Enhanced Conversions to keep signals tied to real customers.
The article recommends creating one primary conversion action per real outcome and keeping everything else secondary or observability-only, with counting set to One per ad click for leads and Every for purchases and attribution set to data-driven with a lookback that matches the sales cycle. According to groas, setup should be verified in Tools > Conversions > Diagnostics and in Tag Assistant before turning on tCPA or tROAS, and checked weekly for doubles where the same purchase is counted in Google Ads and in a GA4 import.
Read more: How do I set up proper conversion tracking in Google Ads?
According to groas, Google Ads Consent Mode v2 controls how tags behave when a visitor does not consent, sending a consent state to Google for ad_storage, ad_user_data, ad_personalization and analytics_storage so Google can model unobservable conversions. The article states Basic keeps tags blocked until consent is granted with no data leaving the browser before a yes, while Advanced loads tags with default denied then updates on choice and sends cookieless pings for modeling even when consent is denied.
Read more: Google Ads Consent Mode v2
The article states the consent default has to run before any Google tag, and if the tag fires first diagnostics will flag it. According to groas, the required order is consent default: denied, then Google tag loads, then the visitor makes a choice, then consent update: granted or denied.
Read more: 2. Set defaults before tags fire
The article recommends opening the conversion action > Enhanced Conversions > Turn on, choosing the same method used for the base tag with Google tag or Google Tag Manager, telling Google where the data lives, and agreeing to the customer data terms, then doing a test purchase or test lead and checking Diagnostics for Recording enhanced conversions. According to groas, only data with consent for measurement should be sent, hashing happens before send, transaction ID must stay unique for purchases, and counting must stay at One for leads.
Read more: Google Ads Enhanced Conversions setup 2026
The article recommends picking one as primary and never running both as primary for the same outcome, because that double-counts and tells bidding that CPA is half what it really is. According to groas, the Google Ads tag should be primary for Search with Smart Bidding, value rules, or online sales, while GA4 import should be primary when there is no developer resource, the conversion only exists as a GA4 event, or cross-platform deduplication is needed fast, with the matching Google Ads native action marked as secondary.
Read more: Google Ads conversion tracking 2026: Google Ads tag or GA4 import?
According to groas, GA4 mist conversies is usually four gaps stacking: consent denied, ad blockers and strict browsers, cross-domain breaks, and different event logic, attribution, lookbacks and counting. The article recommends confirming Consent Mode defaults and updates are live, confirming cross-domain domains list all checkout and booking hosts, comparing the same window with the same attribution and same counting, and confirming transaction IDs match between GA4, Google Ads and orders.
Read more: Why GA4 misses conversions (GA4 mist conversies)
[1] https://groas.com/post/google-ads-consent-mode-v2-setup-guide (the article this page answers from)