Using evars and props to capture internal search terms | Community
Skip to main content
Magus_Boston
Magus_Boston
July 28, 2016
Solved

Using evars and props to capture internal search terms

  • July 28, 2016
  • 2 replies
  • 1218 views

I am using prop and evar to capture internal search terms. But when I am testing it out in the dev environment.. 

i) Page views (76 page views) in prop report is way too less than evar (12,519) report. Why is this happening? 

ii) The total of Visits (1039), Pageviews (74) and Unique visitors (377) is far greater than the sum of all populated records in the prop report i.e when I sum visits the total is 58, Pageviews is 74 and Unique visitors is 47.  

But  when I check the evar report for the totals.. there is a 'None' row which has all 99 percent of values which is not listed in the prop report? 

Can anyone please help to understand this? 

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

Hey Magus.

 

The evars and prop behave differently. When you send a value in a prop and an evar on a page both increase in page views count by one. However on the next page, the evar values may persist, thus increasing the page views further for it and the prop value's page view will still be one. 

Apart from this if you are using any metric which gives site wide totals in the report (ex: visits) then it will also show how many hits or pageviews, visits, etc did not have the value. Hence you are seeing the high percentage against the None in evar report. 

2 replies

TanmayMathur
Adobe Employee
TanmayMathurAdobe Employee
Adobe Employee
August 2, 2016

Hi Bharat,

Welcome to the Adobe Analytics Community!

Could you check the attribution settings of the Evar? Normally the values go to 'None' when they are not attributed to any other value. 

Hyder_Ziaee
Adobe Employee
Hyder_ZiaeeAdobe EmployeeAccepted solution
Adobe Employee
August 3, 2016

Hey Magus.

 

The evars and prop behave differently. When you send a value in a prop and an evar on a page both increase in page views count by one. However on the next page, the evar values may persist, thus increasing the page views further for it and the prop value's page view will still be one. 

Apart from this if you are using any metric which gives site wide totals in the report (ex: visits) then it will also show how many hits or pageviews, visits, etc did not have the value. Hence you are seeing the high percentage against the None in evar report. 

Terms & ConditionsAccessibility statement

Loading footer...