Workspace: Props & Evar explanations | Community
Skip to main content
S
scottt6073095
Level 4
February 10, 2017
Solved

Workspace: Props & Evar explanations

  • February 10, 2017
  • 4 replies
  • 3326 views

Hi All,

I am looking for a simple way to help campaign managers use the Adobe Workspace tool however they get really confused when trying to figure out when to use props versus evars. I have tried to tell them on many occasions when to use them and how the interpretation changes however I would like to get opinions from others on what works in helping employees to clearly learn when and how to use props and evars. 

Some items I got stuck on and couldn't correctly answer was the small data discrepancy between the below reports when comparing page views and visits.

 

the evars are higher for page views and visits but what is the technical reason behind it.

 

for pages, I noticed that the page views and visits are the same totals but not the same numbers for each page. Also, the number of records are higher for props? what is the technical reason behind it and the reason for none

 

thanks,

Scott

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 Hyder_Ziaee

So, from what I can understand, each page gets its own value of the URL for the prop and evar. If that is the case, the instances should match. 

About the numbers differing for the prop and evar, I really think this is cause of allocation. 

Since this is a page URL that you are capturing. I would say use the prop. If you are firing the prop and evar on a s.tl() call as well, then I do not see why a prop would not work for all your needs.

Is there specifically something that I am not thinking about....

-Hyder

4 replies

Hyder_Ziaee
Adobe Employee
Hyder_ZiaeeAdobe Employee
Adobe Employee
February 13, 2017

Hi Scott,

Since the evars persist. you can have more page views associated to an evar value than its counterpart prop value.

Suppose a user goes to Page A. and it fires prop1 & evar1 on Page A as "XYZ", Then the user visits Page B, and here both are not present in the request. Since prop did not persist, it has 1 page view. However, the evar will have 2 page views.

The second questions might be related to allocation. Would need to test for surety.

S
scottt6073095Author
Level 4
February 13, 2017

thanks for your response on this topic and the great example. Also, some context behind why I ask about these things is because someone asked in a meeting and I could not clearly explain.

I am still a little confused, I understand that the evar persists therefore will pass the data to the next page and at times have more traffic metrics than props however, if the same pages have a page url prop and evar shouldn't the page views be the same? The visits metric matches exactly with page url prop and evar but probably because I have  the evar set as allocation most recent and expire after visit. Also, for accuracy's sake should I use the page url prop or evar for traffic reporting as I was told that a evar can do anything a prop can do except pathing.

thanks again for any insights.

Scott

Hyder_Ziaee
Adobe Employee
Hyder_ZiaeeAdobe EmployeeAccepted solution
Adobe Employee
February 16, 2017

So, from what I can understand, each page gets its own value of the URL for the prop and evar. If that is the case, the instances should match. 

About the numbers differing for the prop and evar, I really think this is cause of allocation. 

Since this is a page URL that you are capturing. I would say use the prop. If you are firing the prop and evar on a s.tl() call as well, then I do not see why a prop would not work for all your needs.

Is there specifically something that I am not thinking about....

-Hyder

S
scottt6073095Author
Level 4
February 16, 2017

yes, to confirm, each page gets its own value of the URL for the prop and evar. 

question: how do I look into the possible issue with the allocation being the cause?

 

Thanks again for any help,

Scott

Terms & ConditionsAccessibility statement

Loading footer...