It has nothing to do with using a CDN. In one case you have the ‘GA4 bypass’ option active and in the other case you do not. You can activate this option and use it in custom loader power-up:
In all cases I’m using WP plugin to load GTM container where the instructions remain the same whether I check this or not.
I noticed with another client that the CDN really isn’t the case. One of their website uses Stape CDN, the other three don’t. But requests with collect?v2 url appear in two sites that don’t have CDN, and on the other that also doesn’t have CDN, they appear with a custom loader string.
So the behavior is very inconsistent, and I can’t figure out where’s the difference.
The settings are exactly the same, except for CDN. GTM server-side WP plugin > copied the input fields, and that’s it. The container is the same, and tags are the same (only IDs are dynamically changed based on hostname).
Plugins are up to date on all websites, so there’s no difference in versions either.
Unless sometimes Server-Side GTM plugin generates a snippet to bypass ad blockers and sometimes it doesn’t based on something else, that I’m unaware of.
CDN only affects how your container is loaded, it has no effect on other GTM features or any tags/functions.
The ‘GA4 bypass’ option is simply toggled on or off, it really doesn’t affect the custom loader or its settings, nor does it require any changes to the Stape plugin.
I have checked the sites you have listed:
gumiranepodlage.si here you are not using CDN and I see that bypass is working
Ok, now I’m even more confused. I didn’t change anything, and when I recorded the video you can clearly see the requests url on gumiranepodlage.si weren’t containing the custom loader. Now I have checked as well, and it seems like it works. I don’t know what happend in between.
On some other websites I had similar issues, and then when I changed to Stape CDN it started working, that’s why I assumed this is related.
Maybe it was a plugin version, although I think we’ve updated them on all websites. I don’t know anymore.
Note that bypass is not activated instantly, sometimes you need to wait 5-10 minutes for it to start working. So maybe it has to do with the fact that you tested it immediately, maybe that was the problem.
I did the setup for this client in november. I know it worked then, but I’ve been seeing ?collect requests url for a few weeks, so that’s why it didn’t make any sense to me.
Anyway, it’s working now, but I have no explanation to why this happend.