Tag PilotTrack missed conversions with server-to-server tracking
The classic approach to conversion tracking is to place tags on the order confirmation page (also called the thank-you page). It is technically easy, because all cookies and attribution data should be available there. The problem is that sometimes users never reach that page.
They may drop off by closing the browser tab too early, or the payment method may have a complex flow (think of Buy Now, Pay Later providers that run an online credit assessment).
Server-side GTM avoids these problems by enabling server-to-server tracking: things happen behind the scenes, so no user action can interrupt them.
Why traditional client-side tracking fails
Client-side tracking relies on user behaviour that marketers can’t control. When customers pay through third-party payment providers like Klarna, Afterpay or PayPal, they are often redirected several times before they may return to your thank-you page. Each redirect is another chance to lose data.
Ad blockers are another significant challenge. A share of your visitors run some form of ad blocking, and their conversions simply vanish from your analytics. This creates blind spots in your marketing attribution and makes budget optimisation much harder.
Browser crashes, network timeouts and users closing the tab right after the payment confirmation make it worse. You end up with incomplete data that undermines confidence in your marketing metrics.
How server-to-server tracking works
Server-to-server tracking moves conversion recording away from the user’s browser to your backend. Instead of relying on JavaScript tags that fire when users land on specific pages, your server communicates directly with advertising platforms and analytics tools.
The process typically works like this: when a payment is processed successfully in your system, your server sends the conversion data to Google Ads, Meta, GA4 and other platforms. This happens regardless of what the user does after completing the purchase.
Your payment provider (Stripe, PayPal and others) can trigger webhooks that notify your server about successful transactions. They carry the transaction details, such as customer IDs, values and timestamps, which, combined with the attribution data you stored earlier, link the conversion back to the original marketing touchpoint.
Setting up server-side GTM for conversions
Server-side Google Tag Manager acts as the bridge between your backend and your marketing platforms. Unlike client-side GTM, which runs in users’ browsers, server-side GTM runs on a dedicated server, which makes data delivery reliable.
First, configure your server container to receive conversion events from your backend. This means setting up a GTM client that accepts requests containing conversion data. Your ecommerce platform or custom checkout sends the transaction details to that endpoint right after the payment is confirmed.
The server container then processes the data and forwards it to the advertising platforms through their server-side integrations: the Google Ads conversion tag and GA4 in the server container, the Meta Conversions API, and similar endpoints for other platforms.
Benefits beyond tracking reliability
Server-to-server tracking does more than capture more conversions. Data quality improves, because you work with clean, structured information from your backend rather than browser data that may be incomplete.
Privacy compliance is easier to manage, because you control exactly what data is shared with advertising platforms. You can apply consent rules and data filtering at the server level to comply with the GDPR, CCPA and other privacy regulations.
With complete conversion visibility you can optimise with more confidence. Campaigns that looked unprofitable because of tracking gaps may turn out to be performing well.
Attribution modelling gets more accurate when you capture all conversions consistently. You can implement custom attribution logic on your server, taking into account factors like customer lifetime value, repeat purchases and cross-device behaviour.
Implementation considerations
Server-side tracking is technically more complex than simple pixel-based tracking. You need developers familiar with APIs and webhook processing, and possibly with server infrastructure management if you don’t use managed server-side GTM hosting.
Testing and validation need more sophisticated approaches than client-side tracking. You have to verify that conversion data flows correctly through the whole system, from payment confirmation to the reports in your advertising platforms.
The biggest challenge is connecting server-side tracking with browser-side information. Even without third-party cookies, the user’s browser is still the key source of attribution data, such as page referrers, query parameters and first-party cookies. To get correct attribution in reporting and advertising tools, that data needs to be stored: captured when the user starts the checkout, then looked up when the server webhook arrives.
Our take
Server-side tracking (not to be confused with server-side tagging, see Server-side tagging and tracking) is the most reliable way of making sure analytics and advertising tools see your conversions. For some payment methods, such as Stripe Payment Links, it is the only practical way to track transactions across channels.
It also goes well beyond classic browser pixels and tagging, and needs more advanced tooling, such as storing and processing cookies and other attribution data on the backend.