Always eVars and Never Props?

@skatofiabah eVars track something over multiple pages or sessions, like a campaign or user action that lasts a while. Props are for capturing data on a single page or event, and they don't stick around after that. Props are useful for quick insights and understanding the flow of users on your site, while eVars are better for tracking things that matter over time

Hi @skatofiabah ,

1. Props can collect data instantly and available for reporting. You can use props in real-time reports. eVars take at least 30 minutes to appear in reporting.
2. Props have the ability to become list props, which accept multiple values in the same hit. List eVars are a separate variable, and there are only three list variables available.
3. Props use pathing. which helps your organization to know how the user visited your site.

@skatofiabah you are correct, eVars can do most of what props can do... you can set them to hit expiry, you can use your flow diagrams.

Some of the points that @pradnya_balvir makes is that props are available immediately (I have not seen that... maybe for the real time reports (which need an overhaul) or the old "Reports and Analytic" which is now gone, but Workspace always has the same delay on showing the content (prop or eVar), and if you are using processing rules, you need time to let those process anyway.

List props are a good example, if you need another list, and you know it will be under 100 characters in total, a "list enabled prop" is a good option. The three "list" vars you get can take as many items as you want, so long as each item is under 255 characters, you could pass hundreds of items... but there is only 3 available (but using prefixes and classifications you can make 1 list handle multiple items....)

As for pathing... that only pertains to the now sunset Reports and Analytics... as Flows can be used with any dimension.

The way I see it, for complex implementations, ones that I know will use a lot of dimensions, I will continue to use the 75 props available to me for small page level dimensions, then use Props (set to Hit expiry) for large page dimensions, as well as eVars for attribution, and eVars for Merchandising dimensions... 

You don't have to of course... that is your prerogative... if you know you won't exceed your eVar limits, then you can do most of everything with eVars.

Well I am gonna give you a different perspective. 
Lets say you start doing everything with Evars in implementation and you will run out of the number of evars thats allotted. So rather try to evaluate when is it best to set the prop vs evar.