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_6E55483C1EC2...
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-...
https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/adobe-recommends-using-ev...
https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/always-evars-and-never-pr...
...
