When you use rollups in version 15, Adobe Analytics limits how many reports and report suites can be combined. Understanding these limits can help you create efficient rollups that do not stop processing after a short period.

Rollup complexity score

Every rollup created comes with a complexity score - a hidden number that determines the processing load a rollup takes. If a rollup's complexity score is too high, processing for that day does not occur.

Complexity score is calculated by multiplying the number of active reports by the number of report suites in the rollup. By default, several reports are enabled in a rollup. You can have reports enabled or disabled by having a supported user contact Customer Care with the reports that you want enabled/disabled.

The more reports that are enabled in a rollup, the fewer report suites it can have before reaching the complexity score limit. The more report suites are included in a rollup, the fewer reports it can have enabled. If your organization intends to include many report suites in a rollup, work with Customer Care to ensure that only vital reports are enabled.

The complexity score limit to rollups is currently 4000. If your organization has a specific business need, you can contact Customer Care to raise this limit by request. Adobe Analytics engineers can increase the complexity score required to process the rollup within reason. The recommended limit to the number of report suites included in a rollup is 100.

Rollups inside rollups

It is possible to include rollups as children of rollups. Adobe recommends including only two levels of rollups (report suite > child rollup > parent rollup); adding additional levels beyond two can work, but is unstable.

Reports such as the Most Popular Sites report treat immediate children as line items. If you are looking at a Most Popular Sites report within a Parent rollup of many child rollups, you only see the aggregated child rollups.

You can mix and match rollups and report suites within a rollup.

Troubleshooting rollups

The first thing to check is the complexity score of the rollup in question. A common pitfall is that users add additional report suites to rollups, often tipping the complexity score over the threshold. Rollups with a complexity score over the threshold do not even attempt to process data.

If you accidentally tip a report suite over the threshold, bringing the complexity score back under allows the report suite to process again. No reprocessing requests are required, as a rollup monitors its last processed date. If a rollup is more than a day behind in processing, it automatically processes as many days required to catch itself up.