New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome's "Data Saver" mode prevents tracking of many visitors using Chrome browser #7733
Comments
Hi @ericimprint Thanks for the report. In Chrome documentation they explain how to disable the feature, maybe this is what we could do:
|
I haven't checked where this should be done, but I guess maybe chrome won't load |
I added |
If you open Chrome > Developer tools, do you see the piwik.js being loaded in your browser? |
Piwik.js is being loaded both when the tracking is working and when it is not. Watching the network waterfall I can see it come up both when data saver is on and when it is off. |
FYI: In the tracker debug log I get:
Here's some more info from
Interesting could be eg
|
Created an issue for the device-detector library: matomo-org/device-detector#5363 I presume we should keep this one open? |
@tsteur yes, until the issue in device-detector will be fixed Good find! |
As mentioned in the device detector issue: I assume the problem is within Piwik. Those IPs are excluded by |
Ok, maybe the solution is to consider Google IP addresses requests as bots only when the |
some users sometimes report that Piwik track less data than GA, it could be that this bug fix will improve this situation |
Awesome. Thanks guys. How can I test this before the release? |
@ericimprint you can use Piwik 2.15.0-b1 which includes this fix and few others: http://piwik.org/faq/how-to-update/faq_159/ |
Yesterday before updating to the beta our sites visits were about 77% of GA. Today they are running at 91% of GA. Thanks for the fix. |
Hi @ericimprint that's really awesome to hear. It is a big win for Piwik product and the community at large. Fixing this bug means Piwik became much better at tracking data 🚀 Maybe, we could dig down further and try to explain those 9% difference with GA. What I suggest first would be to look in Piwik and GA and compare for Browser versions report, whether some rows are showing very different "Pageviews" count. Maybe piwik.js has some bug when tracking some particular browser versions? if we find that some browser versions have much less traffic on Piwik than GA, we will have something to investigate further 👍 |
@ericimprint @mattab The difference is indeed big! Some of my numbers: Past Sunday, without the beta installed: Yesterday, with the beta installed: Especially the pageviews are incredibly close! Good job. Visitors are still a bit off, but not by much. But this can be seen throughout the day, the real time visit counter is almost always a bit lower then GA's. Without the beta this could run up to a difference of 30 visitors, now with the beta it's between 0-10. |
@mattab @ericimprint Although my visitor and pageview counts are much, much closer since installing the beta, like I stated in the comment above, my real-time visit counter started to be very incorrect again. For example, right now: Is this normal behaviour for Piwik? Or should I open a new Issue for this. |
I have found that to be normal as they define live visitors differently. The main thing you want to look at is total daily pageviews matching. Matt feel free to correct me if I am wrong. |
I have found that to be normal as they define live visitors differently.
Piwik defines live visitor as "seen in last 3 minutes". (as defined in
config:
https://github.com/piwik/piwik/blob/8461/config/global.ini.php#L415-419)
Do you know how GA defines a "live visitor"? Maybe we could change our
definition of live visitor to match GA's.
|
I haven't found what they define as live exactly, but it's quite impressive to be honest. GA has a Realtime page, where you can see the counter and a table with all the pages that number of visitors is on at the moment. (That would be great to have in Piwik too by the way. The current real-time logbook is to cluttered to get a fast overview) I did some tests with it and it's quite fast. If I open a tab and navigate to a random page, it pops up in the table (and the counter) within seconds. Same goes for closing the tab, it disappears within seconds. So I don't know how, but they can define live very live. Did the same tests with Piwik, but it's not that fluid. |
Visitors using chrome's Data Saver mode are not tracked. I can see them in Google Analytics, but not in Piwik.
The text was updated successfully, but these errors were encountered: