Google Tag Gateway
This behavior allows you to deploy and deliver Google Tags from within your existing property, mitigating third-party tracking limitations enforced by modern browsers.
How it works
Use this behavior to configure Google Tag Gateway. Note that only one instance of the behavior is allowed in a particular rule. If there are multiple rules in the property, each with an instance of the behavior, the last rule that matches the incoming request is processed.
Tag Injection Guidance
If your website uses multiple tags or a tag management solution, we recommend managing tag injection directly within your existing platform rather than through Akamai.
When you inject more than one tag at the page level, only a single tag can take effect. To avoid unexpected behavior when using multiple tags, you should rely on your tag manager or application platform to control how and when tags are deployed.
We don’t recommend Akamai-based tag injection when using Consent Management Platform (CMP) - for example, OneTrust - alongside a tag manager. Injecting tags outside of your existing workflow may bypass or override your consent settings, which could impact your privacy and compliance controls. Managing tags within your tag manager ensures that your consent preferences are always respected.
As a best practice, the Enable Tag Setup option should remain disabled. This setting is not required for the existing Google customers using Google Tag Gateway and helps ensure seamless integration with your current tag management and consent frameworks.
If you have questions about the best configuration for your environment, contact Akamai support to help you determine the optimal setup.
Features and options
| Field | What it does |
|---|---|
| Enable | Enables the Google Tag Gateway behavior. |
| Google Tag ID | Specifies the unique Google Tag ID that was provided to you by Google. |
| Serving Path | Specifies the path that serves the Google Tag. It must consist of 6-10 alphanumeric characters and start with a slash ( / ), and must be a unique path which is not used elsewhere on your site. |
| Send True Client IP Header | Sends the True Client IP header to the Google origin. |
| Enable Script Injection | Injects the Google Tag script directly into the page. Enable this if your pages don't already include the Google Tag script. |
| Enable Setup Tag | Controls whether the injected tag should override any on-page configuration. Enable this if your pages don't already include the Google Tag script. |
Implementation
- Log into Control Center.
- Search for a property you want to add the Google Tag Gateway behavior to by entering its name into the search field or create a new property.
To get to know the stages of setting up your property, see Workflow overview.
- To add the Google Tag Gateway behavior to your property or include, see Behaviors.
The Google Tag Gateway behavior is incompatible with the Brotli Support, Construct Response, and EdgeWorkers behaviors.
- Activate on staging. Deploy your property version on the servers in the Akamai Edge Staging Network (ESN) so that you can test the configuration.
- Test on staging. Set up and run tests against the staging configuration. Once you confirm that your configuration works fine, you can perform regression and load testing, if needed, outside of Property Manager.
- Activate on production. Deploy your configuration version to the Akamai Production network to prepare to go live.
Products that use this behavior
You can create a custom rule and configure the Google Tag Gateway behavior inside a hostname match for the Ion product.
Updated 17 days ago