How to Build and Configure a Google Analytics 360 Roll-Up Report

by Hollis Bowman

In the previous entry in this series on Roll-Up Reporting for Google Analytics 360, I went over the more strategic considerations of how and why you might build a Roll-Up of existing GA web properties. Now that you have the foundations sorted out, you’re ready to build against your plan. The mechanics of building a Roll-Up are quite well documented in the Google help file here, so to add value to the conversation this post also includes the ‘gotchas’ we’ve run into in creating these for our clients.

What You’ll Need To Get Started (The Basics) 

Google Needs To Create The Roll-Up

Currently, Google must create a new Roll-Up property directly. This is a very simple process documented here. You won’t be able to add source properties until the Roll-Up is created. If you’re working with a Google Analytics Certified Partner (GACP) like Napkyn Analytics they can help get this done for you. 

All Source Properties Must Be GA360

Because this is a 360 feature, you can’t add a standard GA property to a 360 Roll-Up, regardless of whether or not the property is under a 360 contract. You need to promote the relevant properties to 360 before you’re able to add a source property to your Roll-Up. This can be done easily within Google Analytics Suite Home with sufficient user rights. Simply navigate to the property you want to promote in the Suite, and toggle the service level from Standard to 360. 

All Source Properties Must Belong To The Same Account

In some cases, organizations will have properties to roll up that belong to multiple accounts. If this is the case, you need to migrate the properties to one account. This can be done within an existing account, or under a new account created for this purpose.

All Properties Must Be Associated With The Same Google Analytics Suite Home

If your Roll-Up or source properties are associated with a Suite Home account, you will need to verify the association of your Roll-Up and source properties with the same Suite Home account. This requires the active authority of your Suite Org Admin (highest user permissions) as there are legal implications to changing your 360 configuration. I strongly recommend that all sign-offs are completed directly by people within the organization for which the Roll-Up is being built who have sufficient authority to agree to terms and conditions. For agencies, this may require a conference call or in-person meeting to direct the appropriate resources to make these changes.

Permissions Levels

You need to have edit-level permissions for both the Roll-Up property and any source properties.

Advanced Configuration Of Your 360 Roll-Up (The Gotchas)

Standard Property And View Settings

You need to enable all the standard property and view settings, such as filters and ecommerce reporting, for your Roll-Up property.

Custom Dimensions And Mapping

Custom dimensions from your source properties are not inherited to the Roll-Up. You need to enable new custom dimensions for your Roll-Up property. This is a good opportunity to take a critical look at how you’re going to use custom dimensions at a Roll-Up level. Are there dimensions that can be aggregated into a single label across source properties? Are there any dimensions that are extremely specific to a source property that do not apply at a Roll-Up level? Once you have a list of the custom dimensions you want to add, in the process of creating them you are given the opportunity to map different indices to a single slot at the Roll-Up level. This can help with consolidation if custom dimension ‘X’ is index 1 in one source property and index 10 in another.

Product Integrations And Uploads

Any product integrations or uploads that you’ve done in source properties are not inherited by the Roll-Up property. You will need to reconnect any relevant uploads to the Roll-Up. In general, I don’t see much value in connecting search console at a Roll-Up level (for example) only because the reporting that results from that is quite specific to particular domains and often does not apply well at a macro level from a Roll-Up.

User ID

User ID must be enabled, and User ID views must be created for a Roll-Up property. This follows the same steps you used to enable this feature for your source properties.

Multi-Currency Handling

By enabling multi-currency support in your source property tracking code, you are able to get currency figures converted to the standard currency enabled for the Roll-Up property. Google Analytics will use the daily exchange rate to calculate the aggregated product revenue figure. So, if you have a US/UK Roll-Up and head offices in London, your product revenue will aggregate all the revenue from the US and UK source properties in GBP, and local product revenue will be USD for your US property and GBP for your UK source property.

Questions or comments? Give us a shout anytime and we’d be happy to have a conversation about Roll-Ups for your enterprise.

 

Hollis Bowman

Senior Analyst and Google Analytics 360 Practice Lead

Hollis Bowman is Napkyn Analytics' Practice Lead for Google Analytics 360. As a senior member of our Analyst Team, Hollis' specialty is working with our clients to turn questions into data and data into answers.

See more posts from Hollis