What recovering your tracking actually looks like.
Picture a PrestaShop store doing solid revenue on Google and Meta ads, with a competent client-side setup. On paper everything looks fine — until the conversions reported in GA4 and Ads Manager are lined up against the actual orders in the back office, and they don’t match. Here is why that gap exists, what closing it changes, and why the mechanism — not a percentage — is the part that transfers to your store.
Before: the numbers don’t add up
The store’s analytics consistently shows fewer purchases than its order list. The mechanics are no mystery: ad blockers cancel requests to Google’s analytics domains before they leave the browser — roughly 3 in 10 internet users run one (GWI, 2025) — and Safari deletes script-set cookies after 7 days under Apple’s own WebKit policy, so returning iPhone shoppers come back looking like strangers. The undercount is biased, too: the missing sales cluster in exactly the iOS-heavy, privacy-conscious audiences many stores value most, and Smart Bidding and Meta’s optimisation learn from data that is missing them.
What changes
Nothing about the store’s ads or products changes. The only difference is where the tracking lives — and which road each event travels.
The PrestaSignal module goes onto the store — a ZIP and a license key, no theme edits, no developer sprint. It provisions everything, including a small connector on the shop’s own web address.
Page views, product views and cart steps are recorded through that connector — the shop’s own domain — with the Google tag libraries served from the same address. Today’s blocker filter lists target Google’s domains; nothing on the page matches them.
Purchases and refunds are reported by the back office, server to server, and counted exactly once — a closed tab, a reload or an extension can no longer lose or double a sale.
Click IDs are kept for 90 days in consent-gated first-party cookies, Enhanced Conversions and the Conversions API carry hashed match data, and shared event IDs keep every platform’s count clean.
The result: platforms finally see what the back office knew
Once the browser events travel first-party and the sales report themselves server-side, the platforms start seeing conversions they were blind to. That is not new revenue — it is the real sales the store was already making, finally measured. How much is recovered depends on the store’s audience: the more iOS traffic and ad-blocker use, the larger the hidden share. That is why this page shows proportions rather than percentages — no verifiable industry average exists, and we would rather measure your store than invent a number for it.
What makes this repeatable is that the cause is universal: every PrestaShop store selling to iPhone users and shoppers with ad blockers loses conversions the same way, for the same reasons. The size of the gap differs; the mechanism — browser tags blocked, script-set cookies cut short — is the same everywhere. That is why the same first-party, server-side design produces the same shape of result across very different stores.
About this example.
Is this a real, named customer?+
No — it’s an illustrative walk-through of the mechanism, deliberately free of invented figures. A measured case study from a live store, with a real before-and-after, is in the works. Until it’s published, we’d rather show you the mechanism honestly than dress a hypothetical up as data — and a free teardown gives you figures specific to your store.
Why show proportions instead of percentages?+
Because no verifiable industry average exists for how much client-side tracking loses — it depends on your audience’s devices, browsers and ad-blocker habits. What is citable: roughly 3 in 10 internet users run an ad blocker (GWI, 2025), and Safari deletes script-set cookies after 7 days (Apple’s own WebKit policy). Your store’s exact number is measurable — on your store, against your real orders.
Will I see the same result?+
The shape, yes — recovered purchases, restored attribution, reports that reconcile with your back office. The size depends on how much of your traffic is on iOS, how many shoppers use blockers, and which platforms you run. The free teardown estimates your specific gap before you commit to anything.
Want real numbers instead?
A free teardown measures the gap on your actual store — your orders, your traffic, your platforms — before you commit to anything.