Google Tag Manager
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.
- See what your container does
- See who changed what
- Tags, triggers and variables by asking
- One version, published at Publish
- The container on your landing pages
- Built by
- Baker
- Category
- Analytics and tracking
- Plan
- Every plan
- Connects by
- Signing in
- Updated
- November 21, 2026
How it works
From connecting to publishing, in three steps
- 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 does
Everything Baker does with Google Tag Manager
-
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.
You approve
Nothing changes in Google Tag Manager until you press Publish
Baker prepares every change in a chat and shows it to you. It applies only when someone on your team who may publish presses Publish, and if you discard the chat, nothing applies.
Data and permissions
What Baker reads and what it can change
Exactly what Baker uses from your account, when and why. Baker asks only for the permissions this needs.
| 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.
Frequently asked 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.
Keep learning
- Connect Google Tag Manager to Baker Connect your Tag Manager container, add it to your landing pages, publish tag changes from Baker, and disconnect, with what happens to your data.
- Add a tracking tag to your landing pages Add a pixel or analytics tool such as TikTok, Pinterest, Clarity, Hotjar or PostHog to every landing page, change it, or remove it, from Landings → Tracking.
- Publish your changes What Publish sends live, in what order, how to check it worked, and how to discard a chat's changes instead.
Used together with
- Google AnalyticsBaker reads your GA4 traffic and conversions, prepares changes to what your property measures, and applies them only when you press Publish.
- Google AdsBaker reads your Google Ads accounts, prepares campaigns, keywords, ads and budgets, and changes Google Ads only when you press Publish.
- Meta AdsBaker reads your Meta ad accounts, prepares campaigns, ads, budgets and audiences, and changes Meta only when you press Publish.
- Tracking tagsAdd TikTok, Pinterest, Clarity, Hotjar, PostHog and other tags once, and every landing page Baker publishes loads them. Forms send their events too.