Server-Side Tracking: Your Ad Data Is Getting Lost in the Browser

Instead of sending measurement data straight from the user's browser to platforms like Meta and Google, the data is first sent to a server container you control (server-side Google Tag Manager). There it is processed and filtered, then forwarded to the platforms server to server. The data is collected on your own domain as first-party data, so ad blockers and browser restrictions cannot intercept this route.

The Meta Pixel runs in the browser; when an ad blocker, Safari ITP or a cookie rejection kicks in, the event never reaches Meta at all. The Conversions API sends the same events from the server. The two are used together, with deduplication preventing double counting. Meta grades this matching in its dashboard as the Event Match Quality score; we compare that score with you before and after the setup.

The setup is $429 (excl. VAT) and is delivered with a report in 2-3 weeks. The server container runs in your own Google Cloud account; the monthly server cost depends on your traffic volume, is paid to Google, and usually lands in the range of a few tens of dollars per month for small to mid-traffic sites. Before the setup we give you a written cost estimate based on your traffic. Optional monitoring and maintenance is $69/mo, limited to a maximum of 5 clients.

Consent Mode v2 is the framework that passes the user's cookie consent status to Google systems as standardized signals. Google has required it since March 2024 for personalized advertising and remarketing in the European Economic Area. Set up incorrectly, Google Ads conversion measurement and audience lists quietly degrade. In our setup, Consent Mode v2 is configured to stay in sync with your consent management platform.

Server-side architecture does not remove consent management; it centralizes it. The consent a user gives or refuses is enforced identically at the server layer: no consent means no personal data is forwarded to the platforms. As part of the setup we deliver a data flow diagram documenting what is collected and where it goes. For your privacy policy and the legal assessment we recommend working with your own legal counsel; we handle the technical implementation side.

Your existing setup is not deleted; it is converted. We first build an event inventory, then route your browser tags through the server container, with deduplication preventing double counting. There is no measurement gap during the migration; the old and new flows run in parallel for a short period, and once verified, the old direct requests are switched off.

With three indicators: the change in your Event Match Quality score in the Meta dashboard before and after setup, the closing of the conversion count gap between GA4 and your ad dashboards, and the event volume in the server container logs. The handover report includes the first measurement of all three; on the maintenance plan we track them monthly. Because the loss rate varies from site to site, we do not promise a percentage upfront; we measure it on your site.