@odedta thanks for your topic!
A few questions:
1) I see you might be using the Analytics Tag implementation in Google Tag Manager to insert the Analytics tracking code?
If this is the case, then you can continue to use this tracking method for Analytics.
2) Currently, once you connect Analytics in Site Kit, the plugin would insert its snippet if it doesn’t detect the tracking code in the site’s HTML code already (it cannot detect the GTM Analytics tag at this time). While you should only use one method to connect to Analytics, it is odd that we cannot see it with the default settings.
Could you check under Site Kit > Settings > Analytics to confirm if Site Kit’s snippet displays as inserted or not?
Ultimately, you should use Site Kit’s snippet or the method with Tag Manager. Note that if you choose Tag Manager, ensure that Site Kit’s snippet is removed, and you can configure the Account, Property, and View manually from the settings to display your data in Site Kit’s dashboards.
Hello and thanks for the fast reply.
It seems like the code was not inserted which is a problem since if you look at the screenshot I attached here, everything is marked with a green check mark stating that everything is good and I do see analytics on the plugin Dashboard.
Only when you open Google Analytics accordion you realize it’s not inserted.
This should be fixed in the next release, please add some kind of notice for the user, I had absolutely no idea that Google Analytics is not collecting data, especially after I used the setup wizard and everything looks fine, green and without errors or notices.
Thanks
-
This reply was modified 6 years, 1 month ago by
Oded Talmon.
@odedta Thanks for your valuable feedback. The default option when setting up the Analytics module is for the snippet to be placed when no other tracking code is found. For cases whereby there is additional tracking code located users can choose to utilize that existing code.
As this is a very useful suggestion I’ve created a GitHub issue which you can keep track of here, which the team can discuss. Many thanks once again for the input, and I can keep you posted here also if this feature makes it to one of our releases.
Thank you very much for opening the issue on github!
