BE Digital Knowledge base

Welcome to the BE Digital knowledge base, a source full of articles on digital topics. Our knowledge base is continually updated with the latest insights. We also regularly publish valuable whitepapers that offer in-depth analysis and advice. For the latest news and trends, visit our blog.

Jamie Schelling - BE Digital

Written by

Digital Marketing & AI Automation

Updated on 3 February 2025

GA4 data discrepancies: server-side tracking and the Measurement Protocol

In the dynamic world of digital analytics, many organisations struggle with a challenging problem: differences between Google Analytics 4 (GA4) data and their actual figures. These discrepancies can lead to wrong decisions and ineffective strategies. Fortunately, there is a powerful solution that combines two advanced techniques: server-side tracking and the Google Measurement Protocol.

Why don't the numbers add up?

There are several reasons why GA4 data can deviate from reality:
  • Ad blockers that block GA4 scripts
  • Users who refuse cookies for privacy reasons
  • Slow loading times, especially on mobile, meaning GA4 doesn't load fully
  • Limitations of traditional tracking methods
  • Consent Mode V2 impact

The impact of Consent Mode V2

An important factor that has recently been contributing to data discrepancies is the introduction of Consent Mode V2. This feature, designed to comply with privacy rules, affects how GA4 collects data based on user consent. When users don't give consent for tracking, this leads to gaps in data collection. Although Consent Mode V2 is essential for privacy compliance, it can result in underreporting of important metrics if it is not implemented or interpreted correctly.
These factors cause part of user behaviour to remain invisible, leading to incomplete data and distorted insights.

Server-side tracking: the invisible helper

Server-side tracking moves the heavy lifting of data collection to the server. This offers some major benefits:
  • Bypass ad blockers: Because the tracking happens on the server, ad blockers have no hold on it.
  • Faster websites: Fewer front-end scripts means faster loading times.
  • More control: You decide exactly which data is collected and how it is processed.
  • Refined consent handling: Better management of user consent, including the nuances of Consent Mode V2.
Think of server-side tracking as an efficient backstage crew that keeps everything running smoothly, without the audience (the users) noticing.

The Measurement Protocol: the direct line to GA4

The Google Measurement Protocol is like VIP access to GA4. It allows developers to send data directly to GA4, without the intervention of browsers or tags.
By combining this with server-side tracking, you create a powerful data pipeline:
  1. Collect data on the server
  2. Process and enrich this data, taking consent settings into account
  3. Forward it directly to GA4
The result? More accurate, more complete data available in real time, even within the limits of cookie consent.

The benefits at a glance

This combined approach offers numerous benefits:
  • More accurate data: Fewer discrepancies between GA4 and actual figures.
  • Better insights: Users with ad blockers now become visible too.
  • Improved privacy: More control over which data is collected and shared, in line with Consent Mode V2.
  • Future-proof: Flexible enough to evolve with new privacy rules.
  • Optimised consent processing: Better integration and interpretation of user consent.

Getting started

Considering this approach for your organisation? Here are some steps to start with:
  1. Evaluate the current setup: Where are the biggest discrepancies? How does Consent Mode V2 affect your data collection?
  2. Look at the technical possibilities: What is needed to implement server-side tracking and integrate it with your consent management?
  3. Start small: Begin with a pilot project to test effectiveness, paying special attention to the impact on privacy-sensitive metrics.
By combining server-side tracking with the Measurement Protocol and a well-thought-out implementation of Consent Mode V2, you can significantly improve the reliability of your GA4 data. The result? Sharper insights, better decisions and ultimately a more effective digital strategy, all within the bounds of privacy rules and user preferences.
Want to know more about how to implement and optimise this solution for your specific privacy challenges? Then get in touch with our experienced digital analytics team. They can help you make optimal use of these powerful techniques, taking into account the latest developments in data privacy and cookie legislation.

Frequently asked questions

Why do my GA4 figures not match the actual figures?

GA4 data can deviate because of ad-blockers that block scripts, users who refuse cookies, slow loading times that stop GA4 from loading fully, and limitations of traditional tracking. Consent Mode V2 also contributes, as a lack of consent creates gaps in data collection.

How does server-side tracking help against data discrepancies in GA4?

Server-side tracking moves data collection to the server, so ad-blockers cannot interfere with it. Websites also become faster thanks to fewer front-end scripts, you have more control over which data is collected and you can handle consent better.

What is the Google Measurement Protocol and how do you use it together with server-side tracking?

The Measurement Protocol allows developers to send data directly to GA4, without the involvement of browsers or tags. Combined with server-side tracking, you collect data on the server, process and enrich it while taking consent into account, and send it straight to GA4.

Jamie Schelling - BE Digital

About the author

Digital Marketing & AI Automation

Jamie Schelling is a Digital Marketing & AI Automation specialist at BE Digital. She combines data, campaigns and automation to make digital performance visible and to improve it structurally.