Server-Side Tracking and Enhanced Conversions for E-commerce: Why Measurement Comes Before Scaling

By Jacob Thyssen, Founder of Thyssen Ads

10 Nov 2026

Short answer: Smart Bidding can only optimise to the conversions it sees. Browser-only tracking loses sales to ad blockers, browser privacy limits and consent, and misconfigured accounts often count the same sale twice. Server-side tracking routes data through your own tagging server so it's more reliable and under your control. Enhanced conversions add hashed first-party data (like email) to recover conversions cookies miss. Consent mode passes your visitors' choices to Google. Set up all three, verify Google Ads against real orders, and only then scale. Scaling on bad data just means losing money faster.

In almost every account we audit, the first problems aren't in the campaigns. They're in the data. Two purchase actions both counted as primary. A thank-you page tag that fires on refresh. A consent banner that blocks the conversion tag entirely. The campaigns are being optimised, just to the wrong numbers.

That's why we treat measurement as infrastructure: server-side tracking and a dedicated tracking specialist before we scale anything.

Why tracking matters more than ever

Google Ads bidding is automated. Target ROAS, Maximise conversion value and Performance Max all learn from the conversion data you send. Google's own conversion measurement documentation is built around that idea.

When data is wrong, three things happen:

1. Missing conversions make good campaigns look unprofitable, so bidding pulls back from them.
2. Duplicated conversions make campaigns look better than they are, so bidding overspends.
3. Revenue without profit makes bidding chase low-margin sales. See POAS vs ROAS.

Part 1: Server-side tracking

What it is

With standard (client-side) tracking, the shopper's browser sends data directly to Google and every other tool. With server-side tracking, the browser sends data to your own tagging server, typically on a subdomain like data.yourshop.com. The server decides what to forward to Google Ads, GA4 and other platforms.

Google's own implementation is server-side Google Tag Manager.

Why e-commerce brands use it

• More reliable data. Requests go to your own domain in a first-party context, which tends to be less affected by browser restrictions and blockers than third-party requests.
• Control. You decide what leaves your systems and can remove data you don't want to share.
• Enrichment. You can add data the browser should never see, such as product cost, to send profit as conversion value.
• Faster pages. Fewer third-party scripts in the browser.

What it isn't

Server-side tracking isn't a way around consent. You still need a consent banner and consent mode, and you must respect the visitor's choice.

Part 2: Enhanced conversions

What it is

Enhanced conversions send hashed first-party customer data with the conversion, usually email, and optionally phone, name and address. Data is hashed with SHA-256 before it's sent. Google matches it to signed-in Google accounts to attribute conversions that cookies alone would miss.

Why it matters for shops

Shoppers switch devices, clear cookies and decline tracking. Enhanced conversions recover part of that lost signal, which gives Smart Bidding more data to learn from.

How to set it up

1. Make sure the checkout confirmation page (or server event) has the customer email available.
2. Turn on enhanced conversions for the purchase action in Google Ads.
3. Send the data through Google Tag Manager, the Google tag or server-side GTM.
4. Check the diagnostics in Google Ads after a few days to confirm match rates.

Part 3: Consent mode

Consent mode passes the visitor's consent choices to Google tags. In the EEA, consent signals are needed to use Google's personalisation and measurement features. If your banner and tags aren't connected properly, you can lose conversion data for everyone who declines, or worse, for everyone.

Checklist:

• Consent banner integrated with consent mode (ad_storage, analytics_storage, ad_user_data, ad_personalization).
• Default consent state set before tags fire.
• Tags respond correctly when consent is granted or denied.
• Tested in every market and language version of the site.

Part 4: The e-commerce tracking audit

Run this before you trust any ROAS number:

• One primary purchase conversion. More than one primary purchase action is one of the most common reasons sales count twice.
• Google Ads purchases vs shop orders. Compare the same period. Expect a gap from attribution and consent, but not double the orders.
• Transaction ID passed so Google can deduplicate.
• Conversion value = what you want to optimise. Revenue excluding VAT and shipping, or gross profit.
• Currency correct for each market.
• No firing on refresh or on revisits to the confirmation page.
• Enhanced conversions active and matching.
• Consent mode working in every market.
• GA4 imports not double-counting alongside the Google Ads tag.
• Brand and non-brand reported separately so you can see what non-brand really returns. See our account structure guide.

Our Octopus AI runs tracking checks as part of a 35-check audit across 8 areas, and flags problems like duplicate primary purchase actions first.

Part 5: From revenue to profit

Once tracking is clean, the next step is to send the number that matters to the business. With server-side tracking you can look up product cost on the server and send gross profit as conversion value. Target ROAS then optimises to profit instead of revenue.

For Unsolved, tracking was rebuilt at takeover, before scaling. Six European markets became profitable in six months, and Q1 2026 delivered a record 2.06x POAS. Read the Unsolved case study.

What it looks like in practice

When we took over Hundlands in May 2026, the first step was moving the brand onto full server-side tracking, alongside splitting brand and non-brand. Only then did we localise feeds and scale. By August and September 2026, total store sales were up 76% year over year, and Google Ads ROAS was up 39% while spend scaled more than sixfold. Read the Hundlands case study.

The order matters: tracking before spend.

Common mistakes

• Installing server-side GTM and forgetting the Google Ads tag still fires in the browser, so every sale counts twice.
• Using GA4-imported conversions and the Google Ads tag as primary at the same time.
• Sending revenue including VAT and shipping in one market and excluding them in another.
• Not retesting after site updates. A new checkout or theme can silently break tracking.
• Treating tracking as a one-off project. It's infrastructure. It needs an owner.

The bottom line

Server-side tracking, enhanced conversions and consent mode aren't technical extras. They decide what Smart Bidding learns. Get one clean purchase conversion, verify it against real orders, recover lost signal with enhanced conversions, respect consent, and send profit where you can. Then scale.

Not sure your Google Ads numbers match reality? Get your free Google Ads and tracking audit.

FAQ

What is server-side tracking in Google Ads?

Instead of sending every tracking request from the shopper's browser straight to Google, the browser sends data to your own tagging server, usually on a subdomain of your shop. That server then forwards it to Google Ads and other tools. It gives you more control over what is sent and usually makes measurement more reliable.

What are enhanced conversions?

Enhanced conversions send hashed first-party data, such as the customer's email address, with the conversion. Google matches it to signed-in users to recover conversions that cookies alone would miss. The data is hashed with SHA-256 before it is sent.

Do I need server-side tracking and enhanced conversions?

If you scale Google Ads with Smart Bidding, yes in most cases. Bidding can only optimise to the conversions it sees. Missing or duplicated conversions mean it learns the wrong lessons.

Is server-side tracking GDPR compliant?

Server-side tracking doesn't replace consent. You still need a consent banner and consent mode, and you must respect the visitor's choice. Done properly, it gives you more control over which data leaves your systems.

What is consent mode?

Consent mode passes the visitor's consent choices to Google tags so they adjust their behaviour. In the EEA, consent signals are needed to use Google's personalisation and measurement features.

How do I know if my Google Ads tracking is broken?

Compare Google Ads purchases with orders in your shop for the same period, check how many conversion actions are set to primary, and look for sudden drops after site or consent changes. More than one primary purchase action is a common reason sales count twice.

Sources

• Google Ads Help: About conversion measurement
• Google Ads Help: About enhanced conversions
• Google Ads Help: About consent mode
• Google for Developers: Server-side Tag Manager