Fallout conundrum

[Andrey_Osadchuk]

Can anyone explain why the Fallout below shows different number of visitors for a given Day, how is it possible that one of the numbers is higher than the number shown in the freeform table?

[Asheesh_Pandey]

Fall Out:

All Visitors touchpoint is looking for all visitors qualify for a calendar date range as first touchpoint, while day (Aug 24, 2019) is only showing visitor qualify for the day.

Freeform:

Only showing visitors qualify for the day.

Solve:

Reset freeform calendar date range to Aug 24, 2019.

E.g.

Fall Out

Freeform

To Solve - Reset Calendar to selected date.

Thanks,

Asheesh

[Andrey_Osadchuk]

Hi Asheesh,

The date in the fallout shown in my screenshot is the first touchpoint. The explanation above does not help, unfortunately.

Any other thoughts?

[Asheesh_Pandey]

Humm, I got it correct for first touch point and segment having same date range, you may wanna play with your day segment. lmk

[Andrey_Osadchuk]

The segment I used i just a day, there is no any other criteria in it. This is why I consider this a conundrum because logically it's not possible that different visitor numbers are returned for the same day.

[Asheesh_Pandey · Accepted solution]

Another thing on virtual report suite, using visitor container segment gives expected results while on parent report suite it should match visitor data anyways.

[cmabie]

Want to follow up here to see if there is any explanation for why using a VRS causes this problem: Was this ever addressed?

[Andrey_Osadchuk]

Asheesh, you are right! This was a virtual report suite; the parent suite returns the data accurately.

Do you know the causing factors of that inconsistency in VRS? What should be taken into account to avoid such issues?

[LeeDixon]

Did you ever find a solution to this Andrey?

[cmabie]

I haven't been able to find any evidence that it has been fixed or even addressed. I am still having this problem.

[analytics_union]

Just wanted to add that I had the same problem here, and found that it's because of how segments are applied in Fallout charts, as explained here: https://docs.adobe.com/content/help/en/analytics/analyze/analysis-workspace/visualizations/fallout/f...

Hopefully, Adobe will change this so that the Fallout report in AW is consistent with its R&A cousin.