# Change the tags in your container by asking, and publish them when you are ready

> Baker connects to your Google Tag Manager container to read its tags, triggers, variables and change history, and to prepare changes in a chat. Nothing reaches Tag Manager until you press Publish. Then Baker applies the changes, saves them as a container version and publishes that version, so they go live on your site at that moment, without a second approval inside Tag Manager.

Source: https://withbaker.com/integrations/google-tag-manager · Updated 2026-11-21

## What Baker does

- **See what your container does.** Ask which tags fire on which pages, what sends data to Meta or Google Ads, or whether a conversion tag is set up. Baker reads the whole container.
- **See who changed what.** Baker reads the container's history, so "what changed in Tag Manager last week" gets a real answer, including changes saved but not live yet.
- **Tags, triggers and variables by asking.** Add an event tag, a trigger or a data layer variable, switch on built-in variables or tidy folders. Baker checks each change against the container before it waits for Publish.
- **One version, published at Publish.** When you press Publish, Baker applies the changes in the right order, saves a version and publishes it. Your site runs the new tags from then on.
- **The container on your landing pages.** Add your container ID once and every landing page Baker publishes loads it. Forms can push their events to its data layer.

## How it works

1. **Connect your Google account.** In Brain → Integrations, connect Google Tag Manager with a Google account that can publish the container, then choose the containers Baker should manage.
2. **Ask Baker for the change.** Describe the tracking you need in a chat. The changes appear in the chat's list of changes for you to review.
3. **Publish.** Press Publish. Baker applies the changes, saves a container version and publishes it.

## What Baker reads and what it can change

| What | Baker | When | Why |
| --- | --- | --- | --- |
| Tags, triggers, variables, folders and built-in variables in the containers you choose | Reads | When you ask | To answer questions about your tracking and to check every change against what the container holds. |
| The container's versions and change history | Reads | When you ask | To tell you what changed, when, and whether it is live. |
| Tags, triggers, variables, folders, built-in variables and container settings | Changes | Only when you press Publish | Only the changes you reviewed in the chat, applied when you press Publish. |
| A new container version, published | Changes | Only when you press Publish | So the changes you approved run on your site. Baker holds back publishing if the container has conflicting edits. |
| Form events from your landing pages | Sends | All the time | When the container is on your landing pages, the Form steps you choose are pushed to its data layer. |

## What you need

- A Google account with Publish permission on the container. Read permission is enough to look, but not to publish.
- The admin or member role in Baker to connect it.

## Questions

### Do I still need to publish inside Tag Manager?

No. When you press Publish in Baker, Baker saves a container version and publishes it. Say so to anyone who reviews changes in Tag Manager, because the changes reach your live site at that moment.

### Is connecting Tag Manager the same as adding its container to my landing pages?

No, they are two parts. Connecting the account lets Baker read and change what runs inside the container. Adding the container in Landings → Tracking makes your landing pages load it. Many teams need both.

### What if someone else is editing the same container?

Before publishing, Baker checks the container's workspace. If there are conflicting or unreviewed edits, Baker holds back the version instead of publishing someone else's work with yours.

### What permission does the Google account need?

Publish permission on the container. With less, Baker can still read it, and a Publish that reaches a step the account may not take says which permission is missing.

## Guides

- [Connect Google Tag Manager to Baker](https://withbaker.com/help/integrations/google-tag-manager.md)
- [Add a tracking tag to your landing pages](https://withbaker.com/help/integrations/tracking-tags.md)
- [Publish your changes](https://withbaker.com/help/publish.md)

## Still stuck?

Write to support@withbaker.com. A person answers within 24 hours. https://withbaker.com/help/contact
