Have you been losing tracking accuracy because browser restrictions keep blocking your tags? Many businesses face this exact problem when relying on client-side tracking alone. The good news is that a proper server-side setup solves most of these issues by routing your data through a secure server container instead of the browser.
This blog walks you through the complete server-side setup process using Google Tag Manager (GTM) and Seers. You will learn how to create a server container, link it to your web container, configure GA4, and verify that everything fires correctly. Each step is written in plain language so you can follow along without needing a developer.
By the end, your tracking events will flow through a server container that you fully control. This means better data accuracy, stronger performance, and fewer disruptions from ad blockers or browser privacy updates.
A server-side setup moves your tracking logic from the browser to a dedicated server container, giving you more control over data collection, improved privacy, better tracking accuracy, and stronger performance across platforms.
With client-side vs server-side tagging, the core difference is where your tags fire. Client-side tags run inside the visitor’s browser. Server-side tags run on a server that you own and manage.
Browser-based tags depend on the visitor’s device and browser settings. Ad blockers, cookie restrictions, and privacy features can all interfere. A server-side setup removes that dependency by processing events on your own infrastructure.
More businesses are switching from client-side to server-side tracking because browser privacy rules have tightened. Safari, Firefox, and Chrome now limit how long cookies last and what scripts can do. Server-side processing avoids these limits.
A server-side setup also reduces page load times. Fewer scripts running in the browser mean faster websites. That directly impacts bounce rates and conversions.
This guide suits website administrators, marketing teams, and business owners who use Google Tag Manager. You do not need coding experience. If you can navigate GTM and the Seers dashboard, you can complete this setup in under an hour.
Make sure you have these essentials ready before beginning your server-side setup.
You need an active GTM web container already installed on your website. This container is where your existing tags live, including any Google Analytics or consent tags.
Your web container must already include the Seers CMP tag. If you have not added it yet, install it first using the Seers GTM plugin guide. This tag handles user consent signals, which are essential for compliant tracking.
You will need access to your domain provider’s DNS settings during the custom domain step. This lets you point a subdomain to your server container for first-party data collection.
The first step of your server-side setup is confirming your existing GTM web container is ready.
Go to Google Tag Manager and sign in. On the Accounts page, find your account and select the Web Container for your domain. This opens the workspace where your tags live.
Click on the Tags section in the left sidebar. Look through your existing tags and confirm that the Seers CMP tag appears in the list. This tag is what sends consent signals alongside your tracking data.
Once you have confirmed the tag is present, close it and go back to your GTM Accounts page. You will create the server container from this screen in the next step.
Now you will create a new container specifically for server-side tagging inside GTM.
From the Accounts page, click the Create Container button. GTM will ask you to name your container and select a platform type.
Give the container a clear name that includes your domain and the word ‘server’ for easy identification. For example, ‘yoursite-server’. Then select Server as the target platform and click Create Container.
After creation, a pop-up appears asking how you want to provision the tagging server. Select ‘Manually provision tagging server’. GTM will display a Container Configuration ID. Copy this value because you will need it in the next step when setting up the container inside Seers.
With the Configuration ID copied, you will now set up your server container inside the Seers dashboard.
Log in to your Seers dashboard. From the left-hand menu, navigate to the Server-Side Tagging section. This is where you manage all your server containers.
Click the button to create a new server container. Give it a recognisable name, paste the Container Configuration ID you copied from GTM, and click Create Container.
Once the container is created, open the container dashboard. Go to the Domain section and copy the domain URL that Seers provides. You will paste this back into your GTM server container settings in the next step.
This step connects your GTM server container to the Seers infrastructure using the domain URL.
Go back to your GTM Server Container. Click on Admin in the top menu, then select Container Settings from the dropdown.
In the server container URL field, paste the domain URL you copied from Seers. Click Save to apply the settings.
Navigate to the Workspace tab and click Preview. This launches the server container in debug mode so you can confirm the connection is active. You should see the container loading without errors.
Setting up a custom domain is a critical part of your server-side setup for server-side tagging benefits like first-party cookie support.
Go back to your Seers container dashboard and find the Custom Domain section. Click Add Domain. Seers will generate DNS records that you need to add to your domain provider.
Copy the DNS records provided by Seers. Log in to your domain registrar (such as Cloudflare, GoDaddy, or Namecheap) and add these records to your DNS settings. The records typically include a CNAME entry pointing a subdomain to the Seers infrastructure.
Wait for DNS propagation, which usually takes a few minutes but can take up to 48 hours. Once propagated, return to Seers and click Verify. After verification, copy the Custom Domain URL. Then go back to your GTM Server Container, open Admin, select Container Settings, and replace the previous URL with your new Custom Domain URL. Select this custom domain in the Workspace tab.
Your server container now needs to receive events from your web container through a simple parameter.
Switch to your GTM Web Container. Go to Tags and find your Google Tag (sometimes called the GA4 Configuration tag). Open its configuration settings.
Inside the tag configuration, add a new parameter. Set the Parameter Name to server_container_url. Set the Value to your server container’s custom domain URL. This tells your web container to route events to the server container.
Save the tag changes. Click Submit and then Publish the container version. Your web container will now forward tracking events to the server container automatically.
This step brings your GA4 Measurement ID into the server container so it can process analytics events and improve conversion data accuracy.
In your GTM Web Container, go to Variables. Under User-Defined Variables, find your GA4 Measurement ID variable and copy its value. This is the ID that starts with ‘G-‘ followed by a string of characters.
Switch to your GTM Server Container. Navigate to Variables and create a new User-Defined Variable. Name it ‘GA4 Measurement ID’, set the Variable Type to Constant, and paste the Measurement ID as the value.
Click Save. This variable will be referenced by the client and tag configurations in the following steps.
A client in the server container listens for incoming requests and routes them to the right tags.
In your Server Container, go to the Clients section and click New. Name the client ‘GTM Web Container ‘, so it is easy to identify.
Select ‘Google Tag Manager: Web Container’ as the Client Type. This tells the server container to listen for events coming from your GTM web container.
In the Container ID field, select the GA4 Measurement ID variable you created earlier. Uncheck any region-specific settings unless they apply to your setup. Click Save to finish creating the client.
Now you will create a GA4 tag and set up a trigger so it fires on the correct events.
In the Server Container, go to Tags and click New. Name the tag ‘Google Analytics GA4’ and select ‘Google Analytics: GA4’ as the Tag Type. In the Tag Configuration, select the GA4 Measurement ID variable you created.
Click on Triggering and create a new trigger. Name it ‘GA4 All Events’ and set the Trigger Type to Custom. Choose ‘Some Events’ and configure it to fire when the Client Name equals ‘GA4’. This ensures the tag only fires for events coming through your GA4 client.
Save the tag with its trigger. Then click Preview from the Workspace to enter debug mode. This lets you verify the tag configuration before publishing.
The final step confirms everything works by testing both containers together.
Open your GTM Web Container and click Preview. A pop-up will ask for your website URL. Enter it and click Connect. Your website will open in a new browser tab with GTM debug mode active.
On your website, interact with the cookie banner that appears. Accept or customise cookie preferences as a normal visitor would. This action triggers consent signals and analytics events that flow from the web container to the server container. This is also where your cookie consent management platform plays its part.
Switch to the Server Container’s preview window. You should see the ‘Google Analytics GA4’ tag firing successfully. If the tag shows as fired, your server-side setup is complete. Events are now routed from the browser, through your web container, to the server container, and on to Google Analytics.
Even with a clear process, you might hit a few bumps during your server-side setup.
Check that you added the server_container_url parameter to the Google Tag in your web container. Confirm the URL matches your custom domain exactly. Also, verify that you published the web container changes after adding the parameter.
DNS propagation can take time. Wait at least 30 minutes before trying again. Double-check that the DNS records match what Seers provided. Some domain providers require you to remove trailing dots from CNAME entries.
Verify the trigger condition matches the client name exactly. The client name must equal ‘GA4’ for the trigger to activate. Also confirm the GA4 Measurement ID is correct. You can find the best server-side tagging solution troubleshooting tips in the Seers documentation.
Completing your server-side setup puts you in control of how your tracking data flows. By routing events through a server container instead of the browser, you gain better accuracy, faster page loads, and resilience against ad blockers. This guide covered every step from container creation to full verification. Your tracking is now more reliable and future-ready.
Seers makes server-side setup straightforward. You get a managed server container, custom domain support, built-in Google Consent Mode v2 compatibility, and a simple dashboard to manage it all. No complex cloud configurations needed.
START FREE TODAYA web container runs tags directly inside the visitor’s browser on your website. A server container runs on a separate server and processes the same events outside the browser environment. The web container sends data to the server container, which then forwards it to platforms like Google Analytics. This separation gives you more control over data processing, reduces browser load, and protects your tracking from browser-level restrictions.
Most website owners and marketers can complete this setup without developer support. The process involves navigating the GTM interface, pasting configuration IDs, and adding DNS records. If you are comfortable working inside Google Tag Manager and your domain registrar, you can handle every step yourself. The only technical part is adding DNS records, which your hosting provider can help with if needed.
The active configuration work takes around 30 to 45 minutes for someone following a step-by-step guide. However, DNS propagation after setting up the custom domain can add a waiting period of a few minutes up to 48 hours. Plan to complete the initial steps in one sitting and return for verification once DNS has propagated.
Your historical data in Google Analytics remains untouched. The server-side setup creates a new processing path for future events. Once active, new events route through the server container while your past data stays exactly as recorded. There is no migration of historical data involved in this process.
Yes. Once your server container is running, you can add tags for multiple advertising and analytics platforms. Google Ads, Meta, TikTok, Snapchat, LinkedIn, and other platforms all support server-side tag configurations inside GTM. Each platform requires its own tag and trigger setup within the server container.
Without a custom domain, your server container uses a default Seers domain. This means tracking requests come from a third-party domain rather than your own. Browsers treat third-party requests differently and may limit cookie lifetimes. Setting up a custom domain ensures first-party context, which extends cookie duration and improves data accuracy significantly.
Businesses of all sizes benefit from server-side tracking. Small and mid-sized websites often see the most improvement because they rely heavily on accurate data from limited traffic. The cost of running a server container through a managed provider like Seers is accessible for most budgets. It is not an enterprise-only solution by any measure.
GTM provides a built-in preview and debug mode for both web and server containers. After completing the setup, open both containers in preview mode and visit your website. Interact with the cookie banner and check the server container preview. If the GA4 tag shows as fired, your setup is working correctly, and events are flowing through the server.
Moving tags from the browser to a server container reduces the number of scripts running on your web pages. Fewer scripts mean faster page load times and better Core Web Vitals scores. Visitors experience a smoother, quicker website. This improvement is especially noticeable on pages that previously ran many third-party tracking scripts simultaneously.
The Seers CMP tag manages cookie consent signals in your web container. When a visitor accepts or declines cookies, this tag communicates those preferences. In a server-side setup, these consent signals travel with the tracking data to the server container. This ensures your server-side tags respect visitor consent choices and your tracking remains compliant with privacy regulations.
Rimsha ZafarRimsha is a Senior Content Writer at Seers AI with over 5 years of experience in advanced technologies and AI-driven tools. Her expertise as a research analyst shapes clear, thoughtful insights into responsible data use, trust, and future-facing technologies.
Take our Free Cookie Audit and find out
Join 50,000+ websites using Seers.Ai to turn compliance into trust, insights, & measurable business growth.
United Kingdom
24 Holborn Viaduct
London, EC1A 2BN
Get our monthly newsletter with insightful blogs and industry news
By clicking “Subcribe” I agree Terms and Conditions
Seers Group © 2026 All Rights Reserved
Terms of use | Privacy policy | Cookie Policy | Sitemap | Do Not Sell or Share My Personal Information.
