Leigh Merritt

Server-Side Tagging Setup: A Step-by-Step Guide for Marketing Teams

Modern server room with clean geometric data visualization flowing between server racks and cloud icons, minimalist tech aesthetic with blue and white colour scheme, professional B2B illustration style

Leigh Merritt

If you’ve been wrestling with iOS updates killing your Facebook ads performance or watching your Google Analytics data become increasingly patchy, you’re not alone. Third-party cookie restrictions and privacy changes have left many marketing teams flying blind.

Server-side tagging isn’t just a technical upgrade—it’s your way back to reliable data collection and better customer insights. But before we get into the nuts and bolts of setting it up, let’s talk about why you should care.

Why Server-Side Tagging Matters Right Now

Traditional client-side tracking sends data directly from a user’s browser to platforms like Google Analytics or Facebook. This method is increasingly unreliable because:

  • Ad blockers prevent tags from firing
  • iOS updates limit tracking capabilities
  • Browser restrictions block third-party cookies
  • Page load speeds suffer from multiple tracking scripts

Server-side tagging flips this model. Instead of browsers talking directly to marketing platforms, they send data to your server first. Your server then decides what data to share and where to send it. You’re back in control.

What You’ll Need Before Starting

Let’s be realistic about what this involves. Server-side tagging requires:

  • Google Tag Manager (GTM) access with admin permissions
  • Google Cloud Platform account
  • GA4 property set up and running
  • Basic understanding of GTM containers and tags
  • Budget for server costs (more on this below)

Time investment: Plan for 4-6 hours of initial setup, plus ongoing monitoring and optimisation.

Step 1: Create Your GTM Server Container

Head to Google Tag Manager and create a new container. This time, you’re not choosing “Web”—select “Server” as your target platform.

Your server container will receive data from your website and forward it to marketing platforms. Think of it as a sophisticated relay station for your tracking data.

Once created, you’ll see a different interface than your standard web container. Server containers use “clients” (which receive data) and “tags” (which send data out) rather than the triggers and tags you’re used to.

Step 2: Deploy Your Server Container to Google Cloud

Here’s where things get technical, but Google has made this surprisingly straightforward:

  1. In your server container, click the deployment icon in the top right
  2. Choose “Automatically provision tagging server”
  3. Select your Google Cloud project (create one if needed)
  4. Choose your preferred region (pick one close to your audience)
  5. Click “Provision”

Google will automatically set up App Engine, configure the necessary services, and provide you with a server URL. This process typically takes 5-10 minutes.

Cost Considerations for Server Deployment

Let’s talk money. Google Cloud isn’t free, and server-side tagging costs vary based on your traffic:

  • Low traffic sites (under 100k events/month): £15-30/month
  • Medium traffic sites (500k events/month): £50-100/month
  • High traffic sites (2M+ events/month): £200+/month

These are rough estimates. Your actual costs depend on event volume, data processing complexity, and regional pricing. Monitor your Cloud Console billing section closely during the first month.

Step 3: Configure Your GA4 Client

Back in your GTM server container, you’ll need to set up clients to receive data. Start with the GA4 client:

  1. Click “Clients” in your server container
  2. Create a new client and select “GA4” from the gallery
  3. Leave the default settings—this client will automatically handle GA4 data
  4. Save and name it something obvious like “GA4 Client”

This client will receive all GA4 events sent from your website to your server.

Step 4: Update Your Website’s GA4 Configuration

Now you need to redirect your website’s GA4 tracking to send data to your server instead of directly to Google. In your web container:

  1. Open your GA4 Configuration tag
  2. Scroll to “Fields to Set”
  3. Add a new field: server_container_url
  4. Set the value to your server container URL from Step 2
  5. Save and publish your web container

Your website will now send GA4 data to your server first, rather than directly to Google Analytics.

Step 5: Create Server-Side GA4 Tags

Your server is receiving data, but it’s not sending anything to GA4 yet. Create a server-side GA4 tag:

  1. In your server container, create a new tag
  2. Choose “GA4” from the tag gallery
  3. Enter your GA4 Measurement ID
  4. Set the trigger to “All Events”
  5. Save and publish your server container

Test this setup using GTM’s preview mode. You should see events flowing from your website, through your server, and into GA4.

Common Pitfalls and How to Avoid Them

Custom Domain Setup

Your server URL (something like https://gtm-abc123.appspot.com/) looks suspicious to ad blockers. Set up a custom subdomain like analytics.yourdomain.com pointing to your server. This significantly improves data collection rates.

Double Data Collection

Don’t run client-side and server-side GA4 tracking simultaneously—you’ll double-count everything. Choose one method and stick with it.

Event Data Mapping

Not all client-side events translate perfectly to server-side. Enhanced ecommerce events, in particular, may need manual configuration to ensure all parameters are captured correctly.

Testing and Validation

Use GA4’s DebugView and Real-time reports to verify your data is flowing correctly. Server-side implementation errors are harder to spot than client-side ones.

Adding Other Platforms

Once GA4 is working, you can add other platforms like Facebook Conversions API or Google Ads. Each requires its own client and tag configuration, but follows a similar pattern.

The beauty of server-side tagging is that you can enhance data before sending it out—adding customer lifetime value, cleaning up inconsistent naming, or filtering out internal traffic.

Next Steps and Ongoing Management

Server-side tagging isn’t a “set and forget” solution. Plan for:

  • Monthly cost monitoring: Keep an eye on your Google Cloud bills
  • Performance optimisation: Monitor server response times and event processing
  • Data validation: Regular checks that all events are flowing correctly
  • Privacy compliance: Update your privacy policy to reflect server-side processing

Server-side tagging gives you more reliable data and better control over customer information. It’s not the simplest setup, but for marketing teams serious about data accuracy, it’s becoming essential rather than optional.

Ready to get started? Download our server-side tagging implementation checklist to ensure you don’t miss any crucial steps in your setup.