Hi All,
I have an eVar that is set when a user sees product. If no product is available, it will show zero and if product is available, it will show the number of products as the value for the eVar. This eVar is set only on visiting the product page.
When pulling data from the Workspace UI, if I select a single day I will see one value (21,115 for Sep 23rd in the screenshot below) but if I select a date range and then breakdown by day, that day shows a larger total (now 23,734 for Sep 23rd).
How is Adobe making this calculation? I thought it would check for the count of distinct visitor ID's that showed zero for the eVar on Sep 23rd, but the way the number increases as the date range increases almost makes me think it counts any UV that visited on Sep 23rd and ALSO saw zero product at some point during my time range.
Solved! Go to Solution.
Views
Replies
Total Likes
Based on your reply to my comment, I'm going to say that this is what is happening:
What you're seeing is a characteristic of the "Unique Visitors" metric, which basically counts the number of people (ignoring cookie deletions, tracker blocking, etc).
Consider these 2 people: Harry and Sally.
Let's assume that both Harry and Sally had never visited your site before these visits.
When you run the report for 23 Sep 2020 only, AA gets the data for 23 Sep 2020 only. That means it includes:
Only Harry had zero products. So he gets counted under the "21,115" number.
But when you run the report for 13 Sep - 23 Sep 2020, AA gets the data for the entire date range of 13 Sep - 23 Sep 2020. That means it includes:
Harry had zero products. So he gets counted under the "23,734" number.
Although Sally had 2 products on 23 Sep 2020, she had zero products on 20 Sep 2020. She's the same person who had different experiences, one of which qualified for the "zero products" segment. So she too gets counted under the "23,734" number.
And that's why you get two different numbers for the seemingly same criteria. The interpretation lies in the combination of date range and metrics used in your report.
Views
Replies
Total Likes
1. What is the Expiry setting of that eVar?
2. How is the "Visitors who only saw zero shifts" segment defined?
Views
Replies
Total Likes
1) Expires after Hit
2) Defined as:
Include Hit # of shifts available [v8] = 0
AND
Exclude (Hit # of shifts available [v8] NOT Equal to 0 AND # of Shifts Available [v8] Exists)
Views
Replies
Total Likes
Based on your reply to my comment, I'm going to say that this is what is happening:
What you're seeing is a characteristic of the "Unique Visitors" metric, which basically counts the number of people (ignoring cookie deletions, tracker blocking, etc).
Consider these 2 people: Harry and Sally.
Let's assume that both Harry and Sally had never visited your site before these visits.
When you run the report for 23 Sep 2020 only, AA gets the data for 23 Sep 2020 only. That means it includes:
Only Harry had zero products. So he gets counted under the "21,115" number.
But when you run the report for 13 Sep - 23 Sep 2020, AA gets the data for the entire date range of 13 Sep - 23 Sep 2020. That means it includes:
Harry had zero products. So he gets counted under the "23,734" number.
Although Sally had 2 products on 23 Sep 2020, she had zero products on 20 Sep 2020. She's the same person who had different experiences, one of which qualified for the "zero products" segment. So she too gets counted under the "23,734" number.
And that's why you get two different numbers for the seemingly same criteria. The interpretation lies in the combination of date range and metrics used in your report.
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Likes
Replies