PrestaSignal
How it works

Server-side tracking, without the server headache.

Most “server-side tracking” guides end with you hosting a Google Tag Manager server, wiring up SSL, and babysitting uptime. PrestaSignal does the opposite: you install one module, we run everything else. Here is exactly what happens to your data on the way from a sale to your ad platforms.

The architecture

Three moving parts, one of them yours.

A PrestaShop module on your store builds the events. A tracking server we host and configure receives them. Your ad platforms get the clean result through their official server-side APIs. You only ever touch the module — the rest is operated for you, so there is no container to deploy, no SSL to renew, and nothing to keep online at 3am.

In the moment of a sale

What happens in the half-second after “buy”.

A single conversion travels a short, deliberate path — and at no point does it depend on the visitor’s browser cooperating.

1
A customer checks out

The order is placed on your PrestaShop store. This is the source of truth — it happens whether or not any browser pixel survives.

2
The module builds the event

PrestaSignal hooks the order, assembles a clean GA4 purchase event with items, revenue and a deterministic event ID, and reads the real session so it joins the right journey.

3
Personal data is hashed

Email, phone and name are normalised and SHA-256 hashed on your server. Raw details never leave the building.

4
It is sent to your server, not the browser

The event is posted server-to-server to your hosted tracking server in a few hundred milliseconds — invisible to ad-blockers and ITP.

5
Your platforms receive the truth

GA4, Google Ads and Meta’s Conversions API each get the conversion, deduplicated against any browser event by its shared ID.

Hybrid by design

Client and server, counted once.

Run server-side only, or in hybrid mode alongside a browser tag. In hybrid mode the same event is sent from both sides with a shared event ID, and GA4 and Meta’s Conversions API use that ID to deduplicate — so you keep the browser’s rich signals and the server’s resilience, while every conversion is counted exactly once.

Shared event ID → counted once, never twice
Good to know

How it works — your questions.

Do I have to host my own server?+

No. The “server” in server-side tracking is the part most guides make you set up and maintain. PrestaSignal hosts and configures it for you — there is nothing for you to provision, secure or keep online.

What does the module actually do on my store?+

It hooks into PrestaShop’s lifecycle — page views, product views, cart actions, checkout steps, purchases and refunds — builds a clean event for each, hashes any personal data, and posts it to your tracking server. It runs in the background and never blocks page rendering.

Is hybrid mode better than server-side only?+

For most stores, yes. Hybrid keeps the rich signals a browser tag still collects while server-side guarantees the conversions the browser would lose. The shared event ID deduplicates the two, so nothing is double-counted.

How long does it take to go live?+

Minutes. You upload the module, paste your license key, and tracking starts flowing — we pre-configure your server and platform connections before you ever install.

See what your tracking is doing right now.

Book a free teardown and we will show you, event by event, what your store is sending — and what it is silently losing.

Part of the PrestaChamps family →