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

How to Connect Codex to GTM (Google Tag Manager)

Short answer

To connect Codex to GTM, connect Google Tag Manager in LoomaScale, add the GTM HTTP MCP endpoint, and complete codex mcp login. Check /mcp in your Codex session, then list and select a container. Codex can compare repository event code with container configuration before you decide on a tracking fix.

Tracking bugs often sit between website code and Tag Manager configuration. Connecting Codex to GTM lets one investigation inspect both the repository's dataLayer calls and the container's triggers. This guide uses a source-specific MCP server so your session can retrieve the actual configuration while you inspect the relevant code.

What do you need before connecting?

Use an installed Codex CLI with remote HTTP MCP and OAuth support. Run the setup on the same Codex host where you will use the tools. A local CLI configuration does not by itself configure a separate cloud task. You need no Google service-account JSON or API key for this hosted OAuth 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 Codex 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. Add the source-specific MCP server to Codex

Run these commands in your terminal. The first saves the remote server and the second starts browser authorization. The server name is specific to this Google source, so another source can be added without replacing it.

codex mcp add loomascale-gtm --url https://api.loomascale.com/mcp/gtm
codex mcp login loomascale-gtm

3. Finish OAuth and check the active Codex connection

Complete LoomaScale authorization in the browser using the account with your Google connection, then return to the terminal. Run codex mcp list to check the saved server. Start or reopen a Codex session and use /mcp to inspect its active tools. A saved entry is configuration evidence; the account lookup below verifies data access. Codex's supported local clients share MCP configuration for the same host. Consult OpenAI's current documentation for your desktop or IDE surface; do not assume a different host inherited your login.

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 compare dataLayer events with GTM triggers in Codex?

Start with a known user action, such as a completed lead form. Identify its dataLayer event name and payload in code, then retrieve the published GTM triggers and the tags they fire. Match exact spelling and required fields. Inspect a named draft workspace separately if it contains a proposed correction.

Use LoomaScale and the GTM container I selected. Read this repository's dataLayer event for successful lead submissions without editing files. Retrieve the published tags, triggers and variables for that event. Compare exact event names, conditions and required payload fields. List mismatches supported by code or container data, and browser tests needed to confirm behavior. Do not modify files, edit GTM or publish.

A matching event name does not establish that the payload arrives at the right moment or with the expected consent state. Codex should identify what static code and container inspection can establish, then provide a specific browser test. If the proposed fix changes a shared variable, review every dependent tag before deciding where to implement it.

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 Codex 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 authorization is missing, run codex mcp login loomascale-gtm again. If the entry is configured but absent in the active session, restart that session and inspect /mcp. Check the URL and host if the tools still do not load. The main LoomaScale plugin and the service-specific server are alternative connections; installing both can expose duplicate tool sets.

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 Codex

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

Can Codex compare my dataLayer code with live GTM configuration?

Yes, when Codex can read the repository and its LoomaScale GTM connection can read the selected container. Ask explicitly for the published version and exact event names. Static comparison identifies mismatches; verifying actual runtime firing still requires a browser or Tag Assistant test.

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.

Do I need an OpenAI API key or a Google service account?

This hosted MCP setup uses your existing Codex client and a browser OAuth connection to LoomaScale. It does not require copying an OpenAI API key or a Google service-account JSON file into the MCP configuration. Your Codex access and the connected Google account's permissions still apply.

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 Codex

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