One module. Every ad platform, fed clean.
Your conversions don’t live in one place — they live in GA4, in Google Ads, in Meta. PrestaSignal captures every PrestaShop event once, server-side, and forwards it to each platform in the exact shape it expects. One install, every destination accurate.
Reports that finally reconcile with your orders.
- Real session continuity
- Tax-inclusive revenue
- Cross-device user_id
Conversions Smart Bidding can actually optimise on.
- Enhanced Conversions
- gclid / gbraid / wbraid
- Dynamic remarketing
The conversions iOS 14 took, recovered server-side.
- Conversions API
- Pixel deduplication
- Token kept server-side
Captured once, shared everywhere
Most stores bolt a separate tag on for each platform, and each one loses a different slice of data. PrestaSignal reads the event a single time on your server, hashes the PII, and fans it out — so GA4, Google Ads and Meta all see the same complete, deduplicated truth.
Why one server beats a tag per platform
The usual way stores track conversions is to add a separate snippet for each destination: a GA4 tag, a Google Ads tag, a Meta pixel. Every one of those runs in the shopper’s browser, and every one loses a different slice of data to ad-blockers, iOS restrictions and inconsistent firing. Three tags means three different versions of the truth, none of them complete.
PrestaSignal flips the model. The PrestaShop module captures each event once, on your server, the moment it happens — a product view, an add to cart, a completed order. That single, authoritative event is normalised, has its personal data hashed, and is then forwarded to every platform you’ve connected through your hosted tracking server. GA4, Google Ads and Meta all receive the same event, shaped to each one’s requirements, carrying a shared ID so nothing is double-counted.
The result is consistency you can’t get from browser tags: one source of truth, fanned out to every platform, resilient to the privacy changes that quietly break client-side tracking. Add a platform later and the events you’re already capturing simply start flowing to it — no new snippet, no new point of failure.
Two ways to track, side by side
- A separate browser snippet for each destination
- Each tag loses a different slice to blockers and ITP
- Platforms disagree on how many sales you made
- Adding a platform means adding another point of failure
- Events captured once, server-side, beyond blockers
- The same complete event sent to every platform
- Shared IDs keep numbers reconciled and deduplicated
- New platforms reuse the events you already capture
More platforms on the way
The same server-side pipeline extends to other destinations. These are next:
Platform coverage — questions.
Do I need a separate setup for each platform?+
No. One PrestaShop module and one tracking server cover GA4, Google Ads and Meta together. Each platform’s connection is configured on the server we host, so you don’t wire up three integrations yourself.
Can I run just one platform to start?+
Yes. You can enable only the platforms you use today and add others later — the same captured events simply start forwarding to the new destination once it’s connected.
Are the conversions deduplicated across platforms?+
Yes. Each event carries a shared ID, so a purchase seen by both a client-side tag and the server-side send is counted once per platform, not twice.
Which platforms are supported right now?+
GA4, Google Ads and Meta Conversions API are live today. Microsoft Ads, TikTok and Pinterest are on the roadmap and use the same server-side pipeline.
Connect every platform from one place.
Book a free teardown and we’ll map which platforms you’re losing data on today.