Server-Side Tracking Case Study for E-commerce BusinessWeb + Server GTM, Working Together

With normal tracking, the visitor's browser sends data directly to Google Ads, GA4 and every other platform. With server-side tracking, the browser sends one stream of data to a tagging server that you control, and that server sends the data on to each platform.

Because the browser only talks to your own server, far fewer requests are blocked, cookies can be set in a first-party context that lasts longer, and you decide exactly what data each platform receives.

• Ad blockers and Safari tracking prevention were removing a share of add to cart, checkout and purchase events
• Google Ads purchase conversions were lower than real orders, so reported ROAS was understated
• Smart Bidding had less data to learn from than the store actually generated
• Every new platform meant adding another script to the website, slowing it down

The web container on the store captures the full ecommerce journey with custom event triggers fired from the site's data layer.

• GA4 Config (Google Tag) on every page view, configured to send data to the tagging server instead of directly to Google
• GA4 events for page_view, view_item, add_to_cart, begin_checkout and purchase, each with full item and value data
• Google Ads Config plus Add To Cart, Begin Checkout and Purchase conversion tags, and a Conversion Linker
• Microsoft Clarity for session recordings and heatmaps of the shopping journey

The server container receives the GA4 requests through the GA4 client, then each tag decides where the data goes. This is where the data is sent on to the ad and analytics platforms.

• GA4 client claims the incoming requests from the website
• GA4 tag forwards events to the GA4 property from the server
• Google Ads Add To Cart, Begin Checkout and Purchase conversion tags send the same events to Google Ads
• A server-side Conversion Linker keeps the ad click ID so each conversion is credited to the right click

• A shopper views a product, adds it to the cart, starts checkout and places an order
• The data layer on the store pushes each of those events with product, value and currency data
• The web container sends them through the GA4 stream to the tagging server on the store's own subdomain
• The server container's GA4 client receives them, and the server tags pass them to Google Ads and GA4
• Google Ads and GA4 both receive the same events, so their numbers line up with each other and with the shop

• Web container checked in GTM Preview mode by viewing products, adding to cart, starting checkout and placing test orders
• Server container Preview used at the same time to confirm each request was claimed by the GA4 client and every tag fired
• GA4 DebugView and Realtime used to confirm events and purchase values arrived correctly
• Google Ads conversion diagnostics checked to confirm add to cart, begin checkout and purchase were all recording

Conversion data now travels through the store's own server, so far less of it is lost to blockers and browser restrictions. Google Ads and GA4 receive the full shopping journey from one consistent source, Smart Bidding learns from more complete purchase data, and new platforms can be added on the server without adding more scripts to the website.