Google Tag Manager access: which Google account sees your container

What it does

Tag Manager access belongs to Google accounts, not to companies or websites. A typical business has a container created years ago by a developer under a personal Gmail address, a marketer working from a Workspace address, and an agency with its own login. Each of them sees a different list of GTM accounts. When you sign in and do not find the container, it usually exists; it is simply owned by another Google account. Editing the wrong container is a quieter problem: you publish tags, they show up in GTM, but the site loads a different container ID and nothing changes for real visitors.

Start from the site, not from Tag Manager. Open the page source or use Google's Tag Assistant and note the container ID, which looks like GTM- followed by letters and digits. Then check each Google account you control: open Tag Manager, go through its accounts and look for that exact ID. If none of your accounts sees it, ask the current owner to add your address in Admin → User Management. Container permissions come in levels, from read and edit to approve and publish, and only publish lets you push a version live, so ask for what you actually need.

Keep a short record per client: the container ID, the GTM account it lives in, and which Google accounts hold publish rights. Avoid giving publish access to a personal address that may leave with an employee. Before publishing, look at the live version of the container, not only at your workspace, because someone may have published while you were working. And always keep a way back: Tag Manager stores versions, so a bad publish can be undone by publishing the previous version again.

In AdAce Ads you can grant Tag Manager access from more than one Google account. The service then shows every Google account that granted access, which GTM accounts and containers each one sees, and marks the container that was actually found on the client's site. You choose which Google account to use for planning, preparing and publishing tag changes. The plan is prepared in a new workspace first, publishing requires your password and second factor, and a rollback is available if something looks wrong after release.

Why it helps

• No more guessing which login owns the container.
• The container found on the site is marked, so you are less likely to edit the wrong one.
• One client can be served through several Google accounts.
• Publishing stays behind your password and second factor.

How to set it up

1. Open “Tracking” and grant Tag Manager access with a Google account; repeat for other accounts if needed.
2. Review the list of Google accounts with the GTM accounts and containers each one sees.
3. Find the container marked as found on the site.
4. Choose the Google account that has access to that container for planning and publishing.
5. Prepare the change plan, review it and publish with your password and second factor.

Good to know