-
Posts
-
Hello together,
I am kind of confused of how to implement proper and GDPR compliant Google Analytics tracking within Enfold.
On the one hand it is possible to just enter your tracking ID (e. g. UA-XXXXXXXXX-X) into the Google Analytics Tracking Code box but on some other tickets I have read that it is also possible to enter the complete gtag.js snippet into the same box.
Additionally, the anonimyzeIP snippet needs to be implemented as well.
Therefore, some questions occur to me:1. How do I properly enter the gtag.js snippet and the anonymizeIP snippet into the Google Analytics Tracking Code box, so both of them work?
2. Does the shortcode [av_privacy_google_tracking] also work on mobile phones?
3. How does the shortcode [av_privacy_google_tracking] work (e. g. does it set a cookie?)?
4. How can the text of [av_privacy_google_tracking] be changed?Best regards,
MarcHey Marc,
Thank you for contacting us and sorry for the delay in my reply.
If you are looking for an easy way to implement Google analytics and make it GDPR compliant please use one fo the plugins listed here.
Best regards,
VinayI would rather want to use the implemented function of the Enfold theme.
Could you please answer the questions of the initial posting?
Hi,
1.) You can refer to the documentation to enable anonymization.
// https://developers.google.com/analytics/devguides/collection/analyticsjs/ip-anonymization
2-4.) That shortcode creates a toggler that allow users to disable or enable the google analytics tracker. It creates a cookie called “aviaPrivacyGoogleTrackingDisabled”, which sets a window property that disables the trackers as described in the following documentation.
// https://developers.google.com/analytics/devguides/collection/analyticsjs/user-opt-out
You can wrap the text inside the shortcode if you want to change the placeholder.
[av_privacy_google_tracking]Disable GA[/av_privacy_google_tracking]Best regards,
IsmaelOk, this resolves some of my questions.
I noticed though, that your recommended links all refer to the analytics.js, even though Google has introduced gtag.js in the meantime.
When I am using Google Analytics nowadays, only gtag.js is being used and there are some differences in those libraries.
I would like to ensure that there are no incompatibilites when your theme is still using code elements from analytics.js and I am using the tracking code for gtag.js.Could you clarify with the colleague responsible for Google Analytics at Kriesi to what extent this has been taken into account in the integration of the code (e.g. opt-out cookie etc.) as the above mentioned link clearly states differences?
Hi,
Thanks for the update. Glad that we’re able to clarify some things out.
And regarding your other question, it doesn’t really matter which snippet you’re using. The theme just renders the snippet inside the head tag, nothing else. Either of the library should work. The anonymization and opt out implementation is the same for both libraries if that is what you’re asking.
analytics: https://developers.google.com/analytics/devguides/collection/gtagjs/user-opt-out
gtag: https://developers.google.com/analytics/devguides/collection/analyticsjs/user-opt-outBest regards,
IsmaelThank you for the reply, which definitely answers my question to full extent.
The ticket can therefore be closed now.
- The topic ‘Implementation of GDPR compliant Google Analytics tracking’ is closed to new replies.