Mapping Dimensions to Measures [BETA]

OVERVIEW
MAPPING RULES

OVERVIEW

Using the Anodot Data Collectors, all dimension combinations are used for every measure.
This mechanism provides maximal granularity for every measure.

In the example image below:

  • The measures Bounce_Rate, Bounces and Hits

each get all combinations of:

  • The dimensions Country, Device_Category and Landing_Page

stream_table.png

 

In some cases though:

  • Not all dimensions are required for every measure. 
  • The resulting number of metrics in Anodot might be too large, and the user would like to reduce that number by reducing the dimension combinations for some or all of the measures.

To overcome these cases, Anodot Provides an advanced beta option to define which dimensions are used with each measure, thus keeping the wanted combinations and the number of metrics under control.

MAPPING RULES

The mapping rules define the required dimensions for each measure in the stream. The rules are defined in JSON format.

Currently, these rules can be defined by an Anodot CSR. They will be available to our customers in the future.

An example JSON definition:

{
"Bounces": {
"aggregationType": "gauge",
"keepOriginal": false,
"dimSets": [
[
"Device Category",
"Landing Page"
],
[
"Device Category",
"Source / Medium"
],
[
"Device Category"
],
[
"Landing Page"
]
]
},
"Hits": {
"keepOriginal": true,
"dimSets": [
[
"Device Category"
],
[
"Landing Page"
]
]
}
}
Was this article helpful?
0 out of 0 found this helpful