You need to bring in the dimension values, not the dimensions
themselves! Click on the arrow at the end of a dimension. It will show
you the values that this dimension assumed in the past 6 months. You can
then select and drag & drop the dimension items into a table. You can do
the same for a different dimension, which will be added in the table,
instead of replacing. You end up getting 'Mixed Dimension Items' in the
same "level" of the table.
It seems like that you talked about mixed dimension, which is already a
thing. Of course, it works only with dimensions items. But you might be
able to work something out.Check here under 'Mixed dimension items' for
You can create a 'Visit' level segment, specifying that:Page equals
'Page A'THEN Page equals 'Page C'. Additionally, in the 'THEN' clause,
you can set that 'Page C' condition is on the next hit of 'Page A' if
you are interested in this tight scenario.Use the segment to filter the
metric you want. Create a similar segment for Page B.
It can be:i) a data availability issue (e.g. the respective data layer
property is empty in some cases),ii) an analytics implementation issue
(for some reason, eVar doesn't get populated), oriii) expected (eVar was
never meant to get populated in those case).I would start by searching
patterns in Analytics. Are the "Unspecified" instances related to a
specific Device, Browser, Page, etc. dimension?
Hi @yokok9528851 If the segment you use in the VRS is DW-compatible, you
can simply select it from the "Available Segments" list that exists
within the "Build Report" section of the 'Data Warehouse Request'.