Skip to main content
seong_munn72942
seong_munn72942
June 28, 2017
Solved

Why does Prop and Evar have different values?(PV, Visit, UV)

Hi,

I stored the Page ID value in Prop and eVar.

The Page Views, Visits, and Unique Visitors values of Prop and eVar are different.

ex)

I want to know the why. please reply.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    StevenHofheinsAccepted solution
    Adobe Employee
    May 16, 2019

    Seong,

    There are a few different things that could affect these to have different results between an eVar and a prop.

    1. If the prop or the eVar isn't fired on some pages.

    ex 1: Lets say an eVar was already set before visiting this page and the visitor visits a page without a prop set the eVar will be passed and the prop wont be.

    ex 2: If its a page where the eVar isn't set and prop is and this is the first page of the visit the prop will be sent but the eVar won't.

    2. If the expiration of the eVar is set to a certain time limit where they can pass new values through it.

    Looks like you have this set up to visit, so you shouldn't have a problem with this.

    If this doesn't answer your question please email client care at:

    clientcare@adobe.com

    Please include—

    Company:

    Report Suite:

    Issue:

    eVar and Prop:

    Thanks,


    Steven Hofheins | Adobe Support

    View in thread

    4 replies

    Hyder_Ziaee
    Adobe Employee
    Hyder_ZiaeeAdobe Employee
    Adobe Employee
    June 28, 2017

    Hi Seong,

    Are these collected on each page? Also what is your expiration for evar?

    Translate
    seong_munn72942
    seong_munn72942Author
    June 30, 2017

    Thank you for answer,

    Page ID is not collected on some pages, and evar expiration is 'Visit'.

    Translate
    Adobe Employee
    StevenHofheinsAdobe EmployeeAccepted solution
    Adobe Employee
    May 16, 2019

    Seong,

    There are a few different things that could affect these to have different results between an eVar and a prop.

    1. If the prop or the eVar isn't fired on some pages.

    ex 1: Lets say an eVar was already set before visiting this page and the visitor visits a page without a prop set the eVar will be passed and the prop wont be.

    ex 2: If its a page where the eVar isn't set and prop is and this is the first page of the visit the prop will be sent but the eVar won't.

    2. If the expiration of the eVar is set to a certain time limit where they can pass new values through it.

    Looks like you have this set up to visit, so you shouldn't have a problem with this.

    If this doesn't answer your question please email client care at:

    clientcare@adobe.com

    Please include—

    Company:

    Report Suite:

    Issue:

    eVar and Prop:

    Thanks,


    Steven Hofheins | Adobe Support

    Translate
    Urs_Boller
    Community Advisor
    Urs_BollerCommunity Advisor
    Community Advisor
    May 17, 2019

    while most of the differences between prop and evar have been pointed out, this would only partially describe the differences in the numbers. I mean, if the eVar and the prop is set exactly on the same hit (assuming its always together), the solutions above would only describe the differences for pageviews. eg. on page 1 both have been set, user navigates to a next page (without pageId), only the pageview counter for the evar will increase (due to visit expiry).

    but: the numbers are not the same for visits/unique visitors!most likely there is another case leading to the difference: the pageID has beehn set right before your data timerange started and the user had at least  1 hit within your daterange not setting the pageId. example: user arrives on page before midnight, pageId will be set. after midnight, he makes another hit but not set the pageId. the result is, that you only have 1 visit/unique visitor for your evar, not for your prop (due to expiry of evar and not set a prop on the new day). the result is the small difference you can see in your tables...

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...