What's a requirement for implementing sitewide tagging?
Make sure the tag still works by loading it within another tracking tag, like Floodlight.
Use just the image portion of the JavaScript.
Make sure Google Click Identifier (GCLID) still works if using click trackers in the URL.
Turn off auto-tagging in all your Google Ads accounts that are enabled for sitewide tagging.
Explanation
Analysis of Correct Answer(s)
The core purpose of sitewide tagging for Google Ads is to accurately measure conversions. This is achieved by linking a click on an ad to a conversion action on your website.
- The Google Click Identifier (GCLID) is the key parameter that connects the ad click to the website session. It's automatically appended to your landing page URL when auto-tagging is enabled.
- Some third-party click trackers or redirect systems can unintentionally strip parameters like the GCLID from the final URL.
- If the GCLID doesn't reach the landing page, the sitewide tag cannot attribute the conversion to the Google Ads campaign. Therefore, ensuring the GCLID is preserved is a fundamental requirement for the system to work correctly.
Analysis of Incorrect Options
- Turn off auto-tagging: This is the opposite of what's required. Auto-tagging must be enabled in Google Ads for the GCLID parameter to be added to your URLs, which is essential for conversion tracking.
- Use just the image portion of the JavaScript: This refers to a non-JavaScript or
<noscript>fallback. Modern, robust tracking relies on the full JavaScript to set first-party cookies and enable advanced measurement features. Relying only on an image pixel is an outdated and less effective method. - Make sure the tag still works by loading it within another tracking tag, like Floodlight: This describes a practice called "piggybacking," which is not a requirement and is generally discouraged. It can slow down your site and lead to data discrepancies. Tags should be implemented directly on the page or through a tag management system like Google Tag Manager.