Timeline for "Time on site" value for a month in Google Analytics is different based on the number of months viewed
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2017 at 8:30 | comment | added | Stephen Ostermiller♦ | I thought that this might be due to data sampling. Google Analytics doesn't use all the data to show stats. It may base stats on a certain percentage of visitors. | |
| Jun 10, 2017 at 10:21 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 16, 2017 at 10:37 | comment | added | Sérgio Paulino | Thank you, @closetnoc! I think I am going to use this response of yours to put my case up to their SLA team and try to get a new solution for this. | |
| May 12, 2017 at 3:25 | comment | added | closetnoc | I used to be in the SLA game for a global Telecom. There are some things you have to consider. One is that you cannot control the Internet or the responsive nature if any request made. That is simply beyond your control. Instead, a sites response time can only be measured on the server itself - from when the request is received and then responded to. You need to measure your metrics that way only and write your SLA accordingly. Otherwise, expectation of response times to remain predictable across the net is wildly unrealistic. | |
| May 11, 2017 at 9:40 | history | edited | Stephen Ostermiller♦ | CC BY-SA 3.0 |
put problem statement into title, remove "thanks"
|
| May 11, 2017 at 8:29 | answer | added | L Martin | timeline score: 1 | |
| May 11, 2017 at 8:22 | review | First posts | |||
| May 11, 2017 at 9:40 | |||||
| May 11, 2017 at 8:18 | history | asked | Sérgio Paulino | CC BY-SA 3.0 |