To implement sitewide tagging, what do you have to do?
- You have to turn off auto-tagging in all your Google Ads accounts that are enabled for sitewide tagging.
- You have to make sure Google Click Identifier (GCLID) still works if using click trackers in the URL.
- You have to use just the image portion of the JavaScript.
- You have to make sure the tag still works by loading it within another tracking tag, like Floodlight.
Explanation:
To implement sitewide tagging, you have to make sure Google Click Identifier (GCLID) still works if using click trackers in the URL. This option is correct because sitewide tagging involves deploying a single Google Ads conversion tracking tag across all pages of a website, allowing for comprehensive tracking of user interactions and conversions. However, if click trackers are used in the URL, such as UTM parameters or other tracking mechanisms, it’s crucial to ensure that the Google Click Identifier (GCLID) parameter is preserved and passed along with the URL parameters to maintain accurate conversion tracking and attribution in Google Ads. The GCLID parameter is a unique identifier appended to the URL when a user clicks on a Google Ads ad, enabling Google Ads to attribute conversions back to specific ad clicks. By ensuring that the GCLID parameter remains intact, even when click trackers are utilized, sitewide tagging can effectively capture conversion data and provide valuable insights into campaign performance across the entire website. The other options listed—turning off auto-tagging in Google Ads accounts, using just the image portion of JavaScript, or loading the tag within another tracking tag like Floodlight—are not necessary steps for implementing sitewide tagging and are therefore incorrect.