Exits / Exit rate for dimension / eVar

[MartaSk1]

Hi everyone, I need the exit rate of users at a specific step on my website. The issue is, I cannot use the page because the application on the website I want to measure the exit rate for is on a single page. 

I have an eVar that has a value of the process step the user is currently in, but I am not sure an eVar would work for an exit rate?

[MandyGeorge]

Because evars have values that can persist beyond the initial hit, you can't really use evars as an exit value. This is where you would use props. What you can do is you can set up the prop to capture the value of the evar when it is fired, this will let you capture the same data but in a prop. With props being traffic variables, you will be able to use entries/exits for it. 

If you are looking for exit rate for a particular page, you can always use a flow diagram, it will show you where people where before/after that page, including the amount of people that exited. You can also have segments built off the logic in the visualization, so you can see it in a table too.

[MartaSk1]

Thank you for your quick feedback. Does the value of theVar persist until it is replaced by another value? For example, let's call it eVar100, if the user is in step 1 of the application, eVar100 will say 'Step1'. Then the user moves to the next step and eVar100 gets the value 'Step2'. Will the value 'Step1' for eVar100 still persist, so will it have two values at this moment?

[MandyGeorge]

Evars will persist until the designed expiry that was selected when they were created. If you go under admin > report suites > conversion variables, you can see the list of evars and the "expiry" assigned to each of them. Ideally your organization should have an SDR or some type of document where you can see all the information without having to dig through the admin settings. 

Also, evars can have more than one value stored in them while they're persisting, and the one that is given credit is chosen by the "allocation" that is set up for them.

[MartaSk1]

Thanks a lot, I really appreciate your help. I actually just found in the documentation that this specific eVar expires after a hit. So I guess, in this case, I will be able to use this for the exit rate? But I found another problem: The same evar100 process step values also appear on a different page. But I just want the exit rates for that one page. I would need To create a segment just for this eVar value AND the one specific page. But I guess exits do not work with segments, right? If I understand it correctly, in a segment, you always have 100 visits = 100 Entries = 100 Exits?

[MandyGeorge]

So even if the evar has a hit level expiry, evars don't have pathing options. If you search for one of your props, you should see the "prop name", as well as "exit prop name" and "entry prop name". The entry and exit versions of the props are created automatically, they capture the first or last (entry or exit) item in that particular dimension that is seen in the visit. Since there isn't a way to specify it's an exit, making it as a segment is difficult, but not impossible. Something like this should work.

I'll break it down a bit. It's a hit level segment, and in the hit level you have your page that want for the exit, I used search just as an example. So you want your page AND another container. This container is going to be at a visit level. Within the visit level container you're going to use a sequential segment. You want your exit page, and THEN exclude any other pages that are seen. This needs to be set at the "logic group" level. Since it's in a visit container, it won't let you set the exclude container as visit, so you want logic group instead.  In the exclude you're just going to have page (non-repeating instance) doesn't exist. 

The logic behind this is a bit complicated. The visit-in-hit part, you're returning a specific hit that is associated with a visit with the visit level conditions. Then the visit container is sequential, you're saying in a visit you saw the particular page, but then no other pages exist after that, meaning it would have to be an exit. 

[MartaSk1]

Thank you, @MandyGeorge ! Can I include my process step eVar into this segment logic you suggested above? Since the page stays the same the entire time, I will need to use the eVar to define at which step the user left. 

[Jennifer_Dungan]

Looks like @MandyGeorge has this one covered

But I just want to add that you can also pair a Hit based eVar with the Exits metric (not to be confused with the Exit Link Instances metric which is reserved specifically to clicking on exit links). Exits is not available in the segment builder, but is available to use in your tables.

[MartaSk1]

Thank you, @Jennifer_Dungan, so I could indeed use the hit based eVar for Exits and Exit Rate even though it does not have pathing like Props?

[Jennifer_Dungan]

Using my Canonical URL eVar (which is set to HIT expiry), I added Exits and Exit Rate:

The "total" exit rate, since every URL in my site has a canonical ink is expectedly 100%, but each individual URL shows its own unique Exit rate.

[MartaSk1]

Hello @MandyGeorge and @Jennifer_Dungan 

So I created the segment along with my page (non repeating instances and my eVar) and the result was 8,5% Exit Rate, which feels too low. I then created the exit segment just for the homepage and compared the result with the adobe native exits metric. It did not match. I then changed the non repeating instances to repeat ( default) and then it matches.

Could it be that we actually need to keep it at default? Could you explain in simple words why we would need the non repeating here as my page eVar expiry is set at hit anyway? The other eVar that I am using for the process step is not set for each hit though. Fr example, while the user is in process step 2, and does something there, e.g. sets filters, we always have the process step eVar set but when for example a pop up layer loads, it is not. Does that matter in this case?

Thank you!
Marta

[Jennifer_Dungan]

Yeah, I am not sure the non-repeating instance is needed in this scenario... non-repeating instance would also remove the times the value is set to the same value concurrently... which then wouldn't really meet your "Exit" requirement.

Example (eVar1 is Hit level, eVar2 is Visit level expiry)

• Page 1
  • eVar1 = "X"
  • eVar2 = "X"
• Page 2
  • eVar1 = "X"
  • eVar2 = "X"
• Page 3
  • eVar1 is not set, value is empty
  • eVar2 is not set, value remains "X"

Whether your eVar is hit or visit, the non-repeating instance would fall on Page1... (which wouldn't be your exit).... The Exit for eVar1 should be on Page 2, and the Exit for eVar2 should be on Page 3.

From: https://experienceleague.adobe.com/en/docs/analytics/components/segmentation/segmentation-workflow/s...