Tag Manager
×
Papercrane
Something changed in your GTM container. Nobody's sure what.
GTM's version list says tags changed. It doesn't say which fields, or across which of your containers. Papercrane's AI agent reads every container you connect, diffs each version, and builds a hosted audit trail your team can check before a launch.
Connect in about a minute with read access you approve on Google's consent screen. Free to connect and ask. Paid plans start when you publish a dashboard. See pricing
Every container, one feed
GTM keeps a version history inside each container, one login at a time, and shows you a change count, not a change. This is what actually changed, across every container the agent can see, on one page.
Change feed
Container
Version
Published
What changed
GA4 Configuration Tag
Purchase Conversion trigger
GTM shows this one container at a time, and a count, not a change. This is every container you connect, one feed, with the field that actually moved.
Where GTM audits get expensive
The container nobody remembers building
Tags accumulate for years: a pixel from a campaign that ended, a trigger for a page that no longer exists. Nobody deletes them, because nobody is sure what breaks if they do.
The client folder
An agency managing a dozen client containers checks each one by hand, one login at a time, with no single view of what shipped where this week.
The scramble before a launch
Someone has to confirm every tag still points at a page that exists and every conversion trigger still fires. GTM's own compare view checks one version, one item, inside the admin, at a time.
Ask what actually changed
What changed in the container since last Friday, and who published it?
Which tags are attached to a trigger that hasn't fired in months?
Which of my containers hasn't shipped a new version in six months?
What's different between this version and the one before the redesign?
Which tags still sit unpublished in a workspace?
Did last week's tag change land the same day my GA4 numbers moved?
Every answer comes back as a table or a chart on a live dashboard, not a version you click into one at a time.
Put the change next to the number
An audit answers what shipped. It can't tell you on its own whether that's why a metric moved, and neither can we by guessing. Connect GA4 or Cloudflare alongside Google Tag Manager and the agent puts your publish timeline next to the metric timeline on the same dashboard, so you can see what landed the same day instead of assuming.
Both timelines, side by side. No claim about which caused what.
Built by Papercrane's agent. Updates when you publish a new version.
1. Connect with the read access you approve on Google's consent screen
2. Ask a question
3. The agent reads your containers and versions and builds a hosted dashboard
4. It stays live, and updates when you publish
Read access only. Nothing changes in your containers, your tags, or your live site.
Three ways to know what's in your container
| The job | GTM's own version list | Manual export and git diff | GTM + Papercrane |
|---|---|---|---|
| See what changed in one publish | A change count; click each item to see it | A real diff, if you already run this pipeline | A real diff, rendered automatically |
| See changes across every container | One container, one login, at a time | Only if you script it yourself | One feed across every container you connect |
| Find tags nobody uses anymore | No built in report | Grep the export by hand | Flagged automatically, with the trigger it's attached to |
| Share the audit with a client or teammate | Give them container access | Send them the exported file | Send a link to a hosted dashboard |
| Check before a launch | Open the container and look, one item at a time | Run your export pipeline | Ask the agent, get an answer in minutes |
When you don't need us
If you manage one container and check the version list once a month, GTM's own history is right there and free; you don't need another login for that. If what you actually need is proof that a tag fires correctly on the live page, across thousands of URLs, on a schedule, that's a job for a scanner like ObservePoint or Tag Inspector: they crawl your site and watch execution, we read your container's configuration through Google's API, and those are different jobs done well by different tools. And if your team needs formal approval workflows and enterprise support built into the tag manager itself, GTM 360 or Tealium iQ are built for that layer, and we are not trying to be. Papercrane is worth connecting when you manage more than one container, or when the audit needs to live somewhere a teammate or a client can check it without a login.
Questions teams ask us
A tag change means something only next to a number. Most teams connect GA4 for what the tags measure, Cloudflare for what hit the edge before any tag fired, and Search Console for what Google indexed regardless of what's tracked.
Connect your containers, ask what actually changed, and check it before you publish the next one.
Free to connect and ask. Paid plans start at publishing. See pricing
Papercrane
Integrations: