Implementation options

There is no single implementation pattern that fits every Google Tag Gateway (GTG) setup. The right choice depends on your current setup and your ability to make changes to the websites source to control script load order.

Proxy for requests

Content Delivery Network (CDN)

The most common approach is to use a content delivery network like Cloudflare, Fastly, Akamai, etc. to setup Google Tag Gateway.

Some of them offer a one-click automated setup. When using this, be aware that it might introduce issues with the script loading order resulting in a "late" consent signal - see our troubleshooting guide for more more information.

Alternative methods

Google Tag Gateway can also be setup directly using a load balancer, web server or using a Content Management System that support Google Tag Gateway (e.g. Webflow).

Follow the official documentation from Google to get started.

Google Consent Mode

When using GTG-enabled tags it's recommended to adopt Advanced Consent Mode (U+C) and configure Data Transmission Controls and Global Consent Defaults for your Google Tag according to your needs.

Related information