Exit Rate Definition Evar or Prop

[MartaSk1]

Hi everyone, 

I have read the documentation and browsed the Q&As but so far, I am still not sure how an exit rate works combined with an eVar or Prop, hope you can help:

We have few pages on our website and a lot of applications, sometimes several per page. That's why I need to use eVars / Props to check after which interaction with an application or after which process step a user left the website. The challenge here is, the eVars / Props I am referring to, are not always filled.

Here is my example, I need clarification on:

Case1:
Hit 1:      eVar_X (Application Name) fired with Value App A
Last Hit before Exit: eVar_X (Application Name) fired with Value App A

Case2:
Hit 1: eVar1 (Application Name) fired with Value App A
Last Hit before Exit: eVar_X (Application Name) not fired

Case3:
Hit 1: eVar_1 (Application Name) fired with Value App A
Hit 2: eVar_1 (Application Name) not fired
Last Hit before Exit: eVar_1 (Application Name) not fired with Value App B

Do I assume correctly that
1. In case 1 eVar_X with Value A counts an an exit

2. In case 2, none of the values of eVar_X counts as an exit
3. In case 3, eVar_X with Value B counts an an exit

I do not entirely understand this part of the definition: "Only one exit exists per dimension per visit. It is not necessarily the last hit of the visit if the dimension was set in previous hits."
Does that mean that in my case 2 above, the value App A is counted as an exit, because Hit 1 is the last hit where a value for eVar_X was set? 

Thank you! 

[Josh__Stephens]

Hi @MartaSk1 

When working with eVars, you'd also need to consider the persistence of the dimension.  If set to most recent | visit, for example, the values would differ than if set to original | visit.

Props can have pathing set up, meaning an entry & exit version is kept.  

When considering persistence for an eVar or exit prop, the value may be the last one seen during the visit, even though it may not have been set on the very last hit of the visit.  

[MartaSk1]

Hi @Josh__Stephens ,

ah, yes of course. Assuming that the eVars I am considering are expiring after 1 hit, would this be the result?

1. In case 1 eVar_X with Value A counts an an exit

2. In case 2, eVar_X with Value A counts an an exit
3. In case 3, eVar_X with Value B counts an an exit

If eVars persist throughout the visit, would this be the result?

1. In case 1 eVar_X with Value A counts an an exit

2. In case 2, none of the values of eVar_X counts as an exit
3. In case 3, eVar_X with Value B counts an an exit

It would be great if you could confirm or reject it. Would help me a lot to understand. Thank you!