Discrepancy list and evar count in adobe analytics | Community
Skip to main content
V
Adobe Employee
VidhyaAk1Adobe Employee
Adobe Employee
May 20, 2024
Question

Discrepancy list and evar count in adobe analytics

  • May 20, 2024
  • 3 replies
  • 1561 views

Hi All,

On article clicked we are storing the card names in evar38 and list2 and having event72 to count the click

When we pulled the report for evar80 with event72  and ist2 with event72.

We can see the difference in event72 count ? is it expected ? why there is different in count although its part of same adobe request .

Network call

 



Adobe analytics report

evar



list

 

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

3 replies

pradnya_balvir
Community Advisor
pradnya_balvirCommunity Advisor
Community Advisor
May 20, 2024

List variables are custom variables, they work similarly to eVars, except they can contain multiple values in the same hit.

 

You can refer below document link: (go through Video)

https://experienceleague.adobe.com/en/docs/analytics-learn/tutorials/administration/manage-report-suites/configuring-list-variables

Josh Stephens
Community Advisor
Josh StephensCommunity Advisor
Community Advisor
May 20, 2024

What are the dimensions settings of your eVar and list var?  I wonder if the persistence and/or allocation is set up differently.  Additionally, list vars are typically set up to capture multiple values in one string.  They'll then be parsed out for reporting.

This link gives more info on allocation & persistence of list variables.  Full allocation gives full credit to each item touched before the success event.  Linear gives equal, partial credit to each touch.

https://experienceleague.adobe.com/en/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/conversion-variables/list-var-admin

 

V
Adobe Employee
VidhyaAk1Adobe EmployeeAuthor
Adobe Employee
May 21, 2024

Hi @josh__stephens 

The evar80 setting in AA
evar expires on visit and allocation is most recent


list2
it never expires and allocation is full



event



Could you please tell what is thee exact reason having different count  ?
what would be the recommended approach for this 

Josh Stephens
Community Advisor
Josh StephensCommunity Advisor
Community Advisor
May 21, 2024

Hi @vidhyaak1,

Thank you for sharing those dimension settings.  

With your current settings, for eVar80, all credit for the click will go to the last touch.

For the list var, full credit will go to each touch that's been seen for the lifetime of this Unique Visitor.  For example, if someone has had three touchpoints and then has a click, each of those three touchpoints will be incremented by 1 for the list var.  Only the last touch will be incremented by 1 for eVar80.  This is why you're seeing different results.

The best settings are really based upon your use case and the insights you're looking for.  With the list var, if you selected linear credit, each touchpoint would get partial credit for the click.  So in the example above, each of the three touchpoints would get 1/3 of a click.  When reporting, Workspace rounds to the nearest integer.  

Before making any changes, I'd suggest using Attribution IQ on the metric to look at different models and lookback periods.

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 23, 2024

Hi @vidhyaak1 

This is presumably by design. The list var column values are not the actual sum of events, they are the sum of the individual list var _value_ occurrences.

 

Event X firing twice, one with list var Y set to val1 and once val1,val2 will likely show val1:2 and val2:1, and combined to a column sum of 3.

 

so, the column sum in a list var context will not match the event instances when looked at them alone.

 

hope that helps,

Björn 

Cheers from Switzerland!
Terms & ConditionsAccessibility statement

Loading footer...