Search
Clear search
Close search
Google apps
Main menu

The instructions in this help article may be affected by recent changes in the Analytics user interface. See this blog post for details. Help center updates are coming soon.

About Roll-Up Reporting

This feature is only available in Google Analytics 360, part of the Google Analytics 360 Suite.
Learn more about the Google Analytics 360 Suite.

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.
Currently, you can't use Firebase properties in Roll-Up Reporting.

 

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., AdWords, 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 AdWords or AdMob accounts).

Session merging

When users are identified by the same Client 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).

If users are not identified by the same Client 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 Client ID on each Source Property

For example:

  • User has ClientID_1 on SourceProperty A
  • User has ClientID_1 on SourceProperty B
  • User navigates between the two properties within the time span of a single session as defined in your Property settings.

Result

  • 1 session is initiated and counted on SourceProperty A
  • 1 session is initiated and counted on SourceProperty B
  • Those 2 sessions are merged and are counted as 1 session in the Roll-Up Property
Different Client ID on each Source Property

For example:

  • User has ClientID_1 on SourceProperty A
  • User has ClientID_2 on SourceProperty B
  • User navigates between the two properties within the time span of a single session as defined in your Property settings

Result:

  • 1 session is initiated and counted on SourceProperty A
  • 1 session is initiated and counted on SourceProperty B
  • Those 2 sessions are not merged and are counted as 2 sessions in the Roll-Up Property
The effect of Session timeout settings

For example:

  • Session timeout is 30 minutes (the default) on both of the Source Properties and on the Roll-Up Property
  • User has ClientID_1 on SourceProperty A
    • Pageview on Page1 at 0 minutes (Landing Page)
    • Pageview on Page2 at 40 minutes
    • Pageview on Page3 at 80 minutes
  • User has ClientID_1 on SourceProperty B
    • Pageview on PageX at 20 minutes
    • Pageview on PageY at 60 minutes
    • Pageview on PageZ at 120 minutes
  • The user views the pages in the following order:
    • Page1 at 0 minutes
    • PageX at 20 minutes
    • Page2 at 40 minutes
    • PageY at 60 minutes
    • Page3 at 80 minutes
    • PageZ at 120 minutes

Result:

  • 3 sessions in SourceProperty A since the pageviews have more than 30 minutes between them. Each session has a single pageview.
  • 3 sessions in SourceProperty B since the pageviews have more than 30 minutes between them. Each session has a single pageview.
  • Those 6 sessions are merged and are counted as 2 sessions in the Roll-Up Property because the first 5 pageviews occur within 30 minutes of each other, and the last pageview occurs 40 minutes after the previous pageview and so results in another session:
    • One session with 5 pageviews in this order: Page1, PageX, Page2, PageY, Page3
    • One session with 1 pageview: PageZ

If you were to set different session timeouts for the Roll-Up Property and for each of the Source Properties, you could have even more varied results between the session count in the Roll-Up Property and the sum of sessions in your Source Properties.

Requirements

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

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., www.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

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.

Was this article helpful?
How can we improve it?
Google Analytics training and support resources

Check out our comprehensive list to learn more about Analytics solutions.