PrestaSignal
How it works

How a sale gets counted — in five pictures.

You should not need an analytics degree to know whether your ad money is working. The questions store owners actually ask are simple ones: where do my missing sales go? What happens when a browser blocks tracking? Will anything ever be counted twice?

The five pictures below answer them by following one shopper from ad click to refund. Two things to keep in mind as you scroll: everything the browser sends travels through your own website address, and the sale itself is reported by your shop's back office — the browser is not involved at all.

The journey

What happens when someone shops

One shopper's journey in five steps: ad click, your shop, browsing, purchase, refund handled. Under the shop step: everything loads from your address. Under the purchase step: reported by your back office.Ad clickYour shopBrowsingPurchaseRefundhandledeverything loadsfrom your addressreported by yourback office
One shopper's journey, start to finish. The steps a browser can lose — the visit, the product pages, the cart — are carried by your own address instead of a third-party one. The sale itself never depends on the browser at all: your back office reports the purchase, and if the order is later refunded, the refund follows the same browser-free road.
The old way

Why the old way loses sales

Traditional tracking: the shopper's browser sends events to google-analytics.com, and an ad blocker cuts the connection before it reaches GA4, Google Ads and Meta. A clock badge notes that Safari deletes script-set cookies after 7 days.Shopper'sbrowserGA4 · GoogleAds · Metagoogle-analytics.com✂ad-blocker filter lists targetGoogle's domainsSafari deletes script cookies after 7 days(WebKit policy)
Traditional tracking asks the shopper's browser to call Google's own domains — exactly the addresses ad-blocker filter lists are built to cut. Roughly 3 in 10 internet users run an ad blocker (GWI, 2025). And on Safari, Apple's WebKit rules delete script-set cookies after 7 days, so even a shopper who comes back to buy is counted as a brand-new stranger.Sources: ad-block usage — GWI 2025, via Backlinko · WebKit tracking-prevention policy.
The new way

How PrestaSignal routes it

PrestaSignal routing: the shopper's browser talks to a connector on your own shop address, which passes events to a tracking server we run, which delivers them to GA4, Google Ads and Meta. A separate lane shows your back office sending purchase and refund straight to the tracking server, without the browser.Shopper'sbrowseryour-shop.com/connectorTracking serverwe run it for youGA4Google AdsMetaYour backofficepurchase & refund —server to server
Everything the browser sends goes to your own address first — a small connector the module places there automatically — then on to a tracking server we run, which hands it to GA4, Google Ads and Meta. Your sales travel a second, browser-free road: the back office reports every purchase and refund server to server. Today's filter lists target Google's domains; here, everything loads from yours.
No double counting

Counted once, everywhere

Deduplication: a browser pixel and a server event both carry the tag order #1042 into the ad platform, which counts the purchase exactly once.Browser pixelServer eventorder #1042order #1042Ad platformcounted once
A purchase can reach a platform twice — once from the shopper's browser, once from your back office. Both copies carry one shared ID that is built from the order itself, so a reload can never double-count. The platform sees the same ID on both and keeps exactly one — your revenue is never inflated.
Consent

Consent is respected

Consent handling: the visitor's consent choice travels with every event. Granted leads to full detail; declined is respected and modeled by Google.Visitor'schoiceconsent travelswith every eventgrantedfull detaildeclinedrespected —modeled by Google
Your consent banner stays in charge. Whatever the visitor chooses rides along with every event: granted means the platforms get full detail; declined means no personal data leaves, and Google fills the statistical gap with its own modeling. Consent is forwarded exactly as given — never rewritten.
Good to know

Questions owners ask.

Do I have to host anything?+

No. The tracking server is a managed server we run for you — we operate it, update it and connect it to your ad platforms. On your side there is only the module, and it installs like any other PrestaShop module.

How long does it take to go live?+

Minutes. You upload the module ZIP, paste the license key we send you, and the module sets everything up — including the small connector on your own website address. No code, no tag containers, no developer needed.

What if the shopper's browser blocks tracking?+

The sale is still counted. Browsing events travel through your own address — today's filter lists target Google's domains, not yours — and the purchase itself is reported by your back office, so it never depends on the browser in the first place.

Which PrestaShop versions are supported?+

PrestaShop 1.7 → 9. The module uses PrestaShop's standard hooks and is production-verified on PrestaShop 9, so it runs alongside your existing theme and modules without touching core files.

Can an order ever be counted twice?+

No. Every purchase carries an ID built from the order itself, so a reload of the thank-you page can never double-count. And when the same purchase arrives from both the browser and the server, that shared ID tells the platform to keep exactly one.

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 →