Using CDNs for Server-Side Tracking

1

Hello,

I have a few questions regarding the use of CDNs, and I hope someone can help clarify them for me.

I am familiar with the Cloudflare and Stape documentation:

However, I need additional guidance on specific scenarios before moving forward.

Some of my clients:

  • Don’t use a CDN at all.
  • Don’t use Cloudflare specifically. Instead, they use a local CDN provider, and their IT teams are unsure how to proceed with the Cloudflare documentation.

Here are my questions:

  1. How can I proceed with using a custom CDN in this scenario? For example, is it feasible to set up and use a custom CDN exclusively for server-side purposes?
  2. Can I purchase a Cloudflare CDN for my client and use it solely for server-side purposes? Would this approach make sense if the client:
  • Already has a different CDN but cannot implement the required steps?
  • Does not have a CDN and would only use it for server-side tracking?
  1. What potential impacts might arise from implementing a separate CDN for server-side tracking? Specifically, I’d like to understand how this could affect existing configurations (if any) or overall performance.

I’m a bit unsure how to navigate these scenarios and would greatly appreciate any guidance or insights.

Thank you in advance!

2

Hello again, is there any clarification needed, or would someone like to offer a suggestion?

Thanks!

3

Hey @DigitTracking,

It depends on what purpose you want to use the CDN for.
If it’s just to speed up loading JS files - then you can use Stape CDN or your own CDN which will work only for sGTM but not for the whole site.

If using CDN you want to bypass ITP restrictions (cookie lifetime on Safari) - then it is mandatory that both site and sGTM container use the same CDN. This way IP addresses of the site and sGTM subdomain will not differ.

In general, there is an article that describes all options for bypassing latest ITP restrictions related to cookies: Safari ITP update limits cookies to 7 days - Stape.

How can I proceed with using a custom CDN in this scenario?

If it’s not CF, I think the easiest option is to ask your CDN support to help you configure the same as described for CF, but using their tools.

For example, is it feasible to set up and use a custom CDN exclusively for server-side purposes?

I don’t see the point, you can just use Stape CDN if you just want to speed up container loading.

Can I purchase a Cloudflare CDN for my client and use it solely for server-side purposes?

Same as above - it makes no sense if the site itself is not proxied through Cloudflare.

What potential impacts might arise from implementing a separate CDN for server-side tracking? Specifically, I’d like to understand how this could affect existing configurations (if any) or overall performance.

Implementing a CDN just for the container (and you don’t have a CDN used on your site) - will have no effect on your tracking results at all, only potentially on the load speed of gtm.js and gtag.js. That is likely to improve page load speed if your site users are in very different locations around the world.

4

Hi Alex,

Apologies for not clarifying earlier. My primary concern is bypassing Safari’s ITP restrictions.

The issue I’m facing is that I haven’t been able to get proper support from local CDN providers for configuration. That’s why I was exploring the possibility of offering my clients a server-side-only CDN solution, if it’s reasonably feasible and understanding its effects.

Unfortunately, as you mentioned, Stape CDN cannot bypass the Safari cookie limitations, which is why this step is mandatory on my end.

Thank you for your reply, and I really appreciate any further insights!

1 Like