What does persistency of eVars means?



Hi there,

I sometimes confuse myself with the concept of eVars, props and success events,

I keep on going back to the basics but can't quite wrap my head into the persistent concept. Is there any good example for this?


If there is a credit card application funnel (step 1 to 5 )

When eVar2 in step 1 is "Credit card application" , and it says that the value is persistent, why do we still need to call eVar2 for steps 2 - 5 ? don't we do that to props anyway? and it make sense for props because its used for individual page traffic report.

Hope that someone can enlighten me a little bit more in this.

Accepted Solutions (1)

Accepted Solutions (1)



An eVar is persistent which basically means it holds its value until the variable expires.

We can change the expiration of an eVar in the admin console and it can be based on a time period (a week, or a month) or after a visit ends.

In your case, if you want to find out the final conversion/completion of credit card form you will be firing an event at the final form submission, but at screen 1 option will only get the contribution of completion if you have evar fired with the option selected at the screen1.


Screen 1. is asking for Male and Female selection and getting storing  in evar 2 

The final Application Submission is getting counted with Event 10 which fires at screen 5.

During this user Journey use is performing multiple actions on screen 2-5  but

To know how many visitors who completed the registration were male or female you will get it with evar2 report with event 10 metrics.

Remember this is one way to look at it however there are multiple settings of evar which can change its behaviours and analytics.

Answers (3)

Answers (3)




Another advantage of capturing pageURL on each page apart from them not being present in the standard reports as Suneesh mentioned, is that evars allow for 255 characters, while props allow 100 characters only.



Correct, it totally depends on the analytical requirements,

also having Page URL or Page Name being capture in all the pages always helps in troubleshooting consider URLs are not available in standard Reporting, Visitor ID or session Id are another Another most commonly used variable which helps in reporting needs considering visitor ids are only available in DW reports.



This is such a good example, thank you so much,

The main reason why I ask as well is that I can see a few of websites that I'm taking care of usually prefer to trigger eVarxx which contains the pageName and also another eVarxx which contains the sessionID to always trigger from screen 1 - 5 constantly,

According to your example, technically they don't have to right? Would you have any idea on any advantage of doing that? Why do people firing constant eVars across funnels?