GA Code is not added via CookieYes – how do you recognize it?
-
Hey,
I am trying to better understand – I am coming from solutions (e.g. Borlabs Cookie, Real Cookie Banner) that require to add the GA4 ID or tracking script directly via the Cookie plugin settings. That means the cookie plugin is in charge to tell if the script should be loaded or be blocked.
I think, If I was adding the GA4 script directly via functions.php or with some other plugin e.g. Site Kit, SEOPress or any other plugin that can do that, then those “traditional” cookie banner & consent management solutions would not be able to block it. GA would probably be loaded no matter whether the user has given consent.
It seems CookieYes works quite differently here. It’s blocking (or not loading) the GA tracking script no matter how it is added. At least I can observe that when using Site Kit. When GA is added via the Site Kit plugin, CookieYes seems to be able to understand that. Same goes for SEOPress, if I add the GA via SEOPress, CookieYes seems to understand this and is able to block when consent is not given.
In general, do I have to check for compatibility between the approach of how the GA code is added and CookieYes, or are you always able to spot how it’s added and block the GA script when consent is not given?
Also, is my overall observation and understanding correct?
Traditional cookie plugins like Borlabs / Real Cookie Banner → GA code and other tracking codes must be added via the plugin otherwise it will not be able to block the script when consent is not given
CookieYes → does not matter how the GA code or other tracking code is added, however, as there are endless approaches, compatibility must be tested
Thanks in advance
Markus
- The topic ‘GA Code is not added via CookieYes – how do you recognize it?’ is closed to new replies.