Stop bidding on conversions Google can’t see.
Smart Bidding is only as smart as the conversions you feed it. When iOS and ad-blockers hide your sales, Google optimises toward the wrong people. PrestaSignal sends clean, server-side conversions — with Enhanced Conversions and the click IDs that keep attribution intact.
Lost conversions quietly wreck your bidding
Every conversion the browser fails to report is a signal Smart Bidding never receives. Over weeks, that teaches Google to chase cheaper, lower-intent clicks — and your ROAS slides without an obvious cause.
Enhanced Conversions, click IDs, and remarketing — server-side
PrestaSignal captures gclid, gbraid and wbraid (for iOS app-to-web and web-to-app journeys) so conversions attribute correctly, and sends Enhanced Conversions with hashed email, phone and name for stronger matching. It also feeds dynamic remarketing with the right page type and Merchant Center product IDs, so your remarketing audiences stay accurate.
What reaches Google Ads
How Google Ads server-side conversions work on PrestaShop
On the click that brings a shopper to your store, the module captures and persists the Google click identifiers — gclid for standard clicks, and gbraid or wbraid for iOS app-to-web and web-to-app journeys where gclid isn’t available. When that shopper converts, the purchase is sent to Google Ads from your server together with the stored click ID, so the conversion attributes back to the exact ad interaction that earned it.
Alongside the conversion, the module sends Enhanced Conversions: the customer’s email, phone and name, normalised and SHA-256 hashed on your server before they ever leave it. Google matches that hashed data to the originating click, recovering conversions that cookies alone would miss on iOS and privacy-restricted traffic. The same server pipeline feeds dynamic remarketing with the correct page type and Merchant Center product IDs, keeping your audiences populated and accurate.
What lost conversions cost you
Smart Bidding optimises on the conversions it sees. Hide a third of them and it learns to chase the wrong clicks.
Conversions the browser never reported make profitable campaigns look unprofitable, tempting you to cut spend that works.
Without gbraid and wbraid, iOS conversions detach from their click and land as untracked.
Dropped events starve your dynamic remarketing audiences, so you re-reach fewer of the right people.
Google Ads server-side — questions.
What are Enhanced Conversions and do I need them?+
Enhanced Conversions send hashed first-party data (email, phone, name) alongside a conversion so Google can match it more accurately. PrestaSignal hashes that data on your server and includes it automatically — it materially improves measurement on iOS and privacy-restricted traffic.
Does this capture gclid for attribution?+
Yes — gclid, plus gbraid and wbraid for iOS app-to-web and web-to-app journeys. They’re persisted and sent with the conversion so Google attributes it to the right click.
Can it power dynamic remarketing?+
Yes. The module sends the page type and Merchant Center-formatted product IDs needed for dynamic remarketing audiences, so they stay populated and accurate.
Is the Google Ads side configured for me?+
Yes. Your conversion IDs, labels and remarketing setup are configured on the tracking server we host and maintain.
Do I need to change my existing Google Ads conversion actions?+
No. We map your existing conversion actions and labels to the server-side events. You keep the conversions you’ve already set up — they simply start receiving cleaner, more complete data.
Is hashed customer data safe to send for Enhanced Conversions?+
Yes. Email, phone and name are normalised and SHA-256 hashed on your server before transmission, so Google receives only irreversible hashes — never the raw values. This is exactly how Enhanced Conversions is designed to work.
Give Smart Bidding the full picture.
A free teardown shows how many conversions your Google Ads account is currently missing.