• Resolved bduperrin

    (@bduperrin)


    I have a issue that suddently appeared while I changed nothing in my configuration.

    When I click on “accept all” I get an error in google the tag assistant extension saying net::ERR_BLOCKED_BY_CLIENT

    But when I click on “refuse all” which was the former “functional only” I renamed in the template everything seems to be ok.

    I also notice that the configuration agent says I have google tag manager installed and I should track stats with GTM while I’ve never used GTM, always GA. I think (but I’m not sure) that the behavior changed at the same moment I noticed this change with the agent.

    Further more (but maybe it would deserve another ticket) I have some questions regarding the new french regulation :
    1°) Is the template I use OK or should the “Accept all” and “Refuse All” buttons be exactly the same ?

    2°) What is the new expected behavior ? Should GA be deactived when people click on refuse all, which means I won’t get any trafic data anymore ?

    3°) What happens when people click on nothing ? GA deactivated by default ?

    4°) Last but not least, do I have to change any setting by myself to comply with the french regulation ?

    PS : I’m using Exact Metrics to manage the GA code and everything has been working perfectly for more than one year until the issue I’m reporting appeared.

    Thanks for your help and advice.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Aert

    (@aahulsebos)

    Hi @bduperrin,

    Let’s start with “ERR_BLOCKED_BY_CLIENT”,

    this is probably due to a browser extension, the “Client” is your browser in this case.

    Could this be the case?

    regards Aert

    Thread Starter bduperrin

    (@bduperrin)

    You were right…the error had to do with gosthery and it’s fixed now.

    Seems to be be working now… but needs confirmation.

    But still very few sessions visible in GA + the fact the plugin believes I have GTM installed while it’s not the case.

    Plugin Author Aert

    (@aahulsebos)

    Hi @bduperrin,

    This could be if the implementation has a googletagmanager.com URL, which is possible.

    This is most likely a false positive, we will tighten the regex so we can skip these implementations.

    The code is added by another plugin and I can see no interference by Complianz.

    regards Aert

    Thread Starter bduperrin

    (@bduperrin)

    I have two other blogs with exactly the same setup and everything works fine (and used to on this one) and I really struggle at finding what is wrong.

    The implementation is through exact metrics and I have no GTM account set up.

    Plugin Contributor Jarno Vos

    (@jarnovos)

    Hello @bduperrin
    In the coming days, we will have a closer look at the integration with ExactMetrics.

    For now, under Complianz > Wizard > Cookies > Statistics, you can set the option “Yes, anonymous”. That should allow you to receive the statistics as usual.

    Kind regards,
    Jarno

    Thread Starter bduperrin

    (@bduperrin)

    h @jarnovos

    Thanks a lot.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Plugin Behavior changed’ is closed to new replies.