The reporting schema is for analytical tables only.

Usually data is taken from the domains and worked within the business intelligence (BI) tool. However, at times it is easier for analysis if specific reporting tables can be created based on the groupings of the aforementioned domains to create analysis.

An example is a KPIs reporting table. This may look like a "one day per row" table, with aggregations from ten domains to create the KPI metrics on a daily basis. In general, this can be quite difficult to create in a BI tool, both technically and data volume-wise, so leveraging the data warehouse for this is an option.

Another example of an analytical table is funnel analysis. This may contain data from a web tracking domain, but aggregated by user to limit the data volumes being ingested by the BI tool.

All reporting/analytical tables go into the reporting schema, where the table names do not need to follow a naming convention, other than to clearly label what the table is to be used for, e.g. reporting.cohort_analysis.

What’s Next