The short answer
Keep one Google Analytics account in the group's name, with two named people at the group as Administrators. Give the agency the role it needs on the property, not control of the account.
Use one property per website. If every office is on the group domain, that is one property, and an office label on every event splits the numbers by office.
Set event data retention to 14 months, keep patient details out of every event, and move properties between accounts when offices are bought or sold.
One account, a property per website
This guide is for a dental group with three or more offices. Google Analytics is set up in layers: an account, the properties inside it, and a data stream for each site. Whoever holds the account holds every office's history.
One for the group
Group account
- Google's examples give one account to the legal entity that owns the data, so the account is in the group's name.
- Two people at the group are Administrators. The agency gets a role on the property it works on.
- One account can hold up to 2,000 properties, so it has room for every site the group owns.
One per website
Group website property
- A property represents a website or app. On a single group domain, every office page reports into this one property.
- It has one web data stream for the site. Google allows up to 50 streams, but one site needs one.
- Office by office numbers come from an office label on each event, not from a property per office.
Only if the office has its own site
Office site property
- An office that still runs its own domain gets its own property inside the group account.
- Name it for the site address, so nobody reads the wrong office's numbers.
- When the office moves onto the group domain, its pages start reporting in the group property. Keep the old property for history.
Whether offices should share one domain at all is in one domain or separate office sites. The tags that feed Analytics are in Google Tag Manager for dental groups.
Who gets which role
Analytics has five roles. A role given at the account level covers every property in it, and you cannot give that person less on a single property. So add the agency and office staff at the property level, and keep account-level roles for the group.
Administrator
Full control, including adding and removing people. Keep it to two people at the group.
Editor
Can change every property setting but cannot manage users. Fits the agency that runs the setup.
Marketer
Can create audiences and key events and import key events into Google Ads. Fits the person running ads.
Analyst
Can share explorations with others on the property. Fits a group analyst or a finance lead.
Viewer
Can see reports and settings and build their own explorations. Fits office managers and owners.
Worth knowing before you add people
- Two data restrictions, No Cost Metrics and No Revenue Metrics, hide spend or revenue from a person while leaving the rest of the report.
- Only an Administrator at the account level can delete users, and the last Administrator cannot remove themselves.
- User groups let you give a whole team one role, but the account has to belong to a Google Marketing Platform organization first.
The other accounts a group should hold, and the order to take them back from an agency, are in switching a dental marketing agency.
Label every event with its office
Page reports can show visits to each office page. But a patient who reads a blog post and then taps Call is not on an office page, so the call has no office. The fix is an office label sent with every event.
1. Work out the office
In Tag Manager, a RegEx Table variable reads the page path and returns the office label. Pages that match no office get a default value.
2. Send it with every event
Add a parameter named office to the Google tag's configuration settings, set to that variable, so page views, calls, forms, and bookings all carry it.
3. Register it once
In Analytics, create an event-scoped custom dimension called Office for the office parameter. It shows in reports 24 to 48 hours later.
A site can also set the label in its own code, through the data layer. That route and the report built on it are in the per-office marketing report. The table below needs no change to the site.
Office label table
List each office and its page. You get the rows for the RegEx Table, in the order they should go, with problems flagged. Tag Manager checks rows from the top and stops at the first match, so an office inside another office's folder goes first.
In the variable, leave Ignore Case and Full Matches Only on, which is how Tag Manager sets them by default, and use Page Path as the input. Check a few office pages in Preview before you publish.
Keep 14 months of detail
Standard Analytics properties keep event-level detail for 2 months or 14 months. The setting does not touch standard reports. It limits explorations and funnel reports, where you build your own views, such as offices side by side over a year.
Set it to 14 months under Data settings, then Data retention, so this year's numbers can be set against last year's. An Editor can change it. Google waits 24 hours before applying a change, and a longer setting also applies to data not yet deleted.
Bought, sold, and new offices
New office page
No new property. Add its row to the office label table, publish, and check in Preview that its page views and calls carry the new label.
Office joins with its own property
Move the property into the group account. The person moving it needs Administrator and Editor on both accounts. The measurement ID stays the same, so no tags change.
Office sold or closed
Remove that office's people at the account level. If it had its own property, it can move to the buyer's account. What happens to the office page is in moving, merging, or closing an office.
When a property moves, Google lets you keep its current permissions or replace them with the new account's. After a purchase, replacing them keeps the seller's users and old agency out. The full list of accounts to collect is in marketing due diligence for a practice acquisition.
Red flags
The property sits in the agency's account
Then the group's history lives in an account it does not control. The property can be moved, but only with the agency's help.
One Administrator
If that person leaves the group, nobody is left who can add or remove users. Keep two at all times.
A property per office on one site
Each office ends up in its own report with no group total, and a page tagged for two offices is counted twice. One website, one property.
Office labels typed by hand on each tag
Spellings drift (Midtown, midtown, mid-town) and one office becomes three rows. Set the label in one place.
Detail kept for 2 months
Explorations and funnel reports cannot look back further than the retention setting, so a year-over-year comparison comes up empty.
Patient details in events or labels
Google's policy forbids sending names, email addresses, or phone numbers, including in custom dimensions and campaign tags.
Checklist
Analytics checklist
0 of 12 done
Related guides
Which events to count, and how to keep patient details out of them, is in tracking calls, forms, and bookings without patient details. Search data for each office is in Search Console for dental groups.
The map of the other group jobs is marketing a multi-location practice or DSO.
For a multi-office group
DDS Web Solutions builds websites and runs search, ads, and reporting for dental practices. Our team has been building websites since 2014, we have served 100+ practices, and our offices are in Sacramento and San Mateo.
For a group, we can set up Analytics in the group's name, with us as an Editor, label calls, forms, and bookings by office, and report them in SmileTrak. We do not promise rankings. See DSO and multi-location marketing, or request a quote.
FAQ
Should a dental group use one Google Analytics property or one per office?
One per website. A property represents a website or app. If every office is on the group domain, one property covers them all, and an office label on each event splits the numbers. An office still on its own domain gets its own property in the group's account.
Who should own the Google Analytics account?
The group. Google's account structure examples give the account to the legal entity that owns the data. Two people at the group should be Administrators, and the agency should have the role it needs on the property, such as Editor.
Can an office manager see only their own office?
Not inside one shared standard property. Roles apply to the whole property, so a Viewer sees every office on it. Share a report filtered to their office label instead, or a per-office summary each month.
How do we get a property back from a former agency?
Ask them to move it. Google lists hiring a new agency as a reason to move a property, and the person moving it needs Administrator and Editor roles on both accounts. The measurement ID does not change, so the tags keep working. Choose to replace the permissions, so the agency's people do not come with it.
What happens to the data when a property moves?
Google says the reporting data is moved, not copied, along with the data streams, settings, and custom definitions. Linked accounts such as Google Ads stay linked. The change history from before the move stays with the old account.
How long until a new office label shows up in reports?
Google says to allow 24 to 48 hours after you create the custom dimension. Set it up before an office opens or joins, so its first weeks are counted under its own label.
Sources
- Analytics Help: Google Analytics hierarchy
- Analytics Help: Google Analytics account structure
- Analytics Help: Access and data-restriction management
- Analytics Help: Add, edit, and delete users and user groups
- Analytics Help: About custom dimensions and metrics
- Analytics Help: Data retention
- Analytics Help: Move a property
- Analytics Help: Best practices to avoid sending personally identifiable information
- Tag Manager Help: User-defined variable types for web