4.9
Server-side tracking for eCommerce brands
Recover the conversions that ad blockers and browser restrictions take out of your reporting, with a server-side container built and maintained by our analytics team.
Trusted by 700+ leading brands worldwide
Trusted by 700+ leading brands worldwide
The analytics team behind the setup
$4B+
In client revenue processed each year
2,100+
eCommerce projects delivered
25+
Full-time analysts and data engineers
%20(1)-p-800.png)
.svg)
Why your conversion numbers keep coming up short
Browsers and ad blockers can remove a meaningful share of client-side tag data before it reaches your platforms, showing up as under-reported conversions. It widens every time a browser adds a new privacy default.
Under-reported conversions
Ad blockers and tracking prevention stop client-side tags firing, so a share of real orders never appears in GA4 or your ad platforms at all.
Bidding on incomplete data
Ad platforms optimize against whatever conversions they receive. Missing signals push budget toward audiences that only look like they perform.
Uncounted repeat visits
Browsers delete tracking cookies after a few days, so a shopper who compares for weeks looks like a brand-new visitor when they buy.
What our server-side tagging setup includes
Every setup starts with measuring what you are losing today, then moves those tags to a server you control.
Server-side container build
A server-side Google Tag Manager container on your own subdomain, so requests come from your domain.
Conversion API connections
Meta, TikTok, and Google conversion APIs connected through the server container for complete purchase events.
Data loss measurement
We measure the gap between orders in your backend and conversions in each platform.
Consent Mode configuration
Consent Mode v2 signals are passed through to the server container.
Event QA against real orders
Each event is checked against real orders in your backend and documented for every platform.
Monitoring and ownership
Alerting on event volume drops, plus documentation your team can maintain after handover.
See how many orders your platforms miss
%20(1).png){kind=tracking}
Consent in a server-side setup
Server-side tagging executes tags on your server, and it does not change what a visitor agreed to. Consent Mode signals travel with each event into the server container, and the container decides what to forward per platform. Setups that skip this step pass on data they have no permission to use, which is a compliance problem as much as a tracking one.
Wider policy work is handled by our GDPR compliance team.
Why brands choose scandiweb for server-side tracking
Server-side work changes your hosting setup and creates data-protection obligations, so it belongs with a team that has delivered it before. Our analytics team has worked in eCommerce since 2015 and handles server-side setups as standard.
Recovery you can verify
We baseline the gap before the build and re-measure after handover, so the improvement is a documented number.
eCommerce transaction depth
Purchase and refund events behave differently across platforms, and our event patterns are built for stores.
Your infrastructure, your data
The container is hosted on your subdomain under your cloud account, so the first-party data stays under your control.
Consent handled at the source
Consent signals are honored inside the container itself, so forwarding decisions happen where they can be audited.
Platform-agnostic delivery
Adobe Commerce, Shopify Plus, BigCommerce, and headless builds are all supported by the same server-side approach.
Certified and audited
scandiweb holds analytics partner status with both Google and Adobe and is certified to ISO 27001, ISO 27017, ISO 9001.
How a server-side tracking project is delivered
A baseline measurement comes first, so the result can be checked against it later. Scope is set by the number of platforms and markets you measure, which the stage-one audit confirms before any build work begins.
Loss baseline
We compare orders in your backend against conversions each platform reports, producing the gap figure the project is measured against.
Architecture and hosting
We choose the hosting model and subdomain, then size the container for your traffic so costs are known before the build.
Container build
The server-side container is built, with each tag rebuilt inside it and consent signals passed through to it from the client side.
Platform connections
Each ad platform is connected through its conversion API, and match quality is tuned until the reported numbers stabilize.
QA, handover, and monitoring
Events are validated against real orders, alerting is configured on volume drops, and we hand over the container documentation.
.png)
Server-side tracking in production
Revenue up 176% after server-side tracking went live
+75%
User data captured with Consent Mode
+195.2%
Mobile conversion rate
+69.9%
Visitors
Learn more
Merging data from 120+ physical stores, ERP, POS & stores
500k+
First-party data profiles
120+
Physical stores unified
5
Markets live
Learn more
What clients say about working with scandiweb
.webp)
.png)
Frequently asked questions about server-side tracking
How much tracking data are we actually losing?
Most eCommerce stores find that platform-reported conversions come in below what the backend records, and the size of the gap depends on traffic mix and how much of it arrives on mobile Safari. We measure it against your order data before quoting, so the number is yours and not an industry average.
Will server-side tagging slow down our site?
It usually does the opposite. Moving tags off the browser removes scripts from the page, which reduces main-thread work and helps Interaction to Next Paint. The server container adds latency on its own request path, and that happens away from the visitor's browser.
What does a server-side container cost to operate?
Two costs apply: the cloud hosting for the container, which scales with your traffic volume, and any ongoing support you choose. We size the hosting during the architecture stage and give you the projected monthly figure before the build starts.
Does server-side tracking work with Google Consent Mode?
Yes. Consent Mode v2 signals are passed into the server container alongside each event, and the container applies them when deciding what to forward to each platform. Consent is honored one step later in the chain, which makes the decision easier to audit.
Do we need our own server and subdomain?
A subdomain on your own domain is what makes the requests first-party, so yes to that part. Hosting stays inside your cloud account, most often Google Cloud, and we size it during the architecture stage so the monthly cost is known before anything is built.
Can you move our existing setup without losing historical data?
Yes. The server-side container is built in parallel with your current client-side setup, both are compared during QA, and the switch happens once the numbers agree. Historical data in GA4 is untouched. Where the GA4 property needs rebuilding as well, our GA4 support team handles that separately.
Talk to a server-side tracking specialist
Tell us which platforms you measure and roughly how many orders you process each month. A specialist replies with an estimate of what your current setup is losing and what a server-side build would involve.
Book a call straight away or email us at: [email protected]
Related analytics services
Losing conversions you cannot see? Measure the gap first.
A specialist baselines what your current setup is missing and quotes the fix against that number.
