When exporting a flattened report, keep each flattened dimension as a separate column #12163
Description
Currently when we export a flattened report the CSV output (and others) looks like this:
Label | Visits | Total events | Events with a value | Total value | Minimum value | Maximum value | Unique visitors (daily sum) | The average of all values for this event
-- | -- | -- | -- | -- | -- | -- | -- | --
PluginTabs - Preview | 78 | 97 | 0 | 0 | 0 | 0 | 76 | 0
PluginTabs - Description | 35 | 41 | 0 | 0 | 0 | 0 | 34 | 0
PluginTabs - Faq | 19 | 20 | 0 | 0 | 0 | 0 | 19 | 0
PluginTabs - Documentation | 18 | 24 | 0 | 0 | 0 | 0 | 18 | 0
Instead we would like each individual columns listed like below, with their correct name and value, for all reports combining several levels and exported as flattened with flat=1
Event name | Event category | Label | Visits | Total events | Events with a value | Total value | Minimum value | Maximum value | Unique visitors (daily sum) | The average of all values for this event
-- | -- | -- | -- | -- | -- | -- | -- | --
PluginTabs | Preview | PluginTabs - Preview | 78 | 97 | 0 | 0 | 0 | 0 | 76 | 0
PluginTabs | Description | PluginTabs - Description | 35 | 41 | 0 | 0 | 0 | 0 | 34 | 0
PluginTabs | Faq | PluginTabs - Faq | 19 | 20 | 0 | 0 | 0 | 0 | 19 | 0
PluginTabs | Documentation | PluginTabs - Documentation | 18 | 24 | 0 | 0 | 0 | 0 | 18 | 0
Notes
- it's important we leave the
Labelcolumn for backward compatibility. - the new columns should be in both the reporting API and the processed report/metadata API
Why is this important? having the components of the Label column clearly separated (un-flattened) allows easy data analysis in the spreadsheet or in other data analysis systems. this will also be very helpful for Custom Reports export where the exported report should have all dimensions clearly listed out.