← Back to Blog

Maybe time to throw GTM and SS GTM in the BIN!

Maybe time to throw GTM and SS GTM in the BIN!

Updated: 20 June 2026

Picture the last time you opened GA4, Facebook Ads Manager, and your email platform side by side, and tried to make the numbers agree.

They didn’t.

GA4 said one thing. Facebook said another. Your booking system or checkout said something different again. And somewhere in the gap between those three screens, you were quietly making decisions about where to spend next month’s budget — based on numbers that don’t actually reconcile.

You’re not bad at your job. You’re not missing a setting. You’re running a tracking stack that was designed to leak.

Let that sink in.

The Game of Telephone Nobody Asked to Play

Here’s the thing about Google Tag Manager (GTM) and server-side GTM (SSGTM): they’re genuinely powerful tools. We’re not here to tell you they don’t work. We’re here to tell you what they cost — and it’s far more than the line item on your invoice.

Imagine your website data is a parcel you need delivered. GTM is the courier who picks it up and drops it at your marketing platforms. SSGTM adds an armoured truck for the middle leg of the journey. Sounds safer, right?

But every handoff is a chance for the parcel to get lost, dented, or quietly opened along the way. A developer makes one small change. An ad blocker swallows a tag. A privacy-first browser like Brave or Safari quietly refuses to play along.

The result? Industry data consistently shows client-side tracking losing 30–44% of events before they ever reach your reports. GA4 alone can under-report by roughly 44% once ad blockers and browser restrictions take their cut.

Translation: nearly half your marketing reality is missing — and you’re optimising against the half that survived.

The Bill You Don’t See on the Invoice

The data loss is the headline. The hidden cost is the small print.

Running GTM and SSGTM properly isn’t a “set it and forget it” affair. It needs care and feeding:

  • Consulting fees to get it configured and keep it sane.
  • Developer time for the inevitable debugging sessions when a tag silently stops firing.
  • Ongoing maintenance as privacy rules shift and platforms change their APIs again.

A conservative estimate — $100/month for support, $100/month for developer time — already lands you at $2,400 a year. And that’s the gentle version. Add a booking engine, a membership flow, or a checkout with real complexity, and those numbers climb fast.

We’ve watched marketers make the jump to server-side expecting relief, only to find a new set of headaches: more moving parts, more places to break, and a learning curve so steep it needs its own consultant. It’s a common story. It might even be yours.

So here’s the question we think is worth asking.

The question isn’t “How do I get better at GTM?”

The question is “Why am I renting this complexity at all?”

Enter inPIPE and the Transmute Engine

What if you could capture your marketing data and send it straight to where it needs to go — clean, complete, and without the tangled middle layer?

That’s exactly what we built.

The Transmute Engine™ is our WordPress server-side tracking solution. It captures events from your site and routes them to GA4, Facebook (Conversions API), Google Ads, BigQuery, Klaviyo and more — all at once, all server-side, all bypassing the ad blockers and browser limits that are quietly bleeding your data dry.

The data capture point is inPIPE, our purpose-built WordPress plugin. It’s not a generic tracker bolted onto WordPress as an afterthought — it’s built from WordPress, for WordPress. Install it, connect your destinations, and your events flow cleanly to every platform that matters. No GTM expertise required. No armoured trucks. No game of telephone.

And here’s the part most tracking vendors won’t tell you: your raw event data lands in YOUR BigQuery warehouse. Not sampled. Not aggregated. Not locked behind someone else’s rules. Every single event, individually, owned by you — forever.

These are your Data Trees (a term we coined): plant clean data today, harvest years of insight later. You can’t backfill the data you never collected, so the businesses planting now are the ones who’ll have something to harvest when AI comes hungry.

But What About the Tricky 5%?

Now, let’s be honest — because honesty is rather the point of this whole article.

The Transmute Engine solves 90 to 95% of all server-side tracking problems straight out of the gate. For the vast majority of WordPress and WooCommerce sites, that’s the entire job done. Clean data in, clean data out, nothing left on the table.

But every so often, there’s an edge case. A booking engine with its own quirks. A third-party system that speaks a slightly different dialect. A handoff between two platforms that don’t naturally talk to each other. That awkward last 5%.

The old answer to that 5% was to reach for GTM — and re-introduce every problem we’ve just spent this article describing. More complexity. More cost. More leakage.

We have a better answer.

The Custom Plugin: Cheap, Owned, and Built for You

Here’s the twist that changes everything.

AI has quietly demolished the economics of custom software. The custom plugin that used to mean weeks of developer time and thousands of dollars? It can now be produced in a few hours for a few hundred dollars.

So for that final 5% — the booking engines, the edge cases, the systems that need a bespoke bridge — we don’t patch over it with GTM. We build a small, dedicated custom plugin that sits between your booking system and the Transmute Engine, managing the data interface so the two systems are perfectly aligned.

We’ve already done this for clients. A booking engine that wasn’t natively handing off its conversion data? A purpose-built plugin captures it, shapes it, and feeds it straight into the Transmute Engine — clean and complete. The awkward handoff disappears.

And the benefits stack up beautifully:

  • It’s genuinely cheap. Hours of work and a few hundred dollars, not weeks and thousands. The old maths simply doesn’t apply anymore.
  • It solves the tracking problem completely. That stubborn 5% becomes part of the 100%.
  • It brings ownership back to your site. You’re not renting GTM’s complexity. You’re not dependent on a third-party tag manager. The plugin lives on your WordPress site, under your control. You own the whole pipeline, end to end.

We can build these plugins for clients – often at a fixed price.

And now for the best bit.

You Can Keep It Alive with Claude Code

A custom plugin used to carry a quiet anxiety: who maintains it? What happens when a platform changes its API, or a security advisory drops, six months after the developer who built it has moved on?

That anxiety is gone too.

With Claude Code, you — or we — can keep your custom plugin continuously up to date. Check it for security issues. Patch it when a destination changes its requirements. Audit the code, harden it, extend it. The maintenance that once required a developer on retainer is now something you can run yourself, on demand, whenever you need it.

Translation: a custom plugin is no longer a liability with an expiry date. It’s a living, owned, maintainable asset that sits on your site and does exactly one job perfectly — and keeps doing it.

That’s a complete reversal of the old trade-off. You used to choose between cheap-but-leaky (client-side), powerful-but-painful (GTM/SSGTM), or bespoke-but-ruinously-expensive (custom development).

Now you can have owned, clean, complete, and affordable — all at once.

Taking Charge of Your Data

The future of tracking isn’t more layers. It’s fewer. As privacy rules tighten and browsers keep clamping down, the old stack only gets more brittle and more expensive. The way forward is simplicity, ownership, and data you actually control.

Here’s where to start:

  • Take an honest look at your current tracking. Where do you suspect you’re losing data? Where do GA4, your ad platforms, and your back-end refuse to agree?
  • Calculate the real cost of what you’re running now — consultants, developer hours, and the maintenance treadmill included.
  • Identify your edge cases. Is there a booking engine or third-party system that never quite hands off cleanly? That’s your 5%.
  • Try a test run. Put the Transmute Engine to work on the 90–95%, and let a cheap, owned custom plugin mop up the rest.

You don’t need to live with data that plays hide-and-seek. And you certainly don’t need to keep paying GTM rent to do it.

Maybe it really is time to throw GTM and SSGTM in the bin.


Stop renting complexity. Start owning your data — all of it.


P.S. Curious how the data actually gets captured in the first place? Meet the plugin that started it all in We Created a Pipe You’ll Never Smoke — the inPIPE story, in plain English.

P.P.S. Wondering why clean first-party data matters so much right now? Who Stole AI’s Dinner? explains what happens when hungry AI systems arrive to find empty plates — and how your Data Trees keep them fed.