Skip to content
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

Jump to bottom

testing piwik regarding correct statistics for visits with different: browser, OS, protocols... #9608

Closed
hpvd opened this issue Jan 21, 2016 · 4 comments
Closed

testing piwik regarding correct statistics for visits with different: browser, OS, protocols... #9608

hpvd opened this issue Jan 21, 2016 · 4 comments
Labels
answered For when a question was asked and we referred to forum or answered it.
Milestone
2.16.1

Comments

@hpvd
Copy link

hpvd commented Jan 21, 2016

general approach for testing piwik regarding correct statistics for vists using

  • different browser
  • different OS
  • different protocols (http / https)
  • and maybe if nessary also different browser versions

=> comparing for same magnitude of

  • avarage time on page
  • average number of each type of action (pageview, event, download etc)

usecase identified in #9607

=>
- what more to test?
- how could this be done in an efficient way?
for good statitstics one should use a platform with enough visitors like http://demo.piwik.org
@hpvd hpvd mentioned this issue Jan 21, 2016
Closed
@tsteur
Copy link
Member

tsteur commented Jan 21, 2016

What I had in mind for this would be #7066 (comment)

@hpvd
Copy link
Author

hpvd commented Jan 25, 2016

The question to answer:
how does this look for different browsers,
OS,
etc?
Is it near equal?
Or are ther large differnts not only in absolute values but in trends?

2016-01-25_16h58_401

@tsteur
Copy link
Member

tsteur commented Jan 26, 2016

I had a quick look using segment browserCode== with different values FF, IE, CH, SF, OP and it looked good. Some browsers have to many visits to be 100% sure about it. Note: I didn't each different browser versions.

@mattab
Copy link
Member

mattab commented Mar 31, 2016

Closing as we couldn't identify a particular problem. To detect "Tracking issues" in different browsers, we have this idea: #9874

@mattab mattab closed this as completed Mar 31, 2016
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Mar 31, 2016
@mattab mattab added this to the 2.16.1 milestone Mar 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Milestone
2.16.1
Development

No branches or pull requests
3 participants
@tsteur @mattab @hpvd