Exit 1, while Occurrence 0

[Sergei_Kalinichenko]

Hi there!

The closest I manage to get were Solved: Showing Zero "0" in workspace and Visits showing zero for pages but has "Entries"..., but I have a little bit different case. Here Solved: adobe campaign delivery label visits showing "0" also I found valuable thoughts.

Goal was: to analyse digital campaign -  page & user behavior

Did a quick segment (hot): campaign code (dimensions expires on visit)  = abc

Got page URL to the table (expire on visit)

Added users, visits, time on site - all were going good. Apparently, added Exits and here popped up suspicious pages with 0 visits, but exits. First I thought something is setting this variable somewhere else, but occurrences are 0 which for me means, that this value was not set in image request.

For something to be in the table user must perceive a tracking code, but how he can exit from something without coming there?

Imaginary scenario: he opened the page in the tab and set this tab aside, then he saw an ad, clicked on it, landed on different page, then closed his browser? So he literally obtained the tracking code after opening the page i'm interested in, had no hits with it, but exit having the tracking code and all the tabs were affected by it?

[Jennifer_Dungan]

I a seeing similar data in my system... I assume this might be due to the lower traffic pages being more susceptible to hash collision (which is part of the way that Adobe handles some of the performance issues by hashing values)... but periodically, different values will identify as the same... normally, we look at the high traffic pages as opposed to the lowest traffic pages, but it sometimes results in some oddities...

You look like you don't have a lot of data (unless you have a segment applied) so I wouldn't think it would be hash collision would apply here... but exits are also part of a calculation, so there may be some error there...

You could reach out to client care to investigate, I would certainly be interested in what is happening.

[Sergei_Kalinichenko]

Thank you Jennifer! Will reach out to support and come back here with reply.

Yeah, this research was for very small campaign. Quick filters are there to filter out internal users and some burden pages.

[Jennifer_Dungan]

Good luck, and ok, the quick segments and being a test campaign explain the low values. But I agree, there shouldn't be an exit without an occurrence... that's wild.

[Sergei_Kalinichenko · Accepted solution]

Hi Jennifer, 

Together with support manager we got to 2 points:

1. Exits is a metric which looks over the visit, so the combination of hit segments did not play the role here.

2. And guess whose article we bumped into when we dug into details?

So, the answer to the matter sounds like:

Even after applying the segment where evar13!=internal, we are seeing the data for internal traffic in the report because the segment is applied at visit level and per the backend logic, if in any visit where even at least once the value evar13 is set as internal is being added up in the report and that's why we are seeing the data.

Which makes sense.

Thank you for amazing article.

[Jennifer_Dungan]

Glad I was able to help on two fronts. Also, I realized I was using a virtual suite that had a HIT based segment... when I look at the main suite, I don't have the issue... 

It's likely the segment causing some inconsistencies.