Compare rollups to global report suites

Global report suite: Implementation is altered to send image requests across domains into a single global report suite in addition to individual report suites.

Rollup report suite: Created in the Admin Console. Takes the sum of each metric at the end of every day.

Server calls: Global report suites increment secondary server calls, while rollups do not make any server calls whatsoever.

Implementation changes: Rollups do not require any implementation changes, while global report suites require an additional report suite ID be placed in the s_code.js file.

Duplication: Global report suites deduplicate unique visitors, while rollups do not. For example, if a user visits three of your domains in the same day, rollups would count three daily unique visitors. Global report suites would record one unique visitor.

Time frame: Rollups are only processed at midnight each night, while global report suites report data with standard latency.

Breadth: Global report suites can attribute credit to conversion variables between report suites, as well as provide pathing across report suites. Rollups have no way to communicate between report suites.

Historical data: Rollups can aggregate historical data, while global report suites only report data from the point they were implemented.

Reports: Global report suites provide additional information on ALL reports implemented; rollups provide aggregate data on only high-level reports.

Supported products: Rollups are not supported in Data Warehouse or Discover. SiteCatalyst 15 is limited to 200 child report suites. Global report suites can be used across all products, and can have an unlimited number of child report suites.

When choosing whether to use rollups or global report suites, consider the following:

• Are the number of server calls critical to my organization? If keeping server calls limited is important, consider using rollups; global report suites almost double the number of server calls made.
• Does reporting a high-level total of traffic across all suites suffice? If deduplicated visitors are a requirement, consider implementing a global report suite.
• Are pathing and conversion/success events across domains important? If cross-site campaigns are heavily used, consider implementing a global report suite.
• Is viewing total site data time-sensitive? Individual report suites still report near real time; if seeing report suite totals the next day is adequate, rollups are recommended.
• Is there a large amount of actionable historical data? Global report suites cannot report retroactively - rollups are recommended if historical data is important.
• Is Data Warehouse and Discover essential to supplement reporting? If so, a global report suite is recommended.

Neither choice affecrts individual report suites. Carefully consider the pros and cons before determining which your organization prefers.