Server-side tagging in PrestaShop: with or without GTM
Server-side tracking sends conversions to Meta, Google Ads or GA4 from the store's server, instead of relying only on the customer's browser. We explain why the pixel does not see every purchase, what deduplication is, what happens with consent and the two ways of setting it up in PrestaShop.
Server-side tagging, or tracking from the server, means that the store sends conversions to the ads and analytics platforms from its server, instead of relying only on the pixel that runs in the customer's browser. In PrestaShop it can be set up with a Google Tag Manager server container on your own server or with a module in the store that delivers the events through a managed relay.
If you run campaigns, the problem will sound familiar even if you do not know its name: the ads dashboard shows fewer purchases than the store has actually had thanks to those ads. The platform is not lying; it simply has not seen them. This article explains why it happens, what changes when the data is sent from the server and how to choose the way to set it up, with just enough technical detail. We cover the most technical part (Meta's Conversions API and deduplication in detail) in another article on the blog.
Why the pixel alone does not see every purchase
The pixel is a piece of code that loads in the browser of whoever visits your store and tells the platform: “this person has viewed a product”, “has added to the basket”, “has bought”. It works as long as the browser cooperates, and it cooperates less and less:
- Ad and tracker blockers. They stop the pixel from loading. The purchase exists, but the notification never goes out.
- Browsers that cut cookies short. Some limit the lifetime of the cookies used to recognise that the person buying today is the one who clicked on the ad days ago.
- Rejected cookies. If the customer does not accept advertising cookies, the pixel must not fire.
- The confirmation page nobody sees. The purchase notification usually goes out from the “thank you for your order” page. If the customer pays at the gateway and closes the tab without returning to the store, the pixel never finds out.
- Loading errors. A slow connection, a conflict with other code on the page or a change in the theme, and the event is lost without warning.
The result is that the platforms receive only part of the purchases your campaigns bring about. And it is not just a reporting problem: bidding algorithms learn from the conversions they receive. With less data, they optimise worse and every sale looks more expensive than it is.
What changes when the server does the sending
Your store's server knows for certain when there is an order, because it is the one that records it. With server-side tracking, it is the server that reports the conversion to each platform, server to server, without going through the browser. That has three effects:
- It does not depend on what happens in the browser. A blocker cannot stop something that is not sent from the customer's device.
- It can be retried. If the platform does not respond at that moment, the event waits and is sent again. The pixel only gets one chance.
- It can be checked. There is a record of what was sent, to whom and with what result, which can be compared with the orders.
What the server sends is the event (purchase, checkout start, basket, product view), its value and its contents, and some identifiers that let the platform match it to a click on an ad: the click identifier that arrived in the URL and customer data first converted into a hash, a fingerprint that cannot be read as an email address or a phone number.
Deduplication: so it is not counted twice
The recommended approach is not to switch off the pixel, but for browser and server both to send. That way the platform receives from the browser what only the browser knows and from the server what the browser loses. But then the same purchase may arrive twice.
It is solved with an event identifier: the pixel and the server send the same purchase with the same identifier, and the platform, seeing two identical notifications, counts one. If the identifier does not match or is missing, sales are duplicated and the dashboard goes from showing fewer purchases than the real number to showing more. It is the most common mistake in hand-built installations, which is why it is worth checking with a test order.
Consent: the server is not a shortcut
Sending from the server does not change what you can do with a person's data. If the customer rejects advertising cookies, that decision applies to what the server sends too. A correct setup reads the customer's consent, respects it and passes it on to each platform, for example with Consent Mode v2 in Google's case.
Two ways of setting it up in PrestaShop
Google Tag Manager server container
As well as the web container almost everyone knows, Google Tag Manager has a server container. It is hosted on a cloud server, receives the events from the store and forwards them to each platform through tags that are configured there.
- Pros: a great deal of flexibility, it works for any website and not just the store, and if your team already works with Tag Manager the environment is familiar.
- Cons: you have to pay for and maintain that server, configure a subdomain, the tags for each platform and the store's data layer, and keep an eye on it still working after every change. It is a technical project with a cost that never ends.
Module in the store and managed relay
The other way is for a PrestaShop module to capture the events where they happen, in the store itself, and deliver them to a service (relay) that takes care of sending them to each platform, with its own queue and retries. There is no server to set up and no container to maintain.
- Pros: it is up and running quickly, the events come from the real order data and someone looks after the server for you.
- Cons: it does what the module and the service support; if you need very specific transformations or want to measure other websites with the same infrastructure, it is less flexible.
When each one is worth it
| Your situation | What usually fits |
|---|---|
| You have a technical team or agency that already maintains Tag Manager and several websites | Server container |
| You need custom transformation rules for each event | Server container |
| You run the campaigns yourself and do not want to maintain a server | Module and managed relay |
| You want to see, order by order, what was delivered to each platform | Module and managed relay |
How to solve it in PrestaShop
The RKR API Conversions Pro module, which appears in the shop as “Conversions API for PrestaShop”, captures the events of the whole funnel, from the product listing to the purchase, and signs them before sending. It includes deduplication with the pixel, Consent Mode v2, a wizard that guides you platform by platform with a “Save and test” button that sends a real event, health traffic lights and a daily reconciliation that compares orders with the deliveries to each platform. It is compatible with PrestaShop 1.7.8 to 9.2.
Delivery is handled by RKR Relay, our server-side conversions service: it receives the events from the store and delivers them to Meta, GA4, Google Ads, TikTok and the other platforms from our server, with an encrypted queue, retries and the status of every delivery. Only hashed identifiers travel to the relay. There are three plans depending on events per month, at €19, €39 and €79 a month + VAT, with no minimum term, with installation and configuration of the module included.
Frequently asked questions
What is server-side tagging?
It means sending measurement events (purchases, baskets, visits) to the ads and analytics platforms from a server, instead of doing so only from the visitor's browser.
Do I need Google Tag Manager to do server-side tracking in PrestaShop?
No. The Tag Manager server container is one of the ways; the other is a module in the store that sends the events directly or through a relay.
Does server-side tracking replace the pixel?
It complements it. The usual approach is to keep both and deduplicate with a shared event identifier, so that each purchase counts only once.
Does server-side tracking do away with the cookie banner?
No. The customer's consent applies just the same to what is sent from the server; what you gain are the conversions lost to technical causes.