How to set up Google Tag Manager and connect it with AI agents

Google Tag Manager is optional. Connect it when you want AIM's AI agents to confirm that your analytics and conversion tags are actually installed before anyone trusts a conversion number or recommends more spend. The connection is read-only. AIM does not create or publish tags.

Tag Manager does not replace your ad accounts or the Meta Pixel. Those stay separate connections.

At a glance

Time: about 20 minutes for a new container, or 5 minutes if one is already live.
Access you need: at least Read on the container.
What AIM can do: read containers, tags, and triggers, and see whether changes are still unpublished.
What AIM cannot do: create, edit, or publish tags.

Before you start

A Google account that can view the container.
Access to the website so you can add the container snippet, or a developer who can.
The Measurement ID from Google Analytics, if that tag should live in this container.
In AIM, the Owner, Admin, or Marketer role on the workspace.

Set up Google Tag Manager

Open tagmanager.google.com and sign in.
Create an account named after the business, then create a Web container. The container ID looks like GTM-XXXX.
Install both snippets Google gives you: one as high as possible in <head>, and the other right after the opening <body> tag. A container that is not on the site has nothing for the agents to check.
Add the tags you rely on. For most sites that is a Google tag with your GA4 Measurement ID. Add a Meta Pixel tag here only if that is how you already install the Pixel. You still connect the Meta Pixel in AIM separately.
Use Preview to confirm the tags fire on the pages that matter, especially the thank-you or purchase page.
Click Submit and publish a version. Unpublished tags do not run on your live site.
If a teammate will connect AIM, give their Google user at least Read access on the container. They do not need Publish.

Connect Google Tag Manager with AIM's AI agents

Sign in to AIM and open Integrations, then Google Tag Manager.
Click Connect Google and approve read-only Tag Manager access.
Sign in with the Google user that can view the container.
Choose the container for this workspace.
When the badge says Active, the agents can read it.

What happens after you connect

Here is what AIM does with the connection, in plain terms.

Your access is stored privately. Google gives AIM a read-only access grant, not your password. AIM keeps it encrypted, uses it only for this workspace, and deletes it from AIM when you disconnect.
The agents check measurement before spend. Before Campaign Planner recommends a new paid channel, or Performance Optimizer suggests more budget, they check that the tags behind your conversion numbers exist and are published.
Unpublished changes are flagged, not published. If your container has changes that were never published, AIM tells you. Publishing stays your decision, inside Tag Manager.
Gaps show up in plain language. A missing conversion tag appears in your report as a measurement gap, with what to fix. You will not see raw tag configuration.
Everything is logged. The Agent work on Google Tag Manager list on the integration page records every time an agent read from this container.

Which AI agents use this connection

Analyst & Reporter checks that conversion tags are installed before it treats a conversion number as trustworthy.
SEO & Discovery uses the container when it reviews how the site is measured.
Performance Optimizer looks for a measurement gap before it recommends more spend.
Campaign Planner checks the container before it recommends a new paid channel.

None of them can create, edit, or publish tags.

If something looks wrong

The container is not in the list. The Google user you signed in with has no access to it. Add Read access in Tag Manager, then disconnect and connect again.
Choose an account. You signed in but have not picked a container yet.
Sign in again or Expired. Google ended the access grant. Click Connect Google again.
Needs attention. AIM could not read the container. Open the Tag Manager page in AIM to see the reason.
The agents say a tag is missing, but you added it. Check that you clicked Submit and published the version. Preview-only changes do not count.

What stays in your control

Disconnecting in AIM stops the checks and removes AIM's access grant. Your published container keeps running exactly as before. To revoke access on Google's side too, remove AIM under Third-party apps & services in your Google Account.

Keep Google Ads and the Meta Pixel connected on their own. Tag Manager tells the agents the tags exist. Those connections are where the agents prepare ads and read results.

Still need help setting this up?

If Preview shows no tags, or the container is missing after you sign in, contact the AIM team. Say you are connecting Google Tag Manager and include the container ID (GTM-). We will help you finish the setup.