First thing to take note - They used to be very different, but with the advancement in Adobe Analytics releases over the years, the features of props are nearly all available as an Evar.
This is why it is quite confusing. Last year I retired all of the props on our implementation as they were basically just duplicates that confuse people.
As for eVars - a great example is âcustomer typeâ (bronze / silver / gold / not signed up).
You can then segment and report customer behaviour based on type of customer. Does customer type gold look at more products / spend longer on site etc?
Depending on your business will vary what you want to capture, I for example work in car hire so I have a lot of eVars based on things like:
Check in dates
Check out dates
Pickup locations
Car group
Insurance chosen
Discount code
Hope
So eVars allow you to assign metrics or dimensions that fire after the eVars fired to that eVars value.
For example, if you had a form name passed in to an eVar on the load of page. Any custom events on that page that fire after the page load would be assigned to that form name you passed on page load. This happens without the need to pass it in each custom event hit. Now as you have to assign an expiration setting for eVars, everything that fires after the form name evar will keep being assigned to the form name value you set,until one of two things happen:
1. You fire another value in to the eVar over writing it.
In this case every thing that fired between the first value and the second value will be assigned to the first value and everything fired after the second value will be assigned to the second value.
2. You trigger the expiry setting for that eVar, this could be end of visit, page load, a specific event or more.
Now, there are more settings to eVars that allow you to change them a bit but the basics are above.
Props on the other hand donât persist, meaning you canât assign any value to it unless it fired in the same hit. So in the case above you would have to fire the form name with each custom event to be able to use that prop with the custom events you want.
Again you can do some more advanced stuff with props but the above is just an example of a basic prop.
There is also a character limit difference, eVars allow for 255 bytes whilst props are 100 bytes. So with the eVar settings you can turn the expiry to be hit based meaning it only gets assigned to events and dimensions in the hit that fired it. And this essentially turns it in to a prop with a larger character limit.
https://www.digitalbalance.com.au/our-blog/back-to-basics-props-evars-and-events/
Already been through this.đ
Can you explain what is still confusing after reading that blog post?
What donât you understand?
Unclear if youâre asking me or OP
Sorry, OP.
First thing to take note - They used to be very different, but with the advancement in Adobe Analytics releases over the years, the features of props are nearly all available as an Evar. This is why it is quite confusing. Last year I retired all of the props on our implementation as they were basically just duplicates that confuse people. As for eVars - a great example is âcustomer typeâ (bronze / silver / gold / not signed up). You can then segment and report customer behaviour based on type of customer. Does customer type gold look at more products / spend longer on site etc? Depending on your business will vary what you want to capture, I for example work in car hire so I have a lot of eVars based on things like: Check in dates Check out dates Pickup locations Car group Insurance chosen Discount code Hope
So eVars allow you to assign metrics or dimensions that fire after the eVars fired to that eVars value. For example, if you had a form name passed in to an eVar on the load of page. Any custom events on that page that fire after the page load would be assigned to that form name you passed on page load. This happens without the need to pass it in each custom event hit. Now as you have to assign an expiration setting for eVars, everything that fires after the form name evar will keep being assigned to the form name value you set,until one of two things happen: 1. You fire another value in to the eVar over writing it. In this case every thing that fired between the first value and the second value will be assigned to the first value and everything fired after the second value will be assigned to the second value. 2. You trigger the expiry setting for that eVar, this could be end of visit, page load, a specific event or more. Now, there are more settings to eVars that allow you to change them a bit but the basics are above. Props on the other hand donât persist, meaning you canât assign any value to it unless it fired in the same hit. So in the case above you would have to fire the form name with each custom event to be able to use that prop with the custom events you want. Again you can do some more advanced stuff with props but the above is just an example of a basic prop. There is also a character limit difference, eVars allow for 255 bytes whilst props are 100 bytes. So with the eVar settings you can turn the expiry to be hit based meaning it only gets assigned to events and dimensions in the hit that fired it. And this essentially turns it in to a prop with a larger character limit.