Adobe recommends using eVars, not props

Question

From the props documentation page:Adobe recommends using eVars in most cases. In previous versions of Adobe Analytics, props and eVars had advantages and disadvantages to each other. However, Adobe has improved eVars to where they fulfill almost all use cases for props.This one puzzles me. eVars work with events because eVars persist, while props don't perisst. For instance, when building hit-based segments for traffic reports, I would use props because I know I won't include unwanted hits due to an eVar still being set.What are your thoughts on this recommendation? Do I use an out-dated understanding of how eVars and props work?

PratheepArunRaj · Accepted Answer

Dear Daniel,Adobe recommends eVars over Props because if you set eVar expiration to Hit, it behaves as a Prop. The earlier version of Adobe Analytics had advantages related to segmentation (As you said), Pathing, Participation, etc.Even if you build a segment in eVar, now you have the option to select Default (Repeating), Instance, and Non-Repeating as attributions, so you can use eVar now instead of Prop. Pathing is available in Workspace for all the dimensions. Attribution modeling made all the attributions possible.If you think about everything, an eVar can replace Prop easily and thus Adobe Recommends it. Thank You, Arun.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded