Expand my Community achievements bar.

Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!
SOLVED

Fallout 'next hit' query

Avatar

Level 2

Hi all,

having a little bit of trouble with a fallout report.

We currently have 2 pages with 'next hit' query set between them. the first pages looks right but the fallout is extremely high. In the journey they are directly next door.

 

When creating a sequential segment 'a>b within 1 page view' the number of visits makes more sense and doesn't correspond at all with the fallout report.

I appreciate hits and page views are a different thing, but why might this be happening to my fallout report? Is there anything i need to be aware of in my tagging? I cannot see anything firing after page view in debugger.

 

thanks!

1 Accepted Solution

Avatar

Correct answer by
Level 10

Create a segment with the criteria "within one hit" and the result will match the Fallout.

I would presume there are some s.tl() calls firing on the first page before the second page loads. That must be happening often but not always.

Share the URLs of page A and B, we'll look into that.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 10

Create a segment with the criteria "within one hit" and the result will match the Fallout.

I would presume there are some s.tl() calls firing on the first page before the second page loads. That must be happening often but not always.

Share the URLs of page A and B, we'll look into that.