Container audits · conversion monitoring · governed changes
For marketing leaders whose Google Tag Manager container is a black box run through someone else’s ticket queue. Project5 audits what is in there, tells you the morning a conversion tag stops firing, and makes every change reversible.
The interface is a sentence — audit this container, did checkout events drop last week? — and 38 governed tools do the work, every write fenced to containers you name.
The problem
GTM is where marketing intent meets engineering reality, and in most companies nobody owns that seam. The CMO can’t read the container, the devs don’t care what’s in it, and the agency that set it up left eighteen months ago. Five bills arrive in the post.
What you get
Not a dashboard to log into. Three deliverables that land where you already work, each one aimed at a bill above.
01 / The Audit
Seven categories against any live container — zombie tags, duplicate triggers, consent posture, performance weight, naming rot, version hygiene, orphaned entities. Client-ready, ranked fixes first, written for the person who approves the work rather than the person who built it.
KillsContainer rot, and the page-speed tax it has been quietly charging you.
02 / The Health Check
Daily verification, backed by the GA4 API, that your key events are still breathing. A flatline or a step-change surfaces as a finding the next morning — not as a gap somebody notices at quarter close.
KillsSilent data death, in a day instead of a quarter.
03 / Drift Watch
Every readable container snapshotted on a schedule and diffed against the last known good. Changes arrive in plain English — tag modified: firing triggers changed — so “who changed what, and when” stops being archaeology.
KillsZero change visibility, including the changes you made yourself.
Read-only. Name a container, get the scored report back.
How it works
Project5 is an MCP server, so there is no dashboard to learn and no console to log into. The interface is the conversation you are already having.
No syntax to get right, no permissions dance, no ticket.
Claude Code holds Project5’s 38 governed tools and picks the ones the job needs — reading the container, writing the entity, publishing the version, reading GA4 back. You see the reasoning as it goes.
Mutations land as container versions with a journal entry attached. There is finally an answer to “who changed what, and when” that isn’t archaeology.
Roll back to the version before that. The publish reverses, and the reversal is journaled too. That insurance is what makes delegating the container safe in the first place.
An allowlist names the containers automation may touch. Anything outside it fails closed — not a warning to click past, a refusal. Read access and write access are not the same grant.
Proof
We don’t sell tag hygiene we haven’t lived. Everything on this list is visible from where you are standing:
The product caught its owner
On 2026-08-08, drift watch read a GA4 tag we had created hours earlier and reported it back to us: added — fires on all pages, no consent settings declared. We declared them and republished. The next run narrated that fix too. We would rather show you that than a testimonial.
The loop is verified live, end to end:
tag authored published fired in a real browser numbers read back via API
Start here
Send one email naming the container you want read. You get the scored report back — the same one linked above, against your own tags. Read-only: nothing is written to your container unless you later name it on the allowlist yourself.
No form to fill in, no call to book, and no third-party processor collecting your details on the way — an email is the whole funnel.