How Google tag gateway for advertisers sets location

Google tag gateway for advertisers improves measurement accuracy and supports data privacy, using your Content Delivery Network, Content Management System, or load balancer to serve Google tags through your own website's domain. Accurate location data enables precise reporting in Google Ads and Google Analytics for effective campaign optimization and regulatory compliance.

Understand location determination

The user's browser communicates directly with Google in a standard tag setup. Google infers the user's location from their IP address.

With Google tag gateway for advertisers, the user's browser interacts with your domain. This could be your Content Delivery Network, Content Management System, or load balancer. Your domain then forwards the tag requests to Google. Google's backend receives your Content Delivery Network's IP address. It doesn't receive the user's original IP. Therefore, your Content Delivery Network must explicitly attach geolocation headers. This ensures accurate user region determination.

Without these headers, Google can't accurately determine the user's region. This can result in inaccurate geographic data in your reports. Issues with region-specific consent defaults may arise if using Consent Mode. Potential data quality problems could also result.

Configure location for Google tag gateway for advertisers

1. Use integration-based solutions (automated configuration)

You can set up Google tag gateway through automated integrations. These include Cloudflare One-Click, Webflow CMS Integration, Google Cloud Load Balancer automatic setup, or Akamai automated integration. For this setup, geolocation header configuration is typically automatic. The respective Content Delivery Network or platform handles it.

You generally don't need to take specific action. The integration automatically passes the necessary data to Google. Cloudflare automatically enables "Add visitor location headers," for example, Google Cloud Load Balancer automatically adds X-Forwarded-Country and X-Forwarded-Region headers.

2. Implement manually

You can manually implement Google tag gateway for advertisers on specific Content Delivery Networks. Examples include Akamai Manual, AWS CloudFront, Azure Front Door, or Cloudflare Enterprise Manual. You must actively configure your Content Delivery Network. This ensures correct setting and forwarding of geolocation headers.

Google expects geolocation data in specific HTTP header formats:

Preferred (Combined Country & Region): X-Forwarded-CountryRegion using ISO 3166-2 format. An example is US-CA for the United States, California.
Alternative (Separate Country & Region): X-Forwarded-Country (2-letter ISO 3166-1 alpha-2 code, for example, US). If available, also include X-Forwarded-Region (1- to 3-letter region subdivision code, for example, CA). If you don’t provide the region code, region-level data may be missing in your reports.
Additional Geolocation Data: When available, additional geographic metadata including latitude, longitude, and city must be included in the X-Forwarded-Geolocation header. For example: latlong=32.9660663,-117.2619838;city=Mountain View.

Forward the true client IP address accurately. Use a standardized HTTP header, such as X-Forwarded-For. Your Content Delivery Network configuration must not alter, mask, or obfuscate this IP address.

Correct formatting is crucial. Ensure headers aren't stripped. Content Delivery Network rules must not modify headers for data accuracy.

Points to be considered

For users in the European Economic Area, Google Analytics measurement data goes directly to regional Google endpoints. This routing bypasses your Content Delivery Network path, ensuring GDPR compliance & representing expected behavior. This exception doesn't affect Google Ads conversion hits; they still route through your Google tag gateway for advertisers path.
Accurate geolocation data is vital for Consent Mode. It allows Google tags to apply region-specific consent defaults, respecting user privacy choices, especially for users in the European Economic Area.
Google tag gateway for advertisers processes only Google first-party cookies essential for measurement & functionality. Google tag gateway for advertisers drops any non-Google first-party cookies forwarded through it. This ensures data privacy & compliance.

Benefits of location setup

Implementing correct location header forwarding ensures:

Improved reporting accuracy: Get granular geographic insights in your Google Ads and Google Analytics accounts.
More effective campaign optimization: Base your campaigns on user location.
Enhanced compliance: Meet regional data privacy regulations & user consent preferences.

Vai tas bija noderīgs?

Kā varam to uzlabot?