Study first
Review the ideas behind the questions
Review the GTM setup choices that affect Google Ads conversion measurement. Focus on the Google tag, Conversion Linker, conversion ID and label, enhanced conversions, cross-domain journeys, and the proof needed before a conversion action is trusted.
Start with the right Google tag setup
Google Ads conversion tagging in GTM depends on the tag foundation and the conversion action details. Checks should confirm the tag ID, conversion ID, conversion label, and firing event before judging performance data.
- The Google tag in GTM supports Google destination IDs for products such as Google Ads and Google Analytics.
- A Google Ads conversion tracking tag in GTM uses the conversion ID and conversion label from the conversion action.
- The tag trigger should match the conversion action, such as the thank-you page or the confirmed user action.
In Practice
ID and label identify the action
Two conversion actions can share an account but use different labels. Copying the wrong conversion label can send the right event to the wrong conversion action.
The trigger proves the business event
For a lead conversion, a broad page view or any submit-button click can be too loose. Use a trigger that represents the confirmed conversion, such as a tested thank-you page or success event.
Common mistakes
Using the same conversion label for every lead, signup, and purchase tag.
Match each GTM conversion tag to the conversion ID and conversion label for the intended Google Ads conversion action.
Q&A
What should be copied from the Google Ads conversion action into GTM?
Copy the conversion ID and conversion label for that specific conversion action.
Why should the trigger be reviewed before launch?
The trigger decides when the conversion tag fires, so it needs to match the confirmed conversion action.
Preserve ad-click attribution signals
Google Ads conversions need enough click context to connect a later conversion with an earlier ad click. The Conversion Linker and cross-domain settings should be reviewed before traffic moves across pages or domains.
- The Conversion Linker tag stores ad-click information in first-party cookies on the site.
- The Conversion Linker should normally fire on all pages so landing-page click data can be stored.
- Cross-domain measurement needs linker configuration when activity spans multiple domains.
In Practice
All Pages is a coverage choice
If the Conversion Linker fires only on the final thank-you page, it can miss click information from the landing page. Review page coverage before conversion traffic starts.
Cross-domain journeys need planning
When ads land on one domain and checkout or signup finishes on another, conversion checks should include the domain handoff. A one-domain setup assumption can lose the link between the click and the conversion.
Common mistakes
Adding the conversion tag but ignoring the Conversion Linker.
Review whether the Conversion Linker fires with enough page coverage to store ad-click information before conversion tags need it.
Q&A
Why is a thank-you-page-only Conversion Linker weak?
It may miss the ad-click information that arrived on the landing page URL.
Handle enhanced conversions carefully
Enhanced conversions add user-provided data to improve matching. That means the GTM setup must respect the documented method, source of the data, and privacy-sensitive handling before any tag is published.
- Enhanced conversions for web can be set up with Google Tag Manager.
- Enhanced-conversion setup depends on user-provided data being available in the selected page source, data layer, or variable method.
- A privacy review should confirm that the selected user-provided data source is intentional before launch.
In Practice
Automatic detection is not a substitute for checks
If the data is not consistently present on the conversion page, automatic or selector-based setup can miss values. Confirm the actual conversion flow and the selected data source.
Use the data layer when the page needs a cleaner handoff
When user-provided data is generated by the app after a confirmed action, a documented data layer source can be cleaner than scraping a changing page element.
Common mistakes
Turning on enhanced conversions without checking where the customer data comes from.
Choose and test the documented user-provided data source, then confirm it is available only in the intended conversion flow.
Q&A
What should be checked before publishing enhanced conversions through GTM?
Check the selected user-provided data source and confirm it is present in the intended conversion flow.