Hi @Jennifer_Dungan , Thank you for the quick response. The safest bet seems to just use eVars and keep it as short as possible. And if it needs to expire on hit like a prop, then do so. Otherwise, we are good?

Hi @Jennifer_Dungan , Thank you for this in detail! You are super knowledgeable and one of the best in Adobe. I understand the first half of your response. Can you explain the second half in more detail about what the non-repeating instance is in the attribution? Is there documentation on this on Ad...

Hi @Jennifer_Dungan , Thanks for the quick response. So those will count as hits if I apply a hit segment for an eVar where it expires on visit and the instance is only the initial landing page load?

Hi @Jennifer_Dungan , Thank you for the prompt response. I have some follow up questions: I can still look at the "page views" metrics with both a Prop and eVar set to be each other, correct? Persistence isn't an issue with this metric since it will get reset for each new page or page refresh?In you...

Hi @Jennifer_Dungan , Thank you for the prompt response. Your eVar for page shouldn't need to be included for the link tracking if it is set for the page, right? Because if the value persists, then the link will count a hit from the page level eVar, right?In other words, if a visit level evar persis...

Hi @Achyuth19 , You can still do page pathing and single page and event analytics with eVars though and they are more specific and better. So I'm having trouble understanding the use to ever choose a prop over an eVar.

Hi @pradnya_balvir, I read this on the prop analytics documentation. It still sounds like an eVar can do all of that and what a prop can do.

Hi @igupta , I think I understand what you are saying. However, the URL isn't what I filter on in my segment, it's the tracking code on a hit level. So I think this will capture all hits within a visit where the user came from tracking code "a".

Hi @harikrishnadevanabowina , Even then, an eVar could still solve that^, right?

Ok thanks!