Props and eVars in Link Tracking

[skatofiabah]

Hi All,

I'm curious when I should be including props and/or eVars into link tracking. My understanding is an eVar can do everything a prop cannot and a prop cannot do everything an eVar can. Should I always be looking at and using just eVars in both page tracking and link tracking? 

Thanks!

[harikrishnadevanabowina]

HI @skatofiabah I suggest using eVars for link tracking.

eVars (Custom Insight Conversion Variables) are designed to track conversions and persist values across multiple page views. They are ideal for capturing campaign information, product categories, or any data that needs to be associated with a user's journey.

I see that in other thread you were mentioning about the campaigns you are running, so suggested to use eVars that props (They are useful for capturing page-level details such as page name, title, or other dynamic content)

This section might be helpful - https://experienceleague.adobe.com/en/docs/analytics/components/dimensions/evar

Hope this helps. 

[skatofiabah]

Hi @harikrishnadevanabowina ,

So I should almost never need to use props? Basically eVars for Page and Link Tracking?

[harikrishnadevanabowina]

HI @skatofiabah Yes, unless ff the link information is only relevant to the current page (e.g., a specific offer or promotion), a Prop might suffice.

BR, Hari

[skatofiabah]

Hi @harikrishnadevanabowina ,

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

[Jennifer_Dungan]

I include both props and eVars into my Link Tracking... for correlation on my links... I use a lot of eVars like props, I also have eVars that are used as conversions....

Let's say I am using an eVar to capture a campaign, I will track it on the page, and not on the link, since the eVar already has a Visit level attribution, and I don't want to inflate my instances. (see your other thread)

But for my eVars which are Hit level, that I use to track page details (like the URL) I will include those on the hit, since that is the URL where the link tracking is occurring. 

[skatofiabah]

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 persists and doesn't get repopulated or reset, then it will persist in the background and be included for that link call when you track and filter on the eVar with the page value?

[Jennifer_Dungan]

That is correct... I like to keep my instance of the eVar clean, set them on the page, then let the link have the attribution... However, I have many "hit" level eVars and that wouldn't work for them... therefore, all my hit based eVars must be set on the link,

There is of course, also the eVars that pertain specifically to the link (and not to the page), those are set only on the click, and may or may not have attribution on them (depending on my needs).... I may want to keep the value of a click all the way through to my order complete, if the click in question is related to an internal promotion.... 

[skatofiabah]

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?

[Jennifer_Dungan]

Correct.

Every hit will have the value, the eVar Instance is limited to just where it's set.