Feature Request: Native support for Google tag gateway on Optimizely-managed CDN (Configured Commerce Cloud)
Summary
We’re requesting support for Google tag gateway for advertisers on Optimizely-hosted Configured Commerce sites. Google tag gateway serves Google tags (GA4, Google Ads, Floodlight) from the site’s own first-party domain instead of googletagmanager.com, which improves measurement resilience against ad blockers, browser tracking restrictions and third-party cookie limitations.
Because the CDN and edge layer for Configured Commerce Cloud is managed by Optimizely, partners and customers can’t configure this themselves. Google’s one-click setup and manual setup both require control over CDN or load balancer routing, which isn’t exposed to us today.
Business problem
Our clients rely on GA4 and Google Ads for revenue attribution, campaign optimization and conversion tracking. With tags loaded from Google’s third-party domains, a meaningful share of sessions and conversions go unmeasured because of blockers and browser privacy controls. This leads to under-reported conversions, weaker bidding signals in Google Ads, and less reliable reporting for marketing and leadership. Competing platforms and self-hosted setups can enable Google tag gateway, which puts Optimizely-hosted customers at a measurement disadvantage.
Requested enhancement
We’d like Optimizely to provide one of the following, in order of preference:
A self-service setting in the Optimizely portal to enable Google tag gateway per site/domain, where the customer supplies the Google tag ID(s) and a measurement path.
A documented, supported process where customers raise a ticket and Optimizely configures the routing and header forwarding on their behalf.
At minimum, official guidance confirming whether this is supported, planned, or not possible, plus any recommended alternative (e.g. server-side GTM on a customer-managed subdomain).
Expected outcome
Google tags load from the customer’s first-party domain, measurement coverage improves, and the setup is supported across all environments (Sandbox, Staging, Production) without custom workarounds.
Ebrahim Manasawala
shared this idea