Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Google Tag Manager API

    1

    Audit and safely edit GTM tags, triggers, variables and versions through the official API

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Google Tag Manager API

    Google Tag Manager API

    Example session with this skill installed

    Audit the tracking setup in our website's GTM container: what fires, on which triggers, anything unused or risky, and what was published most recently.

    • Read your context and instructions
    • Compiled the google tag manager

    Summary

    Read the

    Default Workspace of the website container (GTM-52SD••••):

    15 tags, 8 triggers, 0 user-defined variables, 12 published versions. Nothing was changed.

    Tags by platform

    PlatformTagsFires on
    GA4ga4.config + 8 event tags (contact_form, contact_phone, contact_zalo, contact_facebook, contact_whatsapp, n8n_template_copied, n8n_template_downloaded, website_funnel_events)Config on all pages; events on matching dataLayer custom events
    Meta Pixelmeta.config, meta.lead, meta.contact (Custom HTML)Config on all pages; lead on contact_form; contact on 4 contact events
    OpenAI conversionsopenai.config, openai.lead_created (Custom HTML)Config on all pages; lead on contact_form
    Microsoft Clarityclarity.config (community template)All pages

    Triggers

    All 8 triggers are customEvent triggers named event.*, and

    every trigger is used by at least one tag. Naming is consistent (platform.event for tags, event.name for triggers).

    Findings

    Measurement ID is hardcoded in all 8 GA4 event tags (measurementIdOverride) and there are no user-defined variables. Move it into one Constant variable so a property change is a one-line edit.
    2.

    Consent is "not set" on all 13 GA4 and Custom HTML tags. If you serve visitors in consent-regulated regions, configure consent mode or per-tag consent checks before these fire.
    3.

    Event parameters are uneven. Contact events send parameters (contact_form sends 3), but n8n_template_copied and n8n_template_downloaded send none, so you can't tell which template was used. Add a template_id parameter.
    4.

    One form submit fires three platforms (ga4.contact_form, meta.lead, openai.lead_created). Good for attribution; make sure they share a dedup event ID (version 11 notes "OpenAI CAPI dedup event ID", so this was addressed for OpenAI).
    5.

    Latest versions: v11 "OpenAI CAPI dedup event ID" (14 tags), v12 "WhatsApp contact tracking" (15 tags). The workspace has no unpublished changes.

    Next: I can draft the Constant variable and template_id parameters in the workspace as a dry run for your review.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Let your agent audit and maintain Google Tag Manager containers through the official GTM API v2, without clicking through the GTM UI.

    What it does

    • Lists accounts, containers, workspaces, tags, triggers, variables, folders, templates, environments, versions, and user permissions
    • Creates and updates workspace resources (tags, triggers, variables)
    • Syncs workspaces, creates container versions, and publishes versions
    • Raw REST requests for anything else

    Built-in safety

    • Edits happen in a workspace, never directly in the live container
    • Writes need --confirm-write; deletes also need --confirm-delete; --dry-run previews every change
    • Supports GTM's fingerprint concurrency check so the agent doesn't overwrite someone else's edit
    • Publishing is a separate, explicit step that the skill tells the agent to confirm with you
    • Dependency-free Node.js CLI; Never prints access tokens, refresh tokens, or credential contents, and never accepts tokens as command-line arguments.

    Ideal for tracking audits, consistent naming across many containers, adding GA4 or ads conversion events, and documenting what's actually live.


    Built and maintained by LaPage Digital: websites, automation, and AI operations for growing businesses.

    Needs a one-time Google login with Tag Manager scopes. Only resource-relative API paths are accepted, not arbitrary URLs. Writes and publishing need --confirm-write after your approval.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 22 days ago

    Requires

    Googleapis
    Node.js 20+
    Google account
    gcloud CLI
    Node.js

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Environment Variables

    Allowed Hosts

    tagmanager.googleapis.com
    oauth2.googleapis.com

    Network: only tagmanager.googleapis.com (GTM API v2) and oauth2.googleapis.com (token exchange). Credentials: a one-time gcloud application-default login with Tag Manager scopes (exact command in the skill), no keys to paste; optional environment variables GOOGLE_APPLICATION_CREDENTIALS, GTM_ACCESS_TOKEN, GTM_SCOPES. Reads are unrestricted; workspace edits, version creation, and publishing are blocked unless the agent passes --confirm-write after your approval.

    Listed23 days ago

    What's inside

    Frequently Asked Questions

    Only if you approve it. Edits happen in a workspace, and publishing a version is a separate step that needs --confirm-write.

    Yes. The GTM API treats web and server containers the same way; the skill works with both.

    The CLI supports GTM's fingerprint check, so an update fails instead of silently overwriting a newer change.

    New in Marketing & SEO