Use case 01
Google Tag Gateway
Google tags load from the site’s own domain, so more of the hits that browsers drop still reach Google.
The situation
Ads and analytics tags were loading from a third-party domain. Browsers and blockers dropped a share of those hits before Google ever saw them, so the account was optimizing on a thinner set of conversions than the shop actually made.
What we implement
The Google tag is served from the site’s own domain through a first-party gateway. The same tags keep running in the browser. What changes is the request: it arrives as a first-party hit instead of a third-party one. This is a different setup from a server container.
The result
Measured conversions rose 10% after the gateway was live. The campaigns kept the same tags and the same site. More of the conversions the shop already had showed up in Google.