NOTE: from your docs:
Step 3:Ensure the order of the scripts
Ensure that the scripts are loaded in the following order for proper functionality:
- Custom Consent Mode script
- gtag / GTM script
- CookieYes script
Maintaining this sequence is essential for the correct operation of the functionality.
Previously, CookieYes had us adding the Consent Mode script manually. I was able to add it before adding Google Analytics gtag script. That’s how I got the sequence in the required order. Then the new version was released, which broke it. It’s no longer possible for me as far as I can determine (reading all of the docs).
I don’t control when #1 is executed. Now, with the latest released, I only add #2.
NOTE: I’m not using Google Tag Manager. I’m using classic Google Analytics gtag.
If I add the gtag script to head, using standard WordPress API, I cannot control the sequence described by your docs. There is an implicit requirement to use Google Tag Manager with CookieYes. I don’t see how to integrate it otherwise.
That requirement shows up again when the only way to verify the integration is to debug with Google Tag Manager. For the average person, this is all much. Still, why isn’t the requirement of using Google Tag Manger made more clear? Then the docs are incomplete to setup a new Google Tag Manager.
Is it even possible for CookieYes to work with out Google Tag Manager. If so, how?
Even if I go thru all the effort to install Google Tag Manager, which I don’t need because I’m just using basic Google Anlytics, the real problem is how CookieYes is significantly impacting performace. That’s the real problem. This then impacts Core Vitals, and lowers SEO.
-
This reply was modified 7 months, 3 weeks ago by
Jim Reekes.