Google Analytics Issues

Hi @wayfarians,

Your current Complianz configuration indicates that you’re using anonymized statistics, so the Analytics script is fired by default (also without clicking “Accept” in the banner).

If the Analytics script were to be blocked before obtaining consent, that would indeed explain the drop i Analytics data. However, as that’s not the case on this site and Analytics is loaded immediately; it would seem unrelated to cookie acceptance rates.

Perhaps some optimization feature in a caching tool might be related? I.e. Delay JS Execution in a plugin like WP Rocket, whereby the Analytics scripts may only get loaded after a certain interaction on the page?

Kind regards, Jarno

Thanks for the reply Jarno,

If that were the case wouldn’t the issue have existed before Complianz was installed and activated?

I do have WP Rocket but have had no issues with the GA numbers in the past.

Hi @wayfarians,

That doesn’t necessarily have to be the case, the behavior may have changed now that you’re using Complianz.

While Analytics is loaded by default, as Statistics consent is also present by default in your case: it’s still activated by Complianz. Therefore if Complianz is affected by such an optimization it could still change the behavior.

The best way to figure out what might be related would be to disable plugins/optimizations individually, until the behavior is restored. That’ll tell you which one is most-likely to have been related.

Kind regards, Jarno

Thanks …. so should I disable WP Rocket and see if that makes a difference?

Or is there a setting in WP Rocket that can be applied to allow the script to run properly ?

Disabling it permanently won’t help my Core Web Vitals after all so I’m hoping there’s a solution where both can run.

There’s no chance this is a problem on the Google side ?

I haven’t made any changes to the analytics code since I installed Complianz (not sure if I should have).

• This reply was modified 10 months, 2 weeks ago by J&D.

Hi @wayfarians,

The intention is not to permanently disable WP Rocket, but to reduce the number of variables which are potentially related to the described behavior. Which greatly helps the troubleshooting process as you can narrow down the potential causes of the issue.

But I haven’t been able to spot any issues with regards to loading Analytics on your site, in the context of this plugin, thus far.

Kind regards, Jarno

Ok thanks for that.

Will disable WP Rocket and come back to you once I’ve seen what the analytics numbers look like.

Hi Jarno,

WP Rocket has been disabled for the past 5 days and our Google Analytics traffic has been back to where I would expect it to be for all 5 days.

As such, I think it’s fairly safe to say that’s where the issue is.

Can you provide any advice on how to setup WP Rocket to allow Complianz to work as intended while also not blocking Google Analytics?

Many thanks

John

Hi @wayfarians,

Probably there’s just a single feature in WP Rocket which causes that behavior.

I would re-enable WP Rocket after which the issue should return; and then disable individual features in that plugin, one-by-one, clearing cache after each one you disable; and checking whether disabling that specific feature resolved the issue.

Once it is resolved after disabling a specific optimization feature in WP Rocket, you’ll know that it was likely related to the behavior; and you can leave that one disabled while still being able to use the other functionalities of that plugin.

Kind regards, Jarno