Requests sent to /g/collect

Google Tag Manager Server Container
1

Stape with Custom Loaded enabled used to send requests to an obfuscated endpoint URL.

  1. Now, it sends them to /g/collect?v=2 making them susceptible to blocking.

  2. With the new option enabled (GA4 ad block bypass) it sends them to asdfgh?ad12345=xyz but you lose visibility into the request payload.

Is this (1) a bug?

2

this is expected, the obfuscated endpoint is no longer sufficient for bypass, therefore by default (1) we’ve reverted to the native pattern. And then with bypass enabled (2) it overcomes existing adblockers.

3

Hey

We are having same issue could you elaborate and point out what bypass is ?

4

Hey @quiloos39 ,
Can you please give more details of exactly what problems you see?

5

Maybe consider creating a browser extension which would decode the payload?

It’s impossible to debug with GA4 bypass enabled. :worried: