Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!
Segmentation in flow visualizations feedback
Hi everyone!
Recently, an issue was reported to Adobe regarding how segments are applied to flow reports. I wanted to get your feedback around if you find value around its current functionality, or around how we intend to change it.
How it currently works
When you apply a segment to a flow report, it first does all the pathing calculations, then applies the segment after. This image provides an excellent example:
Using the above image, first it calculates all paths from /search to /ware, then it applies the segment (hits where pages = /ware). What you end up with is a report that doesn't make a lot of sense.
What Adobe plans to change
Instead of applying the segment after paths are calculated, Adobe plans to apply the segment to each part of the path.
For example, instead of:
(/search then /ware) applied segment
It would be:
(/search with applied segment) then (/ware with applied segment)
If the above data was used, this specific example would show 0 for the entire report. Since /search had zero hits match the segment, naturally there would be no subsequent path instances.
We want your feedback!
This is where we want to hear from you.
- How do you expect segments applied to flow visualizations to work?
- Are there any scenarios where applying a segment after pathing data is calculated would be valuable?
We want to make sure that the planned changes are a direct upgrade to getting value out of flow reports. Please let us know!
