Cogny Cloud · Google Tag Manager

Tracking debt, finally inventoried.

Cogny reads GTM and GA4 through the MCP, finds orphan tags, missing conversion events and version drift, and creates a ticket for each fix. You approve in tickets — Cogny ships the tag/trigger updates and version publishes through the GTM API.

❯ book a Cloud demo see how it replaces the manual flow →

❯

cogny --replaces

FLOW

Same outcome. Two very different processes.

How you do it today

Open GTM. Drill into tags, triggers, variables one folder at a time.
Cross-check tag fires against GA4 events.
Spot orphan tags, broken triggers, missing conversions.
Stage the changes. Publish a new version. Hope nothing breaks.
Forget you did this. Re-discover the same drift in 6 months.

How Cogny Cloud does it

Cogny connects to GTM + GA4 via MCP — one-time.
Pulls container + tag + trigger + variable + version reports on a schedule.
Finds insights: orphan tags, missing conversions, version drift, redundant tags.
Creates a ticket per proposed action.
You approve in tickets.
Cogny executes through the GTM API — tag/trigger updates, version publishes.
Watches whether the published change actually fired in GA4. Smarter every week.

❯

cogny --tickets

read + write

Cogny creates tickets AND executes the approved ones through the MCP. Each insight becomes one ticket — here are the kinds Cogny creates from Google Tag Manager:

Orphan-tag ticketTags configured but never firing — proposes a clean removal or fix to the trigger.

Missing-conversion ticketA new conversion event fires in GA4 but no GTM tag captures it for downstream tools.

Version-publish ticketApproved changes bundled into a workspace ready to publish — Cogny ships the version.

ExecutionCogny can update tags, triggers, variables and publish container versions through the GTM API after approval. Cogny does not author custom HTML / JavaScript tag bodies from scratch.

LearnsCogny watches whether each published change actually fires in GA4 and tunes its proposals — drift patterns that repeat get caught earlier next time.

❯

cogny --reads

DATA

The reports Cogny pulls on schedule for Google Tag Manager insights

Google Tag ManagerTags, Triggers, Variables, Versions

GA4Event firing + conversion data

Google AdsConversion-action overlap

Cogny memoryOrg context across weeks

❯

cogny --book

DEMO

Tell us your use case. Then book a 15-min Cloud demo.

❯

cogny --faq

ASK

The questions we usually get on the demo call

Does Cogny replace Google Tag Manager?

No. Cogny connects to Google Tag Manager and adds an AI analyst on top — you keep using Google Tag Manager for everything you do today.

Does Cogny make changes automatically?

No — Cogny creates a ticket for every proposed action, you approve in tickets, then Cogny executes the approved ticket through the Google Tag Manager MCP. Nothing ships without you signing off.

Does Cogny write copy or creative?

No. Cogny does not write ad copy, email bodies, post content, image creative or rewrite existing copy. Cogny’s execution is limited to structural changes — segments, tags, metadata, internal links, redirects, scheduling assets you’ve already drafted, status changes (pause/resume/archive), and code-level PRs via Cogny Code.

Does Cogny actually get smarter over time?

Yes. Every approval and rejection is a signal. Cogny tracks the outcome of each executed ticket (did the deal close, did the ranking recover, did the segment lift revenue) and tunes its proposals to your business — so noisy or irrelevant tickets fall off and the high-signal ones become the default.

❯