Meta Pixel
Back to Blog
Connection guide5 min readNov 12, 2026By Andrii Pasika· Founder, LoomaScale

How to Connect Claude to GTM (Google Tag Manager)

Short answer

To connect Claude to GTM, connect Google Tag Manager in LoomaScale and authorize the LoomaScale connector in Claude. Enable the connector in your conversation, list your containers, and select one by name and GTM ID. Ask Claude to distinguish the published version from draft workspace changes before reviewing tracking.

A Claude GTM connection is useful for turning a complicated container into a tracking explanation your team can review. Rather than guessing from tag names, ask Claude to retrieve the actual triggers, destinations and workspace status. The first useful result is an accurate map of what is live and what remains a draft.

What do you need before connecting?

Use Claude on the web or Claude Desktop with connector access allowed for your account. Organization controls may require an owner to add the connector before members connect individually. This guide covers Claude's connector interface; Claude Code's terminal configuration is a separate route.

  • A Google login that can read the intended Tag Manager container.
  • A LoomaScale account with Google Tag Manager connected separately from Analytics or Google Ads.
  • The container you want to inspect, plus a named workspace if you later request a draft change. Editing, creating versions and publishing require their corresponding Google permissions.

How do you connect Claude to GTM?

1. Connect GTM in LoomaScale

Create or sign in to your LoomaScale account, then open Connections. Choose Google Tag Manager, sign in with the Google email that has access to the required data, and review the requested permissions. Signing in to LoomaScale with Google is not a substitute for connecting this data source. You can connect this service without connecting an advertising account.

2. Connect the LoomaScale directory connector

Open LoomaScale in Claude's connector directory and choose Connect to Claude. Use the existing full connector for access to this Google service alongside your other connected sources. LoomaScale is listed in the directory; that listing should not be read as a claim that Anthropic verified its analysis.

3. Authorize LoomaScale and enable its tools

Sign in to the LoomaScale account that holds your Google connection and complete authorization. In Claude, open Customize → Connectors and confirm LoomaScale is connected. Enable it for your conversation through + → Connectors, then request an account lookup by name. For a service-specific custom connection, use + Add → Add custom connector, enter the endpoint below and complete the detected OAuth flow. Team and Enterprise owners manage organization-level connector availability.

4. Verify access with an actual account lookup

Use LoomaScale to call gtm_list_containers. Show each container's name, public GTM ID and account. Ask me which one to inspect. Read its published version and list its workspaces. Do not edit, create a version or publish anything.

Check that the response identifies your actual container, including its GTM- public ID. Distinguish the published version from each draft workspace before discussing a tracking issue. The container's API account and container IDs are different identifiers from its public GTM- ID; let the tools discover the required values. A successful inventory confirms access to configuration, not that a browser event fires correctly.

How do you review a GTM workspace with Claude?

Choose a named workspace after listing the available ones. Ask Claude to compare its changes with the published container and explain the intended behavior in plain language. Keep existing unrelated changes visible so a later container version does not accidentally bundle them into the release without review.

Use LoomaScale for the GTM container I selected. List its workspaces and ask me which one to review. Read that workspace's status, tags, triggers and variables. Explain each unpublished tracking change and any reported conflicts. Identify shared triggers or variables that could affect other tags. Separate confirmed configuration from questions requiring Tag Assistant. Do not edit, create a version or publish.

The result should name the selected workspace and preserve tag and trigger identities. If Claude proposes a fix, ask it to describe the current value, proposed value and affected dependencies before any write. Test the journey in Preview. A readable explanation supports review, but only a checked version and explicit publication make a draft live.

Which MCP endpoint does this guide use?

https://api.loomascale.com/mcp/gtm

The service-specific endpoint exposes GTM tools and LoomaScale account helpers. The full directory plugin or connector uses https://api.loomascale.com/mcp and can reach all sources you separately connect. Choose the full connection for work across services; use the specific endpoint when you want this source's tool set. An endpoint choice limits exposed tools, not the Google roles your login holds.

What can Claude read or change in GTM?

LoomaScale reads containers, tags, triggers, variables, workspaces, versions and tracking-audit findings. Where enabled and authorized, changes go into the workspace you select; creating a version and publishing it are separate operations. Review the exact version before approving publication. Configuration inspection cannot observe a visitor's browser or prove that consent and tags behave correctly on the site. Validate proposed changes in Tag Manager Preview and Tag Assistant before a live release.

Why is the connection or data missing?

If Claude does not call a tool, enable the connector for the conversation and name LoomaScale explicitly. If new tools are missing, open its connector page and use Refresh tools list; the Claude refresh guide shows the menu. A refreshed list cannot grant access to a missing Google property or bypass an organization restriction.

A missing container usually calls for checking the Google login, container access and Tag Manager connection. If discovery says accounts are still loading, retry after discovery finishes. If an audit describes different tags from the live site, check whether you requested the published version or a draft workspace. A write-permission error is separate from read access: check the relevant edit, version or publish permission and the feature's availability before reconnecting.

Related connection guides and official references

Use GTM in another assistant

Connect another Google source to Claude

Official setup references

Setup references checked on November 12, 2026. Menu labels and workspace policies can change; use the linked vendor guidance for your account. For LoomaScale's supported workflows, see the documentation hub.

FAQ

Why does Claude see a GTM fix that is not live on my site?

The fix may exist only in a draft workspace or unpublished version. Ask Claude to identify the source of each finding and read the container's published version separately. Workspace edits, creating a version and publishing that version are distinct steps.

Does connecting GTM automatically publish tracking changes?

No. Reading a container and running an audit publish nothing. Authorized edits are workspace changes; a version must be created and the specific version approved before publishing. Test tag behavior in Tag Manager Preview and Tag Assistant before a live release.

Is connecting Claude the same as configuring Claude Code?

This guide uses Claude's web or desktop connector interface. Claude Code can also use MCP tools, but its terminal configuration and authentication checks have their own setup. Use the dedicated Claude Code guide for a reproducible CLI connection and verify the source account there.

Who wrote this

Andrii Pasika, founder of LoomaScale

Andrii Pasika

Founder, LoomaScale

Andrii founded LoomaScale and wrote the Google Ads MCP server behind it. He runs his own campaigns through it, and mail to team@loomascale.com reaches him.

Connect GTM to Claude

Create your LoomaScale account, connect the Google source, and use the verification prompt above to retrieve your own account data.

Start with LoomaScale

Connect your assistant to your ad platform

LoomaScale runs inside the assistant you already use. Pick the pair you work with; each guide takes about five minutes.

ChatGPT
Google Ads

Manage Google Ads campaigns from ChatGPT: search terms, budgets and new campaigns, paused for your review. One-click install from ChatGPT's directory.

Read the integration
Claude
Google Ads

Manage Google Ads from Claude: audits, budget changes and new campaigns, every write inside the spend cap you set. Connect from Claude's directory.

Read the integration
Claude Code
Google Ads

Install the LoomaScale plugin in Claude Code with two commands and audit Google Ads from your terminal: search terms, budgets and pacing, with skills built in.

Read the integration
Codex
Google Ads

Install the LoomaScale plugin in OpenAI Codex with two commands and audit Google Ads from your terminal: search terms, budgets and conversion goals.

Read the integration
ChatGPT
Meta Ads

Manage Facebook and Instagram campaigns from ChatGPT: ad sets, budgets and creatives in one chat. The same one-click install.

Read the integration
Claude
Meta Ads

Manage Facebook and Instagram campaigns from Claude: audits, budget caps and new ad sets, inside the limits you set.

Read the integration
Claude Code
Meta Ads

Run Facebook and Instagram campaign reviews from Claude Code: the same plugin, one sign-in, and skills for waste audits, pacing and creative fatigue.

Read the integration
Codex
Meta Ads

Review Facebook and Instagram campaigns from OpenAI Codex: the same plugin and sign-in, with placement, age and lead-quality checks.

Read the integration
ChatGPT
TikTok Ads

Manage TikTok campaigns from ChatGPT: reports, video watch-through, audience breakdowns, and pauses, budgets and bids on request. The same one-click install.

Read the integration
Claude
TikTok Ads

Manage TikTok campaigns from Claude: audits, video and audience reports, and pauses, budgets and bids inside the spend cap you set.

Read the integration
Manus
Google Ads

Connect Manus to Google Ads through LoomaScale’s MCP server. Analyze campaigns, keywords and search terms, then request changes within your permissions and spend cap.

Read the integration
Slack
Google Ads

Ask Slackbot about Google Ads in any Slack DM: audits, search terms and pacing checks, with changes kept inside your spend cap. Install the app once per workspace.

Read the integration
Manus
Meta Ads

Connect Manus to Meta Ads through LoomaScale’s MCP server. Review Facebook and Instagram campaigns, ad sets, creatives and placements.

Read the integration
Slack
Meta Ads

Ask Slackbot about Facebook and Instagram campaigns in any Slack DM: delivery, pacing and ad-set spend, read live from Meta Ads.

Read the integration