Google Ads and Google Analytics measurement setup
Google Ads and Google Analytics measurement setup
This domain tests whether you can build a trustworthy measurement foundation across Google Ads, Google Analytics 4, and the Google tag. Expect questions on account linking, tag implementation, conversion actions, consent, attribution settings, and data-quality checks.
Core rules
- Link Google Ads and GA4 at the correct level: a GA4 property links to a Google Ads account, and the Ads account links back. You need edit or admin rights on both. The link passes auto-tagged click IDs (gclid) and enables Ads reports in GA4 and conversion imports into Ads.
- Keep auto-tagging enabled. GA4 uses gclid to attribute sessions and conversions to Ads. Manual UTM tags remain useful for non-Ads channels, but they do not replace gclid for Ads attribution.
- Implement one Google tag per destination. Use gtag.js or Google Tag Manager; a GA4 configuration tag sends page views and events, and a Google Ads conversion tag fires on the conversion event. Verify with Tag Assistant and GA4 DebugView.
- Define conversion actions deliberately. A conversion action has a source (Google Ads tag or imported GA4 key event), a counting method (every conversion or one per click), a click-through window, a view-through window, and an attribution model (data-driven is the default). Mark actions used for bidding and reporting as primary; mark diagnostic actions as secondary.
- Use consent-aware tagging. Consent Mode passes end-user consent choices to Google tags; when consent is denied, tags send cookieless pings and Google may model conversions. Configure consent before tags fire and test granted and denied states.
- Improve match quality with enhanced conversions where appropriate: hashed email, phone, or address from your own forms can recover conversions that cookies miss.
Worked example
An online retailer imports the GA4 purchase key event into Ads as a conversion action. It sets the action as primary, uses data-driven attribution, a 30-day click window, and a 1-day view window. Auto-tagging stays on, so Ads clicks carry gclid into GA4. The Google Ads conversion tag is not separately fired for purchase, avoiding double counting. Consent Mode is deployed before the Google tag, and enhanced conversions collect hashed email on order confirmation. Reasoning: one purchase produces one Ads conversion, and bidding uses a defined primary action.
Traps
- Firing both an Ads conversion tag and an imported GA4 purchase event for the same purchase, which double counts.
- Disabling auto-tagging, then expecting GA4 to attribute Ads clicks.
- Importing a non-key event, or marking every action primary so bidding chases low-value signals.
- Ignoring consent state, then comparing pre- and post-consent data without accounting for modeled conversions.
- Mismatching time zones or currency, or treating last-click GA4 and data-driven Ads reports as identical.