Since last week we are experiencing problems with Google Analytics / Site Kit. Out of sudden, our traffic dropped. We are hosting with SiteGround and in their analytics we still have lots of traffic. What’s going on here?
Hello @eshalabs, thanks for opening a support topic with us. As this is a recent drop off in Analytics and I can see your are based in the European Economic Area (EEA), this could be due to the fact that you are using Site Kit and Google Ads is connected or an Ads conversion ID is placed by Google Analytics. Could you please first confirm if this is accurate?
If the above is accurate then you will need to update to the latest version of Site Kit and enable consent mode for your website.
If this isn’t the case then I am also happy to check your setup if you could please share your Site Health information. You can use this form to share privately if preferred.
We are not using Ads with our Site Kit, only Analytics. We have however turned on the consent mode. Should we turn it off? We don’t use ads on our website.
@eshalabs Thanks for confirming that you are not using Ads on your site. If ads are not detected on your site then you will not be prompted to use consent mode. If you are not using ads then you can switch consent mode off. If you are, you should see a ‘Recommended‘ label next to the consent mode setting.
As this doesn’t look to be consent mode related, could you please share your Site Health information. You can use this form to share privately if preferred.
@eshalabs Thanks for confirming and for sharing the information requested. I can’t see anything obvious that stands out here. You could try following our troubleshooting steps here to see if you can see any plugin/theme conflict.
Could I check with you if the data you see in Site Kit matches the data in your Analytics account? If yes, you may want to also ask a question at the Analytics Help Center with regards to your Analytics data as we are limited to the support we can offer on the analytics side of things.
Let me know if you have any questions on the information above.
We have already contacted Google and received this a few minutes ago: Post checking the issue with the dedicated team, I would like to inform you that we have submitted the form but found that the tags are not triggering on the website. Additionally, the debug view is not enabled.
I would suggest you get in touch with the web developer and recheck the implementation of the tags on the website. Once the issues with the tags are fixed, wait for 24 to 48 hours so that data should start updating over the interface.
We have never had tags on our website and I am not sure about the debug view. Everything was working fine until a few days ago…
Regarding your question: Yes, our Analytics account also shows a drop in traffic, but Search Console is still up and running.
@eshalabs When checking your site on https://tagassistant.google.com/ I can see an Analytics tag firing on your site. When checking your source code it does look like your source code is being manipulated. This is likely due to a caching/maintenance plugin.
As mentioned above, you could try following our troubleshooting steps here which may help to find a conflict that could be responsible for blocking traffic being gathered. You could also check your Complianz plugin settings to ensure there isn’t a setting being used that could block Analytics from being recorded.
From the Site Kit side of things, I can’t see any issues. The Analytics code is being placed and I can see the Analytics page hit when checking from the tag assistant as mentioned above. Let me know how your checks go and if there are any further questions you have.
@eshalabs Just to let you know that we identified an issue where if consent mode was turned on, it was being applied for all users regardless of location. We’ve now addressed this with the latest version of Site Kit, version 1.123.1. When enabled, this will only default to consent required specifically for EEA countries and the United Kingdom.
Thanks for reporting this previously, which helped us to identify this.
.
