[UA] About Roll-Up Reporting [Legacy]

Roll-Up Reporting aggregates data from multiple Analytics properties and lets you see that data together in the same reports.

For example, if you have multiple properties for brand sites in different countries (example.fr, example.co.uk, etc.), you can aggregate that data to see global-performance metrics, and then drill down to compare brand performance among countries.

Roll-Up Reporting comprises two types of properties:

• Source Properties: Individual Analytics properties that include data from a single site, app, or internet-connected device.
• Roll-Up Properties: Properties that serve as aggregators of the data from multiple Source Properties.

 

In this article:

Data

Roll-Up Properties can include data from both web and app properties, as well as properties whose data is uploaded via the Measurement Protocol.

Roll-Up Properties do not include data that you import into Source Properties, nor data that you link to Source Properties (e.g., Google Ads, AdMob, AdSense, YouTube). If you want to replicate the linked data from your Source Properties in your Roll-Up Properties, you need to create the same linking at the Roll-Up level (e.g., link your Roll-Up Properties to the relevant Google Ads, AdMob, or Google Marketing Platform accounts).

Roll-Up Properties include Real-Time data from their Source Properties.

You can't send data directly from a site or app to a Roll-Up Property (e.g., by tagging the site or app with the Tracking ID for the Roll-Up Property, or by sending hits directly to the Roll-Up Property via the Measurement Protocol). Hits sent directly to a Roll-Up Property are dropped.

Session merging

When users are identified by the same Client-ID or User-ID across the different Source Properties, then session data for those users is usually merged. An exception to this can occur when users navigate between Source Properties and cross the boundaries of the Session timeout settings (described below).

The types of Source Properties from which data is merged include:

• Properties for sites linked via cross-domain tracking
• Properties for different directories or subdomains of the same top-level domain
• User-ID properties for sites or apps that share the same login

If users are not identified by the same Client-ID or User-ID across different source properties, then the session data is not merged.

Session timeout settings can affect how sessions are merged when users navigate among Source Properties.

As a result, the number of sessions in a Roll-Up Property does not necessarily equal the sum of all sessions in Source Properties. The following examples illustrate how sessions are merged under different circumstances.

Same ID on each Source Property Different ID on each Source Property The effect of Session timeout settings

Requirements

A Roll-Up Property and all its Source Properties must all belong to the same Analytics 360 account.

You need to set the service level for each Source Property to 360.

A single Source Property can be aggregated into multiple Roll-Up Properties. Roll-Up Properties, however, cannot serve as Source Properties.

Setting up Roll-Up Properties require no additional tagging.

Creation and management

Currently, creation of Roll-Up Properties is handled by the Google Analytics 360 Support team.

When you want to create Roll-Up Properties, contact Google Analytics 360 Support, and provide the following information:

• Company name
• Account number for the Analytics account in which you want the Roll-Up Property
• Time zone for the Roll-Up Property (e.g., (GMT -08:00) Pacific Time)
• Default hostname (e.g., example.com)
• Number of Roll-Up Properties you want

Once your Roll-Up Properties are in place, you can manage the addition and removal of Source Properties in Analytics Admin under Property > Roll-Up Management. Learn more

System limits

Each Roll-Up Property can have a maximum of 200 source properties.

Data limits

Each hit processed by a Roll-Up Property is counted separately from the corresponding hit in the Source Property, and counted as .5 of a hit rather than 1 as it applies toward your monthly billable hit volume. For example, if you have 10 million hits in a Roll-Up Property, Analytics counts that as only 5 million.

Temporary data anomalies

You many notice a difference in the count of direct sessions between a Roll-Up Property and its corresponding Source Properties: the Roll-Up Property can temporarily have a higher count.

Source Property: If a user initiates a direct session after a session that was initiated by a campaign, and that direct session falls within the campaign-timeout setting, then the source of that direct session is attributed to the most recent campaign.

Roll-Up Property: No data from before the creation date is rolled up. If direct sessions in Source Properties are attributed to campaigns from before the creation date of the Roll-Up Property, then that campaign data is not rolled up, and those sessions appear as direct. This can lead to a greater count of direct sessions in the Roll-Up Property than in all of the Source Properties combined.

This discrepancy will disappear once the campaigns in the Source Properties time out, and direct sessions are attributed to campaigns that were created after the Roll-Up Property was created.

Currency conversion

If you have implemented Multi-Currency Support in the tracking code of your Source Properties, then all of your currency data is converted to the currencies set for your Roll-Up Property views.

Analytics currently does not convert currency values if you have not implemented Multi-Currency Support.

Remarketing Audiences

You can create Remarketing Audiences based on your Roll-Up Properties if you enable Remarketing and Advertising Reporting Features for the associated Source Properties. Note that this feature is subject to your Ads Personalization settings whether at the event, user property, and/or property level for each Source Property. If ads personalization is disabled for any event via these controls in a Source or Roll-Up Property, then that event is not able to be used for ads personalization within the Roll-Up Property.