Analytics advanced 60-90 minutes

How to Set Up Server-Side Tracking with Google Tag Manager

Learn how to bypass ad blockers and improve data accuracy by setting up a GTM Server container for your Australian business.

Emma 30 January 2026

In the world of Australian digital marketing, data privacy and accuracy are becoming increasingly difficult to balance. With the rise of ad blockers, Safari’s Intelligent Tracking Prevention (ITP), and evolving privacy regulations, traditional browser-side tracking is no longer enough to get a clear picture of your ROI.

Server-side tracking moves the data processing away from the user's browser and onto a secure server you control. This means faster website speeds, better data security, and more accurate conversion tracking for your Meta and Google Ads campaigns. For local businesses in Brisbane and across Australia, this is the gold standard for future-proofing your analytics.

Prerequisites

Before we begin, ensure you have the following:
  • An existing Google Tag Manager (Web) container installed on your site.
  • A Google Cloud Platform account (or a credit card ready to link for the server hosting).
  • Administrative access to your Domain Name Registrar (e.g., GoDaddy, VentraIP, or AU Domain Administration).
  • A basic understanding of how tags and triggers work in GTM.

---

Step 1: Create a New Server Container

First, you need a dedicated space for your server-side logic. Log in to your existing Google Tag Manager account.
  • Click on Admin in the top navigation bar.
  • In the 'Container' column, click the + (plus) icon to create a new container.
  • Name your container (e.g., "LMG Server Side").
  • Under 'Target Platform', select Server.
  • Click Create and accept the Terms of Service.

Step 2: Provision Your Tagging Server

Once the container is created, a dialogue box will appear asking how you want to set up your tagging server.
  • Select Automatically provision tagging server (this is the easiest route for small to medium businesses).
  • If you haven't linked a billing account, you will be prompted to create or select a Google Cloud Billing Account.
  • Google will set up a 'Standard' configuration. For most Australian SMEs, the free tier or low-cost entry tier is sufficient to start.
  • Screenshot Description: You should see a progress bar indicating that Google is "Provisioning the Cloud project and server-side container." This usually takes 2-5 minutes.

Step 3: Configure Your Custom Domain

By default, Google provides a URL like appspot.com. However, to truly benefit from first-party data (and bypass those pesky ad blockers), you need to use your own domain (e.g., metrics.yourbusiness.com.au).
  • In your Server Container, go to Admin > Container Settings.
  • Click Add URL.
  • Enter your desired subdomain (e.g., gtm.yourwebsite.com.au).
  • You will be provided with DNS records (usually A or AAAA records).
  • Log in to your domain registrar (like VentraIP or NetRegistry) and add these records to your DNS settings.

Pro Tip: It can take anywhere from 1 hour to 24 hours for DNS changes to propagate across Australia. Don't worry if it doesn't work immediately!

Step 4: Update Your Web Container Transport URL

Now we need to tell your website to send data to your new server instead of directly to Google.
  • Switch back to your Web Container in GTM.
  • Find your Google Tag (formerly the GA4 Configuration tag).
  • Under 'Configuration Settings', add a new parameter:
* Field: server_container_url * Value: Your new custom subdomain (e.g., https://gtm.yourwebsite.com.au)
  • Save and Preview the Web container.

Step 5: Set Up a Client in the Server Container

In the Server Container, 'Clients' are responsible for receiving the data from the browser.
  • In the Server Container, click Clients on the left menu.
  • You will see 'GA4' and 'UA' listed by default. Ensure the GA4 Client is enabled.
  • This client will listen for incoming requests from your website's Google Tag and claim them for processing.

Step 6: Create Server-Side Tags (GA4)

Now that the server is receiving data, it needs to send it to the final destination.
  • Go to Tags > New.
  • Select Google Analytics: GA4 as the tag type.
  • Enter your GA4 Measurement ID (the same one used in your web container).
  • Under Triggering, select All Pages (or a custom trigger that matches the incoming GA4 client requests).
  • Screenshot Description: Your tag configuration should show the GA4 Measurement ID and a trigger that looks for "Client Name equals GA4".

Step 7: Preview and Debug

This is the most critical step to ensure you aren't "flying blind."
  • Click Preview in your Server Container.
  • Click Preview in your Web Container.
  • Browse your website in the debug window.
  • In the Server Container Debugger, you should see requests appearing in the left-hand column. If you click on one, it should show that a tag has fired successfully.

Step 8: Publish Your Changes

Once you have verified that data is flowing from the Website -> Server -> Google Analytics:
  • Click Submit in the Server Container.
  • Give your version a name (e.g., "Initial Server-Side Setup").
  • Click Publish.
  • Repeat this for the Web Container if you made changes to the transport URL.

---

Common Mistakes to Avoid

  • Missing the HTTPS: Always ensure your Server Container URL starts with https://. Unsecured requests will be blocked by most modern browsers.
  • Forgetting DNS Propagation: Many Aussie business owners get frustrated when the setup fails on Step 3. Give the DNS time to update; use a tool like 'DNS Checker' to see if your subdomain is live.
  • Billing Issues: If your Google Cloud billing isn't set up correctly, the server will shut down without warning, and you'll lose all tracking data.

Troubleshooting

  • Problem: No data appearing in Server Preview.
Solution:* Check your Web Container. Ensure the server_container_url is typed exactly right and that the Web Container has been published.
  • Problem: 404 Errors in the Console.
Solution:* This usually means the Server Container isn't yet live or the DNS hasn't pointed to the right IP address. Re-check your A records in your domain registrar.
  • Problem: High Google Cloud Costs.
Solution:* For most small businesses, the default 'Testing' setup is fine. If you have massive traffic, ensure you haven't over-provisioned the number of server instances in the Google Cloud Console.

Next Steps

Setting up server-side tracking for GA4 is just the beginning. To truly maximise your marketing performance, you should next look at:
  • Meta Conversions API (CAPI): Send your Facebook conversion data server-side to improve ad attribution.
  • Cookie Longevity: Configure your server to extend the life of first-party cookies.
  • Data Redaction: Use the server to strip out PII (Personally Identifiable Information) before it reaches Google, ensuring you stay compliant with privacy standards.

If this feels a bit too technical or you're worried about breaking your current tracking, we can help. The team at Local Marketing Group specialises in technical SEO and analytics for Australian businesses. Contact us today to get your tracking sorted professionally.

Google Tag ManagerServer-Side TrackingGA4Data Privacy

Need Help With This?

Our team can help you implement this and more. Book a free consultation.

Book Free Consultation