• Resolved aoedigi

    (@aoedigi)


    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!

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author WebToffee

    (@webtoffee)

    Hi @aoedigi,

    Please update the plugin to latest version(v1.8.9). Then add below code to your theme’s functions.php
    add_filter('wt_cli_enable_js_blocking','__return_true');

    This will enable the functionality to load the script upon accept without a page reload and you can then disable the auto reload after accept option.

    Let me know how it goes.

    Thread Starter aoedigi

    (@aoedigi)

    Hey Webtoffee,

    Thank you for your swift response.

    I have inserted the code, and it seems to work fine better, as the scripts are being loaded without a page reload.

    We do need to collect some data in Analytics before we can conclude whether this solves the tracking issue. We hope so ??

    We therefore hope that you will leave our ticket open for 24-48 hours until we have gathered sufficient data.

    Thanks in advance.

    Thread Starter aoedigi

    (@aoedigi)

    Hello WebTofee,

    We are experiencing issues with the most recent update of your plugin in combination with the added code on our Kinsta hosted website.

    I have implemented the code into the functions.php and updated the plugin on other websites, where it seems to work smoothly. However, we are experiencing issues on our Kinsta hosted website.

    I have been in contact with the Kinsta customer service, who encouraged me to ask you the following questions in order to overcome the problems:

    1)

    Is there’s anything that need to be bypassed/skipped from our caching besides the following cookies since the recent update and added code:
    – viewed_cookie_policy
    – cookielawinfo-checkbox-necessary/cookielawinfo-checkbox-non-necessary?

    We have already bypassed those cookies from their caching, where it has worked flawlessly until recent update + addition of code

    2)

    The following code were to be added in the functions.php

    add_filter('wt_cli_enable_js_blocking','__return_true');

    Does the code need to be added to both the parent theme and child theme? If not, were is the code to be added?

    Thanks in advance.

    Plugin Author WebToffee

    (@webtoffee)

    HI @aoedigi,

    1) In this version of the plugin, there is one more cookie set by the plugin for cache compatibility implementation. You may please whitelist that as well.
    CookieLawInfoConsent

    2) You only need to add the code in the child theme.

    Thread Starter aoedigi

    (@aoedigi)

    Hello Webtoffee,

    Thanks for the swift response.

    We will attempt to do so and get back to you.

    Thread Starter aoedigi

    (@aoedigi)

    We are still having difficulties on the following website:

    https://www.natures-help.eu

    The website is hosted with Kinsta and is using their Cache tool. As stated before we have whitelisted two cookies and have now – after you previous reply – added another, so that the following cookies now are whitelisted:

    – viewed_cookie_policy
    – cookielawinfo-checkbox-necessary/cookielawinfo-checkbox-non-necessary
    – CookieLawInfoConsent

    Are you familiar with any issues regarding your plugin and/or Kinsta?

    Adding the provided code to the functions.php makes no difference.

    Plugin Author WebToffee

    (@webtoffee)

    Hi @aoedigi,

    – cookielawinfo-checkbox-necessary/cookielawinfo-checkbox-non-necessary

    If you have whitelisted this as single cookie, then it might not work. Try adding it as 2 separate cookies which makes a total of 4 cookies to whitelist.

    viewed_cookie_policy
    cookielawinfo-checkbox-necessary
    cookielawinfo-checkbox-non-necessary
    CookieLawInfoConsent

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Plugin sets traffic as (direct) / (none) in Analytics’ is closed to new replies.