Description
My use case:
Why is this feature important to you
Try explaining to a non-analyst Adobe Analytics user, why a custom built segment is not segmenting and values are being shown that should be excluded. Indeed, there is a manual approach, but it has it's own downsides.
In the examples that I provide, to illustrate the point, I am using one request examples and as such might not make sense in aggregated perspective. So keep in mind that a large site with a lot of different marketing placements appearing in many different combinations (A with B, A with C, C with X) and thus when you only want data for a particular ID, the current solution will create a lot of data noise.
How would you like the feature to work
On example of a single request. When I build a segment that checks against a list evar in a single occurrence, and the list evar contains ID's "A", "X" and "Z", and I want to return only values (let's say we talk view counts) for "A" in my table/view - the segment should be able to understand the list variable and selectively return values (view counts) for "A" only and not include values for "X" and whatever else. TLDR: Built segments should understand the elements on the list evar and return wanted values only.
Current Behaviour
Any segment built to filter list variables, doesn't understand to return values only for the elements in built segments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.