This article is written by Brian Topham, Customer Care Program Manager at Adobe.
Have questions about Adobe Analytics. Ask the Community.
In the following example a user follows this path Pages: A > B > C > D. On page B, campaign X is passed and persists the rest of the visit.
A fall out report is then run in Workspace and Ad Hoc. The HIT level segment Campaign = X. is applied
When you drag a segment to the top of a fall our report it is considered a top-level segment. Ad Hoc you drag the segment inline with the fallout check points
In the this example, when doing a fallout for A > B > D, Workspace (behind the scenes) is creating a sequential segment: page A THEN page B THEN page D. So the full segment logic looks like:
(page A THEN page B THEN page D) + (Campaign = X)
The segment login in Ad Hoc (with the in-line segments) is:
[Hit where (page A + Campaign = X) THEN Hit where (page B + Campaign X) THEN Hit where (page D + Campaign = X)]
Reviewing the segment logic, notice that this visit would be in the Workspace fallout report, but not the Ad Hoc fallout report, as Page A does not have Campaign X.
Ad Hoc will evaluate the segment on a per fallout check point bases, where Workspace is just a sum of a sequential segment [page A THEN page THEN > page D] + the segment(s) the user adds. This can mean the data between Ad Hoc and Workspace may not match, especially when using a HIT level segment. This is because in essence the HIT level segment is being evaluated at a visit level. In this case was there a hit with campaign = X.