Measure first.
Then budget.
We make sure Shopify, GA4, Meta and Google Ads see the same orders: server-side, with consent logic connected and fully documented.
Server-Side Tracking
Purchases captured
Event stream
- purchase€129.00GA4 ✓ Meta ✓ Ads ✓
- add_to_cart€64.90GA4 ✓ Meta ✓ Ads ✓
- begin_checkout€218.40GA4 ✓ Meta ✓ Ads ✓
- view_item€89.90GA4 ✓ Meta ✓ Ads ✓
- purchase€74.50GA4 ✓ Meta ✓ Ads ✓
- add_to_cart€39.00GA4 ✓ Meta ✓ Ads ✓
- purchase€312.80GA4 ✓ Meta ✓ Ads ✓
The browser loses orders.
A pixel in the browser depends on things outside your control. If one of them fails, the platform misses the order, even though it was booked in the store long ago.
iOS asks first
Since Apple's tracking prompt, many users decline tracking. Meta then only sees part of what is actually bought.
Blockers swallow events
Anyone using an ad blocker doesn't fire an event in the browser. No data from these sessions reaches analytics or the ad platforms.
Cookies live shorter
Safari and Firefox strictly limit cookie lifetimes. Anyone who returns after a few days counts as a new visitor, and the first touchpoint is lost.
Budget follows the wrong numbers
If a platform reports too few purchases, a good channel looks bad. The more budget depends on that number, the more expensive the wrong decision.
What the server does better.
With server-side tracking, your own tagging server reports the order to Meta, Google and other channels. The customer's browser is no longer the weakest link in the chain.
More purchases attributed
The platforms recognize more orders and credit them to the ad that triggered them.
Independent of the browser
The event leaves the store via your server. Blockers and cookie rules no longer get in the way.
Better-managed campaigns
Meta and Google learn from more complete signals and no longer optimize for an incomplete picture.
You're in the right place if …
GA4 and Shopify show different revenue, and nobody knows which number is right.
Meta reports significantly fewer purchases than your store.
Nobody in Google Tag Manager knows anymore which tag triggers what.
You want to spend more on paid media and first need numbers you can rely on.
Your tracking has grown over the years, and nobody dares to touch it anymore.
Your setup only runs in the browser and loses signals there.
When something else matters more.
Consent isn't sorted out
As long as the consent banner and Consent Mode aren't set up properly, you're measuring on shaky ground. That has to be settled first, otherwise the tracking won't hold up.
The numbers are right, the revenue isn't
If measurement is reliable and people still aren't buying enough, the problem lies in the store itself.
Go to Conversion OptimizationYour setup is fresh and documented
Then you don't need a rebuild, just occasional maintenance and small adjustments.
What's included.
GA4 e-commerce
Complete purchase and checkout events including product data, across the entire funnel.
Google Tag Manager
Clean-up or rebuild, with clear naming conventions and a clean data layer.
Server-side tracking
Events run through your own tagging server instead of only through the browser.
Meta Conversions API
Purchases reach Meta even when the browser blocks signals.
Google Ads conversions
Enhanced Conversions and clean conversion values as the basis for bidding strategies.
Consent & documentation
Consent Mode connected, every event documented and traceable.
How we work together.
Tracking audit
We record what fires, what's missing and what's counted twice, and reconcile store and platforms.
Measurement plan
We define which events go where, with which parameters.
Implementation & testing
Built in Tag Manager and on the server, test purchases included, with consent status passed through.
Reconciliation & docs
Platform numbers are checked against store orders, and every event is documented.
Three packages, one point of contact.
Want to know what your setup measures first? Or rebuild right away? Or take the step to the server? That gives you three ways to go.
Tracking audit
Stores where the numbers in Shopify, GA4 and the ad platforms contradict each other and nobody can name the cause.
- Inventory of all active tags, pixels and events
- Reconciliation of store orders with what the platforms report
- Findings with a clear path to a solution
You know which events are right, which are missing and which are counted twice.
Tracking setup
Stores that want to stop patching and rebuild their tracking cleanly once and for all.
- Google Tag Manager with a well-designed data layer
- GA4 with all e-commerce events across the funnel
- Meta Conversions API connected server-side
All events are checked and documented, stating what fires where and when.
Server-side tagging
Stores where blockers and cookie limits cost so much signal that the campaigns suffer.
- Your own tagging server for your store
- Server-side connection of the channels your budget depends on
- Testing of all events before going live
Conversions reach Meta and Google even when the browser blocks.
What we work with for you
The data layer delivers the data from the store, Tag Manager distributes it, and the tagging server passes it on to the platforms. Every link has its job, and every link is documented.
FAQ on tracking
Short, honest answers. If your question is missing, ask it in the intro call.
What is server-side tracking?
Orders and other events no longer go from the user's browser to Meta or Google, but from a server you control. Blockers and short cookie lifetimes no longer apply at that point. The data still comes from your store's data layer.
Why do Meta and Google report fewer purchases than Shopify?
Because a classic pixel runs in the browser. The iOS tracking prompt, ad blockers and short cookie lifetimes in Safari and Firefox cut off some of the events. The order still happens, the platform just never hears about it. Server-side tracking recovers part of that gap.
Why do the store and GA4 differ?
Because GA4 only sees users who have consented and don't block anything, while the store backend knows every order. On top of that, tags sometimes fire twice. Some discrepancy is therefore normal. Use GA4 for trends and channel comparisons, not as accounting, and make sure you know the gap and can explain it.
Do we need server-side tracking?
If you put significant budget into Meta or Google Ads, usually yes: the platforms optimize for the conversions they receive. With a small ad budget, a clean setup in the browser is often worth it first.
Does server-side tracking replace Google Tag Manager?
No, it complements it. The data layer collects the data in the store, the web container processes it, and a server container passes it on to the platforms. Without Tag Manager, the whole thing lacks control.
Does server-side tracking replace consent?
No. Server-side doesn't mean without consent. We pass the consent status from your banner through to the server container, so only what's allowed gets sent. That's why we plan consent and tracking together.
What changes for Meta and Google Ads?
Both receive more orders along with better attribution data and can base their delivery on that. For you, that means less guesswork about ROAS and attribution. Specific values depend on the store, which is why we only name them after the audit.
How do I know the setup is right?
At the end there's a log. Every event is checked against test purchases, and you see what fires when, with which parameters. That way any discrepancy can be explained later instead of guessed at.
Let's talk about your store.
In 30 minutes we clarify your starting point, goal and next steps. Free and without obligation, directly with the person who will work on your project.