Expand my Community achievements bar.

Fallout reports: Allow additional sequencing constraint parameters.



Currently within fallout reports users have two criteria options for evaluating paths: "eventual path" or "next hit".
Given that segmentation capability exists for within hits, pageviews, visits, minutes, hours, and additional time periods, it reasons that more options could be made available.

This idea is to enable support for any of those criteria within the fallout report.


A specific example from our site:

We'd like to be able to evaluate the flow directly from 'page a' > 'page b' > 'page c'.

Our 'page b' is a search results page and users can view it many times sequentially.

As a result using the 'next hit' criteria, even with a page name eVar (with visit expiration) is very different than the results for 'then within 1 pageview', regardless of which setting for 'repeat instances' is selected at the project level.


For a more generic use case, this would allow folks to do page level fallout pathing more accurately, given many users will have link hits that can exist between pages.