Fallout 'next hit' query | Community
Skip to main content
sallyd67892944
sallyd67892944
Level 2
February 4, 2020
Solved

Fallout 'next hit' query

  • February 4, 2020
  • 1 reply
  • 2537 views

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!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Andrey_Osadchuk

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.

1 reply

Andrey_Osadchuk
Andrey_OsadchukAccepted solution
Level 10
February 14, 2020

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.

Terms & ConditionsAccessibility statement

Loading footer...