The short answer
Create one Tag Manager account in the group's name, with two named people at the group as administrators. Give the agency the container permission it needs, not account control.
Use one container per website. If every office is on the group domain, that is one container. An office still on its own site gets its own container in the same account.
Keep Publish to a short list, name every version for what changed, and check changes in Preview before they go live.
One account, a container per website
This guide is for a dental group with three or more offices. Google Tag Manager holds the tags that count calls, forms, and bookings and send them to Google Analytics and Google Ads. Whoever controls it controls how every office is measured.
One for the group
Group account
- Google describes the account as the top level for a company, so the group gets one account in its own name.
- Two people at the group are administrators. The agency is a user with container access.
- Every container the group's offices use sits inside it, including sites that came with an acquisition.
One per website
Group website container
- Google says to create one container for each website, not one for each page.
- On a single group domain, every office page shares this one container.
- Office by office reporting comes from the page address and the office in each event, not from extra containers.
Only if the office has its own site
Office site container
- An office that still runs its own domain needs its own container, inside the group account.
- Give it a clear name, the site's main address, so nobody publishes to the wrong office.
- When the office site moves onto the group domain, its tags move into the group container.
Whether offices should share one domain at all is in one domain or separate office sites. Which events to count, and how to keep patient details out of them, is in tracking calls, forms, and bookings without patient details.
Who gets which permission
Tag Manager has two layers. At the account level a person is an Administrator or a User. Administrators can create containers and change anyone's access. At the container level each person gets No access, Read, Edit, Approve, or Publish.
Read
Can see the tags, triggers, and variables but change nothing. Fits an office manager or an owner who wants to look.
Edit
Can build changes in a workspace, but cannot save a version or publish. Fits an analyst or a second agency.
Approve
Can save versions as well as edit, but cannot publish. Fits a reviewer before changes go live.
Publish
Can put changes live on the site. Keep this to a short list: the agency that runs the tags and one person at the group.
What Google says about losing access
- Keep at least two active administrators. Tag Manager shows a notice when an account has only one.
- An account or container with no administrator is deleted. People with read access have 30 days to export it from the trash.
- Google's support team cannot add users to an account for you.
The other accounts a group should hold, and the order to take them back from an agency, are in switching a dental marketing agency.
Access review
Copy each person from Admin, User Management, with their account role and highest container permission. The review counts the group's named administrators and flags agency administrators, shared logins, and personal addresses.
The form starts with a sample list of six people. The agency is an account administrator, one group administrator is a shared login, and an office manager signs in with a personal address.
Workspaces, versions, and publishing
Every change starts in a workspace, a draft of the container. A standard account has three at a time: the default workspace and two more. Tag Manager 360 has no limit. Give the agency and the group's own team separate workspaces, so one side never publishes the other's unfinished work.
Publishing saves a version and makes it live. Google keeps a publish history that shows who published each version and when. Name each version for what changed, such as "Book button clicks for all offices", and add a short note.
Before
Check the change in Preview on two or three office pages. A staging site can have its own environment, so changes can be tested there first.
Publish
One person from the short Publish list puts it live, with the version name and note filled in.
If it breaks
Open Versions, choose the last good version, and publish it again. Then fix the change in a new workspace.
New, sold, and moved offices
New office page
No new container. Check in Preview that calls, forms, and the Book button on the new page are counted under the right office.
Office joins with its own site
Ask the seller to add two group people as administrators, or export their container and import it into a new one in the group account. Change the IDs, then check in Preview.
Office sold or closed
Remove that office's people from User Management. What happens to the office page is in moving, merging, or closing an office.
The full list of accounts to collect when an office joins is in marketing due diligence for a practice acquisition.
Red flags
The agency created the account
Then the group's tags live in an account the agency controls. Google advises that the account be managed by someone in your organization, not an outside agency.
Only one administrator
Google recommends at least two. If that one person's Google Account is deleted, the account can be left with no administrator.
A shared login
An address like marketing@ that several people sign in with. Google advises real user accounts, one per person.
Personal Gmail addresses with access
Access leaves when the person does. Use work accounts the group manages.
Versions with no names
A list of versions called Version 41, 42, 43 makes it hard to find the one to roll back to. Name each version for what changed.
A container per office on one site
Two snippets on the same pages can fire the same tag twice and double the counts. One website, one container.
Checklist
Tag Manager checklist
0 of 12 done
Related guides
Search data for each office is in Search Console for dental groups. Counting calls by office is in Google Ads budgets and call attribution for 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 Tag Manager in the group's name, with us as a user, count 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 Tag Manager container or one per office?
One per website. Google says to create one container for each website or app, not one per page. If every office is on the group domain, one container covers them all. An office that still has its own domain gets its own container in the group's account.
Who should own the Tag Manager account?
The group. Google advises that the account be managed by someone in your organization, not an outside agency, and that at least two people be administrators. The agency gets the container permission it needs as a user.
What happens if a Tag Manager account has no administrator?
Google says an account or container with no administrator is deleted automatically. Users with read access have 30 days to export the container from the trash. Google also says its support team cannot add users for you, so keep two administrators at all times.
Can the agency make changes without being able to publish them?
Yes. Edit lets a person build changes in a workspace. Approve also lets them save a version. Only Publish puts changes live. On Tag Manager 360 there is also an approval request step before publishing.
How do we undo a bad publish?
Open Versions, pick the last good version, and publish it. Google keeps a publish history that shows when each version was live and who published it.
How do we set up tags on a site that joined the group?
Google lets you export a container as a file and import it into another container. A common way is to export the group's container, change the IDs and domain that differ, and import it into the new office's container, then check it in Preview before publishing.