Chapter 13
Common mistakes in server-side tracking
 "Zoran Artmagic")
Table of contents
In recent years, arboro has set up server-side tracking in many Shopware and Shopify stores and reviewed existing setups built by other providers. The same mistakes keep coming up. Most of them are avoidable.
Mistake 1: No clear requirements
The switchover starts with the technology instead of the question of what should be measured. The result: events are missing, parameters are incomplete and teams do not get the numbers they need. The measurement plan from Chapter 4 prevents this.
Mistake 2: The old tracking keeps running
The numbers in GA4 rise sharply after the switch and everyone is pleased. In reality, everything is being measured twice. An insidious mistake, because it produces good news.
Mistake 3: Duplicate routes to the same platform
A Shopify app reports purchases to Google, and the server container does too. Or the browser pixel and the Conversions API run without a shared event ID. The platform counts twice, ROAS looks better than it is and bid automation learns the wrong lesson.
Mistake 4: Consent ignored on the server
The cookie banner only controls the browser. The server container still forwards everything that arrives. Data protection then depends on a single point, and errors in the banner are passed on unnoticed to every platform.
Mistake 5: The promise of "tracking without consent"
Some providers sell server-side tracking as a way around consent. That does not hold up legally and can become expensive. What the law says is covered in Chapter 3.
Mistake 6: Wrong or undersized hosting
Servers outside the EU make the data protection assessment harder. A single server without redundancy loses events at peak load, exactly when most is being sold.
Mistake 7: No user data for the platforms
The server sends purchases, but without a hashed email, phone number or address. Enhanced Conversions and the Meta Conversions API fall far short of their potential.
Mistake 8: Shopify checkout not migrated
Purchase tracking relied on legacy scripts on the Thank you page. Since August 2026 they no longer run, and some purchases are missing. Many stores have not noticed yet.
Mistake 9: No maintenance plan
A store update changes a template and the purchase event disappears. Nobody notices until weeks later someone asks why the campaigns are performing so badly.
Mistake 10: Judging success by how high the numbers are
Tracking is not good because it delivers high numbers, but because it delivers consistent ones. Measured purchases above actual orders are always a mistake.
The four most important checks
Are the purchases measured in GA4 below or equal to actual orders?
Is there exactly one conversion route, or working deduplication, for each ad platform?
Does the server container evaluate the consent status itself?
Is there a defined maintenance plan with a responsible person?
Frequently asked questions
Most easily by comparing with actual orders. If GA4 or an ad platform reports more purchases than the store had, you are counting twice.