Multiple Universal Analytics Tracking Codes

Question: We are working with our client to install two analytics tracking codes on the site. Is it possible to set up multiple trackers through MonsterInsights for our clients’ different departments?

Answer: MonsterInsights doesn’t support multiple trackers however you really shouldn’t be using multiple tracking codes because Google has support for this type of user management built-in and it’s designed for exactly this type of scenario. By managing them as a single property, you can minimize the risk of property level changes that cause for analytics discrepancies, and also save on Google Analytics account and user quotas.

Solution: Using access-restricted views of the same property like adding your users to one view, and yours to the other, of the same Google Analytics property, is a better solution.

That would allow for a lot less issues with Google Analytics, particularly on certain Google Analytics features that don’t support multiple UA codes, and would also allow for more flexible tracking. Additionally, that’d also allow for a lot more organizational control, and in GA the view permissions allow for easy control over who can see/edit/delete each view. Plus if they need to edit property level things like

If the concern is that they’re going to be editing the views your team is using, you could simply only add them to a view for them, and then either add your team at the property or the view-for-you level.

Example Use Case:

Let’s say, that you have a GA property that you want to have 3 teams on:

1. Admins, let’s assume this is your IT staff, need to be able to access the entire property’s reports.
2. Organic needs to be able to access the property report but you don’t want them to have the same view as
3. NonOrganic (and vice versa.) So that way each team can add their own filters to the analytics reports and such. Maybe one of these teams should have the ability to read + change the view, but the other should only have read access

Google natively supports this type of permissions out of the box, as it’s specifically designed for enterprise customers where user permissions are leveled access inside of organizations. When traffic and events are reported to Google Analytics, they’re reported to the Property’s UA code. From there, the data is spread to all views of a property.

So, by default, your property has a view, which by default is called All Website Data. What you should do is make a second view, let’s call it Organic team. Then in that view, if you go to the Admin options -> User Management, you can add people to this view. When they log in, they will only be able to see this view (not the others of the property). Additionally, you can change their permissions between the following 4 options:

1. Manage Users: Can manage account users (add/delete users, assign permissions). Does not include Edit or Collaborate.
2.  Edit: Can perform administrative and report-related functions (e.g., add/edit/delete accounts, properties, views, filters, goals, etc., but not manage users), and see report data. Edit permission is required at the view level to apply filters. Includes Collaborate.
3. Collaborate: Can create personal assets, and share them. Can collaborate on shared assets, for example, edit a dashboard or annotation. Includes Read & Analyze.
4. Read & Analyze: Can see report and configuration data; can manipulate data within reports (e.g., filter a table, add a secondary dimension, create a segment); can create personal assets, and share them, and see shared assets. Cannot collaborate on shared assets.

So let’s say the organic team should only be able to read the reports. In this case, you just add them to their Organic view that you made with Read permissions. They will only be able to read that one view’s reports, and will not be able to see other views. Any changes they make to their view will not affect any other view.

Some helpful links:

• How to add/modify/remove users on the account, property and view levels.
• User permissions that a user can have at the account, property and/or view levels.
• How to make a new view.

What we would recommend is the following setup, assuming you have 2 teams that need to view the GA data and edit it separately from each other, and 1 team/person who needs to be able to view it all.

1. View 1: “Raw Data,” this view should not be editable or viewable by either the Organic or the NonOrganic team. This view is to serve as a backup, in case a team messes up a filter and you need to compare data to an unfiltered view.
2. View 2: “Organic team,” this view should be created, and you should add any members of the organic team to this view, with the edit privileges
3. View 3: “Non-Organic team,” this is the view for the NonOrganic team, and you’d add your members here

Any user who needs access to all views of a property should be added at the property level.

The person(s) who are managing your GA account, and who will be responsible for adding views and users should be added at the account level.

This will allow you to have 2 independent copies of the exact same GA data, that can be edited by 2 different teams without being able to see/change each other’s data, and allows for backup view just in case.

That’s it!

Are you interested in verifying your site in Google Search Console to see how your site is doing in the Google Search Results? Then please see our guide: How to Verify Your Site in Google Search Console with Google Analytics.