Recording of dimension values
- Dimension definition is saved.
- Dimension is associated with a report group.
- Report group is assigned to an event.
- Event is triggered.
The above has some implications that are best explained by example. Suppose you have an event with the following configuration:
Event | Report Group | Included dimensions | Start Date for Recording Dim Values |
---|---|---|---|
EventA | ReportGroup1 |
|
Day 1 |
As soon as the dimensions are associated with the report group and the report group is associated with EventA, values are recorded for DimA and DimB whenever EventA fires.
Suppose that three days later two more report groups are created and associated with EventA, so that the configuration now looks like the following:
Event | Report Group | Included dimensions | Start Date for Recording Dim Values |
---|---|---|---|
EventA | ReportGroup1 |
|
Day 1 |
ReportGroup2 |
|
Day 4 | |
ReportGroup3 |
|
Day 4 |
Now, when EventA fires, dimension values are recorded for dimensions A-E, yet there is no data at all for DimC, DimD, and DimE before Day 4. When dimensions from ReportGroup2 and ReportGroup3 are added to reports, there are no values from before Day 4.
Suppose that another three days passes, and then DimC is added to ReportGroup1. The event configuration now looks like the following:
Event | Report Group | Included dimensions | Start Date for Recording Dim Values |
---|---|---|---|
EventA | ReportGroup1 |
|
|
ReportGroup2 |
|
Day 4 | |
ReportGroup3 |
|
Day 4 |
Since DimC was added to ReportGroup1, there is no data for DimC in recorded instances of EventA + ReportGroup1 combination before Day 7. While the dimension is included as part of the report group, all values displayed for ReportGroup1\DimC before Day 7 are null values.
However, if you use EventA + ReportGroup2 or EventA + ReportGroup3, there are reported values for DimC for Days 4 and onward.
This distinction can be confusing in reports using the configured dimensions.