Is evar that expires after a hit the same as a prop? What's the difference? | Community
Skip to main content
Level 3
August 28, 2024
Solved

Is evar that expires after a hit the same as a prop? What's the difference?

  • August 28, 2024
  • 1 reply
  • 755 views

Taking page url as an example, what is the difference in capturing page url c02 in an evar that expires after a hit compared to page url t02 captured in a prop? 

 

Thanks in advance!

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 bjoern__koth

Hi @user70977 

essentially they react in the same way. I try to avoid props whenever possible, mainly because of length limitations.

Props are great if you use the real-time AA report. Back then, props were helpfule because they allow pathing, but nowadays this can be done on eVar level as well.

 

https://experienceleague.adobe.com/en/docs/analytics/components/dimensions/evar#concept_6E55483C1EC24566B5D3B2736E766EBC

Value of eVars over props

Adobe recommends using eVars in most cases, supported through the following:

  • eVars have a 255-byte limit in reports. Props have a 100-byte limit.
  • Props by default do not persist beyond the hit they are set. eVars have custom expiration, allowing you to determine when an eVar no longer gets credit for a subsequent event. However, if you use report time processing, both props and eVars can use a custom attribution model.
  • Adobe supports up to 250 eVars, and only 75 props.

See prop for more comparisons between props and eVars.

 

There are a bunch of discussion in these forums as well over it

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/props-for-pathing-when-analysis-workspace-allows-quot-flow-quot/m-p/670751#M3692

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/adobe-recommends-using-evars-not-props/td-p/398385

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/always-evars-and-never-props/m-p/694356#M52139

...

1 reply

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
August 28, 2024

Hi @user70977 

essentially they react in the same way. I try to avoid props whenever possible, mainly because of length limitations.

Props are great if you use the real-time AA report. Back then, props were helpfule because they allow pathing, but nowadays this can be done on eVar level as well.

 

https://experienceleague.adobe.com/en/docs/analytics/components/dimensions/evar#concept_6E55483C1EC24566B5D3B2736E766EBC

Value of eVars over props

Adobe recommends using eVars in most cases, supported through the following:

  • eVars have a 255-byte limit in reports. Props have a 100-byte limit.
  • Props by default do not persist beyond the hit they are set. eVars have custom expiration, allowing you to determine when an eVar no longer gets credit for a subsequent event. However, if you use report time processing, both props and eVars can use a custom attribution model.
  • Adobe supports up to 250 eVars, and only 75 props.

See prop for more comparisons between props and eVars.

 

There are a bunch of discussion in these forums as well over it

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/props-for-pathing-when-analysis-workspace-allows-quot-flow-quot/m-p/670751#M3692

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/adobe-recommends-using-evars-not-props/td-p/398385

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/always-evars-and-never-props/m-p/694356#M52139

...

Cheers from Switzerland!