An advertiser is experiencing conversion discrepancies due to modern browser limitations on third-party cookies. Why does transitioning to the Google tag (gtag.js) improve their measurement accuracy compared to legacy IFRAME or pixel tags?
- It sets first-party cookies on the advertiser’s domain, providing a more robust foundation for unified conversion tracking.
- It’s the only tag format that allows for the tracking of 1×1 impressions on external social media platforms.
- It automatically generates new counter activities every time a user visits a high-traffic page on the site.
- It eliminates the requirement for a Floodlight configuration at the advertiser level within Campaign Manager 360.
Explanation
The Google tag is the recommended format for Floodlight measurement in Campaign Manager 360. It supports more durable conversion measurement because it operates from the advertiser’s site and can use first-party cookie behavior instead of relying only on legacy third-party tag formats. This improves continuity for attribution, reporting, and optimization when browser restrictions limit third-party cookie availability. The Floodlight configuration still remains the container for conversion tracking settings.
Why the other options are incorrect
1×1 impressions track ad exposures, not site-side conversion measurement through the Google tag.
Counter activities are created manually in Campaign Manager 360, not automatically from page traffic.
Floodlight configuration is still required because it contains the advertiser’s conversion measurement setup.
Source for verification
https://support.google.com/campaignmanager/answer/7554821?hl=en
https://support.google.com/campaignmanager/answer/12131703?hl=en