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

Visitor Totals for a Segment Not Summed Correctly with a Date Range of a Month #16545

Closed
garrick-abine opened this issue Oct 7, 2020 · 1 comment
Closed

Visitor Totals for a Segment Not Summed Correctly with a Date Range of a Month #16545

garrick-abine opened this issue Oct 7, 2020 · 1 comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@garrick-abine
Copy link

Hello,

We seem to be having an issue similar to #16320 where aggregated totals for a segment don't calculate correctly. Our install is on-premise running 3.14.1. We have a segment where all visits for the channel for the month (Sep 2020) totaled 1,336 visits. This is the the same total regardless of the period selected (month or date range). However, selecting the following date ranges for the same segment yields visitor totals of:

Date Range Visitor Totals
1 Sep - 30 Sep 1,336
1 Sep - 26 Sep 4,467
1 Sep - 27 Sep 711
8 Sep - 30 Sep 4,005

We tried invalidating the reports for the segments (for the month of Sep) and re-running the archive progress to recreate them. However, the error with the totals remains. This issue does not appear for the previous month (Aug 2020). Is there something else that we can investigate or do to correct this? Thanks!
@tsteur tsteur mentioned this issue Oct 7, 2020
Closed
@tsteur
Copy link
Member

tsteur commented Oct 7, 2020

Thanks for creating the issue @garrick-abine I've followed up in #16320 (comment) and will close the issue as it looks like a duplicate of that issue and it be great to have all the information in one issue. I hope you don't mind :)

@tsteur tsteur closed this as completed Oct 7, 2020
@tsteur tsteur added the duplicate For issues that already existed in our issue tracker and were reported previously. label Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsteur @garrick-abine