Fall Outs & Path Finder are used to look for behavioral patterns and Segments we want to address & market to. Doing so is very limited if not impossible using Pages alone. Instead we need to also add Variables and Events as nodes in Fall Out reports and Path Finder.
Events indicate a Visitor logically reached state X regardless of the Page it occurred on. Otherwise if all Events were tied to a single page, why would we need Events? Conversion Funnels allow Event flows but no pages. So to do Fall Outs with only pages at each node is missing the point of elevating and looking at Behaviors and instead stuck in the era of Page Counting. Example Below:
![](/skins/images/89607737A8DC1E6A7C97A43904C01FE4/responsive_peak/images/image_not_found.png)
CONCEPT: You want to look at the success from Page A to Page B for all Visitors who between those two looked at any of your on site sales promotions (captured by Event 1) - How would you do it? Multiple separate Fall Outs for every page between A and B where Sales Promos exist?
IDEA SUGGESTING: Instead, suggest the following: Page A > Event 1 > Page B
What if you wanted to look at this same Fall Out but do so for who looked at Car vs. Truck promotions (Hey - I'm Ford...) which you captured in eVar1? Clearly a core reason for collecting variables is to do exactly this and qualify events. So obviously we must be able to qualify Fall Outs
Same example then would be: Page A > Event 1 > eVar1="Truck" > Page B
This is just a simple & elemental example. Clearly could build more complex and meaningful patterns from this and make these very effective tools.
Consider also if Segmentation finally becomes a core pillar in ALL Omniture tools and especially Site Catalyst, then if you built the above Fall Out you could push a button to "Define Segment" and use this in Data Warehouse, Test & Target, Recommendations, Merchandising, etc.