Filtering Unique Visitors based on eVar value across different time ranges | Community
Skip to main content
A
austi003
September 24, 2020
Solved

Filtering Unique Visitors based on eVar value across different time ranges

  • September 24, 2020
  • 4 replies
  • 1580 views

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.

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by yuhuisg

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.

  • Harry visited your site on 23 Sep 2020 and saw zero products.
  • Sally visited your site on 20 Sep 2020 and saw zero products. But she also visited on 23 Sep 2020 and saw 2 products.

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:

  • Harry's visit on 23 Sep 2020 with zero products.
  • Sally's visit on 23 Sep 2002 with 2 products.

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's visit on 23 Sep 2020 with zero products.
  • Sally's visit on 20 Sep 2020 with zero products.
  • Sally's visit on 23 Sep 2002 with 2 products.

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.

4 replies

yuhuisg
Community Advisor
yuhuisgCommunity Advisor
Community Advisor
September 25, 2020

1. What is the Expiry setting of that eVar?

2. How is the "Visitors who only saw zero shifts" segment defined?

A
austi003Author
September 25, 2020

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)

yuhuisg
Community Advisor
yuhuisgCommunity AdvisorAccepted solution
Community Advisor
September 25, 2020

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.

  • Harry visited your site on 23 Sep 2020 and saw zero products.
  • Sally visited your site on 20 Sep 2020 and saw zero products. But she also visited on 23 Sep 2020 and saw 2 products.

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:

  • Harry's visit on 23 Sep 2020 with zero products.
  • Sally's visit on 23 Sep 2002 with 2 products.

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's visit on 23 Sep 2020 with zero products.
  • Sally's visit on 20 Sep 2020 with zero products.
  • Sally's visit on 23 Sep 2002 with 2 products.

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.

A
austi003Author
September 25, 2020
That was what I was wondering, just not the way I would expect it to work. Put another way, AA is basically saying give me all of the Unique User ID's that qualify, and then count them for each day they visited even if that day wasn't the zero product day. That is the only explanation I could come up with as to how that number grows, because a user did not see zero shifts that day but did visit that day and saw zero shifts on a prior day included in my date range.
jantzen_b
Adobe Employee
jantzen_bAdobe Employee
Adobe Employee
February 3, 2021
Do any of the answers below answer your initial question? If so, can you select one of them as the correct answer? If none of the answers already provided answer your question, can you provide additional information to better help the community solve your question?
Terms & ConditionsAccessibility statement

Loading footer...