• Resolved somtam

    (@somtam)


    Hello guys and sorry to disturb again,
    but I started to collect an Analytics Missing Tracking Code error, with “No valid tracking code could be found for at least 530 pages in property xxx”.
    I think that it is probably due to the fact that Analytics doesn’t accept the privacy ??
    So I was wondering if you can fix this, analyzing the spider before to block it.
    thanks again for the amazing work you are doing!

    https://www.ads-software.com/plugins/ginger/

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

    (@manafactory)

    Somtam you are right, if your analytics code is not anonymized and with opt-in mode enabled ginger will disable GA code before cookie acceptance…
    We are thinking about that, this problem is also related with cache.
    With a cache system enabled (varnish, w3tc, super cache or others) and google analytics not anonymized is tecnically impossible to respond with a different output to a spider request.

    So a spider exception sould work only without caching.

    We will continue to investigate on it, in the meantime you can anonymize ga adding this code to your script:
    ga('set', 'anonymizeIp', true);

    This should fix it

    Thread Starter somtam

    (@somtam)

    I understand this is a completely mess for you and also this is a law difficult to enforce!

    For some customer I ananymized the IP, because they don’t need it, bor for others, especially those that have worldwide traffic, I think it could cause problems with the data. I mean, could happen that we are going to lose the geo traffic data right?

    An idea could be that you make a list of user agent, and then server side enable or disable features depends on who is making the request. It make sense right?

    Of course to solve the cache problem you have to make this check into an hook earlier than the one used from most of the cache plugin.

    Plugin Author manafactory

    (@manafactory)

    Somtam is not completely true, anonymized IP will not affect geo traffic. Analytics will hide last 3 number of IP, so you can still understand geographic position.

    The idea of filtering user agent could work only without cache.
    With server caching system (like Varnish) every user will have the same output html. So the solution must be client side

    But…
    the good news is that in the next week we will release a free analytics addon that will anonymize IP only for people that are not accepting cookies.
    It will work client side via javascript, and it should fix also the problem related with webmaster tool alert ??

    Thread Starter somtam

    (@somtam)

    that is a good news. Thanks for update!

    Plugin Author manafactory

    (@manafactory)

    Hi somtam,
    try to upgrade and ginger to 2.0 version

    Now you can activate google analytics addon, and manage analytics code directly inside ginger.

    It will anonimyze or not your analytics based on user cookie preference

    And it will fix report problem

    Bye

    Thread Starter somtam

    (@somtam)

    Thanks again to improve this plugin!
    One question. With this addon do I have to insert the analytics code or ID in your addon?
    Because in this way it would be no possibile to use plugin like WooCommerce Analytics, that tracks all the ecommerce transaction.
    thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Problems with Analytics report’ is closed to new replies.