Keeping the Docker Image Up to Date in Server-side GTM: What Should GA4 and GTM Practitioners Know?
Keeping the Docker Image Up to Date in Server-side GTM: What Should GA4 and GTM Practitioners Know?

Server-side Google Tag Manager has become one of the topics we encounter more and more in digital measurement in recent years. Server-side GTM is becoming widespread especially among brands that want to manage the flow of events to GA4, Google Ads, Floodlight or other platforms through a more controlled setup.
However, server-side GTM works somewhat differently from the classic web GTM container.
In a web container, we usually deal with tags, triggers, variables, the dataLayer and event setups. In server-side GTM, a server side also comes into play. This setup can run on Cloud Run, App Engine, Stape or another hosting infrastructure.
That is why, once server-side GTM is set up, looking only at the tag setup in the GTM interface may not always be enough. You also need to make sure the tagging server running on the infrastructure side is up to date and healthy.
One of the technical topics that comes up at this point is keeping the Docker image up to date.
What Does the Docker Image Mean for Us?
Simply put, we can think of the Docker image as the technical package that makes server-side GTM run.
Measurement requests from a website or app first reach server-side GTM. This server container processes incoming requests and routes them to the relevant platforms. The application layer behind this setup runs on the tagging server Docker image published by Google.
As people working on GA4/GTM, we usually don't update this image directly. Updating and deployment generally fall to software, cloud or DevOps teams.
But that doesn't mean the topic is outside our remit.
Because if server-side GTM is part of the measurement flow, a problem here can affect GA4 events, Google Ads conversions or other integrations.
So what matters on our side is this:
Not updating the Docker image technically, but being able to check the current state, pass it on correctly to the relevant team when needed, and test the event flow after the update.
Can We Check the Current Version in GTM?
Yes. If server-side GTM is in use, the current tagging server image version can be checked in the GTM interface.
To do this, open the server container, not the web container.
The path to follow:
Google Tag Manager > Server container > Admin > Container settings
The current tagging server image version can be seen here. Google also publishes server-side tagging Docker image versions on its official release notes page.
So the first check we can do is quite simple:
- Is server-side GTM in use?
- Do we have access to the server container?
- Which image version is shown under Admin > Container settings?
- Is there an update warning in the GTM interface?
- Is there a gap between it and the latest version on Google's release notes page?
These checks let us understand the current state without deploying anything ourselves.
So What Happens If an Update Is Needed?
If the image in use is outdated, or a warning like “tagging server is out of date” appears in the GTM interface, it needs to be shared with the relevant technical team.
The wording matters here.
Instead of saying “we'll update the Docker image”, a more accurate way to put it is:
We checked the tagging server image version used for server-side GTM. There appears to be a gap between the current version and the latest version published by Google. Could you check whether an update is needed on Cloud Run / App Engine / the hosting in use?
This way, the topic is owned correctly and the technical responsibility is passed to the right team.
Because an image update may involve technical topics outside our day-to-day GTM work, such as Cloud Run revisions, service settings, environment variables, custom domains, scaling or routing.
Our Real Role Begins After the Update
Once the technical team has done the necessary check or update, the most critical part on our side is testing.
Because when server-side GTM is updated, what matters is not just that the service is running, but that the measurement flow continues as expected.
At this point, the following checks can be done:
- Open the GTM Server container in Preview mode.
- Send test events.
- Check whether requests are reaching the server container.
- See whether the relevant GA4 tags or vendor tags are firing.
- Validate events in GA4 DebugView or Realtime reports.
- Check for parameter loss in critical events such as purchase, add_to_cart, begin_checkout and generate_lead.
- Check transaction ID, value, currency, item details and consent parameters.
- Monitor event volume for a short period after go-live.
These tests help confirm not only that server-side GTM is technically up, but that it is also working correctly from an analytics perspective.
Why Does This Matter?
Keeping the Docker image up to date in server-side GTM may look like an overly technical topic at first glance. And it is. But for people working in digital analytics, ignoring it completely isn't right either.
Because if we use server-side GTM, the measurement flow is no longer just the tags in the web container. In between there is a server container, a hosting infrastructure it runs on, and the image version that setup uses.
So what matters for us is not taking on the technical operation, but being able to read the measurement infrastructure end to end.
If an event isn't reaching GA4, a conversion looks to be missing or there is a warning on the server-side GTM side, you need to know that this may stem not only from the tag setup but also from an update or service issue on the infrastructure side.
Quick Checklist
For projects using server-side GTM, a simple checklist on our side could look like this:
- Check whether server-side GTM is in use.
- Check whether you have access to the server container.
- Check the image version under Admin > Container settings.
- Look for an update warning in GTM.
- Compare with the latest version on Google's release notes page.
- If there is a gap or a warning, pass it on to the technical team.
- After the update, test the request flow with GTM Preview.
- Validate events via GA4 DebugView and Realtime.
- Check that there is no parameter loss in critical conversion events.
- Monitor event volume for a short period after go-live.
Keeping the Docker image up to date in server-side GTM may not be something we update directly. But knowing what this setup means, being able to check the current state in GTM and passing it on correctly to the technical team when needed is an important skill in digital analytics.
Because modern measurement is no longer just about setting up tags. GA4, GTM, consent, server-side setups, cloud infrastructure and data validation processes all work together.
That is why, in projects using server-side GTM, keeping the Docker image up to date is one of the topics we should at least be aware of and add to our regular checklist.
Let’s talk about this for your brand.
Write to us →