Container audit & cleanup
Every tag, trigger and variable reviewed: dead and duplicated ones removed, the rest named and documented, with workspaces, version notes and user permissions in order.
Analytics · Google Tag Manager
Goodish is a Google Tag Manager agency for teams whose tracking has grown messy or stopped matching the ads. We audit and rebuild GTM containers, deploy GA4 and ad-platform tags through a clean data layer, and move tracking server-side with Meta's Conversions API, Google's enhanced conversions and consent mode, so conversions survive cookie blockers.

Because containers grow by addition. Every campaign, agency and website release adds tags, nobody removes the old ones, and triggers tied to a button’s CSS class break silently when the site is redesigned. The result is duplicated conversions, missing events and ad platforms learning from the wrong signal.
The fix is structure rather than more tags: a data layer the developers own, one naming plan for events, workspaces and version notes, and a written record of what every tag is for. When the GA4 property itself needs restructuring, that is part of our GA4 consulting; both sit inside our wider analytics service.
Where your data goes first. With server-side tagging, the browser sends events to a tagging server you control, and that server passes them on to each platform. In practice it gives you:
For ATC Alert, a medical alert company, we introduced server-side tagging so that Google Ads (through Google Analytics) and the Meta pixel received accurate conversion data past common cookie blockers. The ATC Alert case study tells the rest.
Someone who checks the numbers after launch, not only the setup. A server container that is configured but never reconciled against the backend just moves the errors to a new place.
We compare platform conversions with the CRM or the shop after every change, and we document the result. For TMT Finance that discipline grew into 90+ tracked data points across GTM and GA4, Looker Studio dashboards per team and written documentation of everything tracked.
Every tag, trigger and variable reviewed: dead and duplicated ones removed, the rest named and documented, with workspaces, version notes and user permissions in order.
A data layer your developers can maintain and one naming plan for events, so GA4, the ad platforms and product analytics read the same actions.
GA4, Google Ads, Meta, LinkedIn, Microsoft Ads and other tags deployed through GTM, checked in preview mode before anything is published.
A server-side GTM container on your own subdomain as a first-party endpoint, feeding GA4, Meta's Conversions API and Google Ads enhanced conversions.
Google consent mode connected to your cookie banner, with every tag tested before and after the visitor's choice.
Purchase and lead events with transaction IDs that prevent double counting, and cross-domain tracking across checkout, booking or app subdomains.
Real clients, real numbers, straight from our client reports.
Medical alert systems · 2023 → 2024
A → G
Ad message variants tested
A/B-tested messaging that moved from the watch to the service, server-side tagging that feeds clean conversion data to Google and Meta, and Mailchimp emails that update themselves from Chargebee subscriptions.
TMT Finance Financial media & funding, United Kingdom · 2023 → today
−97%
cost per lead
Product analytics and UX forensics first, an onboarding flow redesigned on that data, and only then Google Ads relaunched with smart bidding fed by the new conversion data.
Onboarding software for financial advisors · 2020
Research and design guidelines, a fast WordPress site the team publishes to themselves, and tracking that joins the website (Google Tag Manager and Google Analytics) to in-app analytics in Mixpanel.
Working with Goodish was great. They fixed a goal tracking / data integrity issue that had several other experts stumped. I wouldn’t hesitate to work with them again in the future.
We open the container, GA4 and the ad accounts, compare what fires with what the platforms and your backend record, and write down every gap.
Data layer, tags and the server-side container built in a separate workspace, tested in preview, then published with version notes.
Conversions checked against the CRM or backend after launch, and a written record of every tag, trigger and event your team can maintain.
Scoped per setup: a single tag and a full monitoring system are very different jobs, so we quote after the free audit.
FAQ
It sets up and maintains the tags that send website behaviour to your analytics and ad platforms: GA4, Google Ads, Meta and the rest. Adding a tag is easy; the work is a data layer, triggers and naming that stay correct as the site changes, and conversions that match what your backend records.
Instead of every pixel loading in the visitor's browser, the browser sends one stream of events to a tagging server on your own subdomain, and that server forwards them to GA4, Meta's Conversions API and Google Ads. You decide what leaves, the endpoint is first-party, and conversions are less exposed to ad blockers and browser privacy features.
For most accounts, yes. We run both and deduplicate them with a shared event ID, so Meta gets the browser signal and the server signal without counting a conversion twice.
No, and it shouldn't. Consent mode and your cookie banner still decide what may be collected; server-side tagging makes what is collected more reliable and gives you control over what each platform receives.
Google Tag Manager decides which tags fire and what data they send; it stores nothing itself. GA4 is one of the destinations: it stores the data and reports on it. Most of our clients use both, with GA4 configured through GTM.
The first audit is free. Implementations and monitoring systems, including server-side tagging, are quoted on scope after it.
We’d like to use analytics and ad measurement (Google, Meta, LinkedIn) to see what works on this site. Nothing is set until you choose. Privacy notice