Google Tag Gateway + Stape Custom Loader: can/should they be used toge

Custom Loader
1

Hi,
I have a question about a possible overlap between Google Tag Gateway (with Cloudflare) and Stape Custom Loader.

As a general rule in our agency, when we create a new GTM setup we also enable Google Tag Gateway with Cloudflare in the Google Tag Manager admin, to proxy GA4 through the site’s domain.

Now that we are implementing Stape server-side + Custom Loader, I’m not sure if enabling Google Tag Gateway on the same project/domain is technically compatible or potentially conflicting (since both Custom Loader and Gateway want to “own” the proxying of Google tags through Cloudflare / a first-party domain).

My question is:
For projects where we use Stape sGTM + Custom Loader + first-party tagging domain,

  • should we avoid enabling Google Tag Gateway for that domain/container?
  • Is there any known conflict or double-proxy issue if both are active?

what is the recommended best practice?

  • a) Use only Stape Custom Loader + tagging server / Own CDN and do NOT use Google Tag Gateway
  • b) Or is there a scenario where using both (Gateway + Custom Loader) makes sense and is officially supported?

I’d like to align our internal standards and avoid misconfigurations, so any clarification or architecture recommendation from your side would be very helpful.
Thanks in advance!

1 Like
2

Hi,

When using the sGTM container together with Custom Loader and a first-party domain, you do not need to enable GTG, as these approaches perform similar functions. Using them simultaneously is not recommended, as this can cause conflicts in tracking.

It all depends on your needs, but the recommended practice is to choose one of the approaches: either sGTM + Custom Loader + Own CDN, or Google Tag Gateway + GTM. Both options implement server-side tracking, but have different advantages.

The first approach provides greater flexibility at the tagging level. It allows you to enrich, modify, and route events on the server side via server_container_url, which is especially useful for complex and custom tracking scenarios.

The second approach works at the network level: it captures requests to Google domains and proxies them through Cloudflare. This is an easier solution to set up, but with less flexibility compared to full-fledged sGTM.

3

That’s what I thought,
thank you for clarifying and giving me your time :green_heart:
I have a better understanding of the whole thing.

1 Like