ChatGPT Plugin

HYPD.AI for Tag Manager

Connect Google Tag Manager

Brand: HYPD

Category: Marketing
Primary Subcategory: Pending

Integration details

Description

HYPD.AI for Tag Manager brings data from authorized Google Tag Manager accounts into ChatGPT, helping marketers, agencies, analytics teams, ecommerce teams, and developers understand how tracking is configured, troubleshoot implementation problems, compare versions, and make controlled changes. Use it to: • Discover the Google Tag Manager accounts and containers available to you, then select the correct container before beginning an audit or implementation task. • List container workspaces and inspect complete snapshots of their tags, triggers, and variables to understand the current tracking architecture. • Open individual tags, triggers, and variables in full to examine configuration details, firing conditions, dependencies, and naming conventions. • Audit measurement setups for missing, duplicated, outdated, or potentially misconfigured components, including tags and triggers associated with GA4, Google Ads conversions, consent management, and other marketing or analytics platforms. • Find overly broad or restrictive firing conditions, inconsistent naming, unnecessary duplication, orphaned variables, and other configuration risks that can affect data quality. • Review the currently published container version and compare historical versions to understand exactly what changed, identify possible regressions, and prepare clear release notes. • Plan tracking implementations conversationally and create drafts for new or replacement tags, triggers, and variables without immediately changing the container. • Review proposed changes before they are applied, including the affected entities, configuration, intended outcome, and implementation reasoning. • Create restorable container versions from approved workspace changes so each implementation has a documented release point. • Publish an approved container version through a separate confirmation step, keeping workspace changes and live-site publication under distinct controls. • Produce tracking audits, implementation plans, QA checklists, change summaries, and stakeholder-friendly explanations without manually documenting the entire container. HYPD.AI only accesses accounts and containers available through the connected user. Reading, auditing, and analysis do not modify Google Tag Manager. Changes follow a guarded workflow: HYPD.AI prepares a draft, shows the proposed change for review, requires explicit approval, and only then applies it. Publishing a version requires a separate approval. HYPD.AI cannot bypass Google Tag Manager permissions, change user access, delete containers, or silently apply unapproved changes. Users should validate changes with Google Tag Manager’s Preview and Debug tools before publishing and remain responsible for deciding when a version is ready to go live.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Marketing
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: HYPD
Access: Account required
First tracked: 2026-10-15
Tool count: 14
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce HYPD.AI for Tag Manager has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

14 tools agents can invoke

Performs one approved Change Draft against Google Tag Manager: writes the entity into its workspace, creates the version, or publishes it — whichever the draft recorded. Each draft applies once; a failed or uncertain apply is closed, never retried blindly (duplicate tags and double publishes come from retries). For entity writes, relay result.droppedFields verbatim; never claim discarded fields were applied.
gtm_apply_change_draft
Records the user's explicit approval of one Change Draft, in their own words, after you showed them the current and proposed state and the reasoning. Only an approved draft can be applied. Never paraphrase the confirmation or supply it on the user's behalf.
gtm_approve_change_draft
What changed between two versions of a container: tags, triggers and variables added, removed or modified, computed server-side so a 200-tag container does not have to be diffed by hand. The tool for 'what did the last release change?' and for verifying a rollback target.
gtm_compare_versions
Records a Change Draft that, once approved and applied, snapshots one workspace into a new container version — Tag Manager's equivalent of a commit. Nothing goes live: publishing that version is its own draft. Name and notes become the container's changelog, so say what changed and why.
gtm_draft_version_create
Records a create/update of one tag, trigger or variable as a Change Draft; nothing is written to Google. Updates capture the current entity and fingerprint. Show current/proposed and reasoning, get the user's explicit yes, then call gtm_approve_change_draft with their exact reply, then gtm_apply_change_draft. Apply writes only to the workspace. After a stale-fingerprint apply failure, re-read gtm_get_entity and create a new draft without supersedes_draft_id; get fresh approval, never retry the old draft. Inspect result.droppedFields and report discarded fields. Version creation snapshots the workspace; a separately approved publish makes it live. No delete operation. Drafts expire after 24 hours.
gtm_draft_entity_change
Records a Change Draft that, once approved and applied, makes one container version LIVE on the user's site — the only gtm_* step with visitor-facing effect. Tell the user exactly which version goes live and that the previous one stays restorable by publishing it again, and get an explicit yes before approving.
gtm_draft_version_publish
Builds the HYPD app link where the container's owner turns on Actions — the way out of a 'changes not enabled' refusal from a gtm_draft_* tool. Nothing is changed by calling it: give the user the link, stop, and retry the draft once they say it is done.
gtm_get_enable_changes_link
Lists the user's messages from the HYPD team, newest first: announcements, plan news and actions needed, each with its text, an optional link, and whether it is unread. Use it when the user asks about messages or news from HYPD, or a tool result mentions unread HYPD inbox messages. Listing does not mark anything read; the user does that by opening inbox_url.
hypd_list_inbox_messages
The user's connected Tag Manager containers across their Google logins — each row carries the numeric account_id and container_id every other gtm_* tool takes (the GTM-XXXXXXX public id is display-only). Start here in every conversation: an empty list means the user has not connected Google Tag Manager yet — tell them to reconnect this connector from their MCP client's settings and complete its connect step — and plan_notice explains containers held back by the user's plan.
gtm_list_containers
The container's version history, newest first: id, name, notes, who created it and when. Pick two ids here for gtm_compare_versions, or the previous version to roll back to via a publish draft.
gtm_list_versions
The workspaces of one container — every container has a Default Workspace, and teams add more for parallel work. A workspace_id is required before reading a snapshot, inspecting an entity, or drafting a change; ask the user which one when several exist.
gtm_list_workspaces
Every tag, trigger and variable in one workspace, as Google returns them — the full picture of what the container does before a change is proposed. Served from a short cache when the same workspace was read moments ago (from_cache says so). Audit questions ('is GA4 firing on every page?', 'what does this tag depend on?') start here.
gtm_get_container_snapshot
One entity in full, exactly as the Tag Manager API holds it — parameters, firing and blocking triggers, notes, fingerprint. Read this before proposing an update: an update replaces the whole entity, so the proposal starts from this shape.
gtm_get_entity
The version currently published to the user's site, with its tags, triggers and variables — what visitors actually get, as opposed to a workspace draft. live is false for a container that has never been published.
gtm_get_live_version

FAQs