Hi @bulldogsnare,
Would it be possible to temporarily bypass any caching/optimization functionality on the website in question, so that we’re able to take a closer look at the behavior without those involved?
That’d help to narrow down the potential reasons a bit further.
Also, how are you currently implementing Analytics on this website? Through the fields in the Complianz Wizard, or with another tool?
Kind regards, Jarno
Hi, Im afraid I am not in control of any optimisation software, it’s looked after via a third-party. But, everything was working fine up till 17th October and the optimisation software was running alongside Complianz. GA4 tag is implemented via Elementor tools. Happy to share admin login if required.
Many thanks
Hi @bulldogsnare,
Please make sure not to offer or post any login credentials on these forums, as this is against the WordPress Forum Guidelines.
I think the culprit here is WP Meteor. I installed it on a test environment with a similar Complianz set-up, and after this plugin performs its’ optimizations, the Analytics script isn’t correctly loaded anymore after providing consent in the Cookie Banner.
You, or the third-party who manages the WP Meteor settings for you, can make the following adjustments in the WP Meteor settings. This should solve the issue.
Kind regards, Jarno
I have added excluded both and will see what happens. WP Meteor has been running alongside Complianz without issues prior to the 17th of this month so can’t understand why it would suddenly stop the tag from firing etc. Are you sure this is the culprit?
Hi @bulldogsnare,
Immediately when I activated WP Meteor on my test site; the same behavior as present on your website, started to occur on my end.
And now that you’ve made the change, I can see that the Google Analytics script on your site is loaded correctly after clicking the “Accept” button in the Cookie Banner, so yes, that does appear to have fixed it.
Kind regards, Jarno
But is there not a way to fire Google Analytics for every user unless they specifically deny it?
Hi @bulldogsnare,
Firing Analytics initially, before obtaining consent, would mean that you’re asking users to opt-out instead of explicitly opting in.
It is required to obtain consent for Statistics (such as Google Analytics) in the UK, therefore your visitors have to provide explicit consent before it can be loaded.
Disabling the Cookie Blocker at the end of the Wizard would stop the plugin from blocking anything. But that would, of course, mean that you’re no longer conforming to the above.
Kind regards, Jarno
