Plugin sets traffic as (direct) / (none) in Analytics
-
Hello GDPR,
Since installing your plugin, we have experienced a problem in our Analytics, as the plugin messes up the data in Google Analytics. The issue is, that as the plugin effectively blocks our Google Analytics script from loading before people has given their consent, it seems that Analytics can’t credit the traffic source correctly thereby setting the traffic source to (direct) / (none) which is incorrect.
This is especially an issue with our users coming from Google searches, as the search results do not include any UTM parameters as Google Ads does.
How do we avoid this?
Our GDPR setup can be seen here: https://drive.google.com/file/d/14YRydlA68IP40B6kIOoD9WMnvqBizh5J/view
We have setup the plugin to reload the site as people click the accept button by going to:
Customise buttons -> accept button -> “action” set to “open URL” -> Kept the URL field blank
By doing so, the plugin reloads the URL. By setting it to “close” we found, that the scripts would not fire until the user visiting another page on the site, which would give misleading landing page results in Analytics.
How has people solved this problem?
Cookiebot seems to have a function where the scripts will fire on the website as soon as people click on ‘accept’ (without reloading the page) which we assume would lead to correct results. Is there any way to do this with your plugin? We do not mind paying for the your plugin if it does the same.
Thanks in advance!
- The topic ‘Plugin sets traffic as (direct) / (none) in Analytics’ is closed to new replies.