No click id, no conversion
Google Ads attributes on gclid, or on gbraid and wbraid when the journey came through an app or a restricted-cookie browser. A conversion sent without one of them is not attributed to anything: it is discarded, silently.
PrestaShop module + Google Ads Data Manager API, EU-hosted
Google Ads conversion tracking for PrestaShop, click id included
A native PrestaShop module that sends the validated order to Google Ads from your server, carrying the click id captured when the visitor arrived. Without a gclid, gbraid or wbraid attached to the conversion, Google Ads cannot attribute the sale to the campaign that paid for it, and the conversion is simply ignored.
The problem
Why Google Ads under-reports PrestaShop conversions
A Google Ads conversion is only useful if it carries the click that produced it. On a PrestaShop checkout, that click id has several chances to disappear before the order is validated.
The click id arrives, then evaporates
The visitor lands with ?gclid=..., browses, comes back a week later, pays. If nothing stored that value at arrival and carried it to the order, it is gone by the time the purchase happens.
iOS and in-app journeys send something else
Google increasingly delivers gbraid or wbraid INSTEAD of gclid. An integration that only knows the word gclid loses exactly the traffic that is hardest to measure.
The fix
Captured on arrival, carried to the order, sent from the server
The module stores the click id in a first-party cookie the moment the visitor lands, and reads it back when PrestaShop validates the order. The conversion leaves your server with its click id attached.
All three click ids, not just gclid
gclid, gbraid and wbraid are captured, plus msclkid for Microsoft Advertising. Whichever one Google chose to send, the conversion carries it.
Carried by the server path, not the beacon
The purchase event built at order validation reads the stored click id server-side. It does not depend on a browser beacon an ad blocker can remove, which is the case the click id matters most.
OAuth, no token to paste
You connect the Google account that manages your Ads once, and the refresh happens on our side. Your PrestaShop database never holds a Google credential.
Setup
Three steps, and Google Ads starts receiving
-
Install the connector
A standard ZIP in the module manager, PrestaShop 1.7 and 8. No core override, no theme change, nothing added to your checkout.
-
Paste your connection key
One key from your DataFirefly console identifies the site. It is the only thing your shop holds: no destination credential ever lives in your store.
-
Add Google Ads as a destination
Your Google Ads settings go into the console, stored encrypted on our side. Rotating them later touches nothing in the shop.
The same connector feeds every other destination from the same events, so Google Ads is a starting point rather than a silo. See the PrestaShop connector in detail or Google Ads across all platforms.
Same connector
Your other destinations from PrestaShop
One installation, one key. The events you already send reach every destination you switch on.
Pricing
Included in every plan, free plan included
10,000 events a month free, no card. Paid plans from 39 €/month when your volume grows. Every destination is included in every plan: Google Ads is never an add-on.
FAQ
Frequently asked questions: PrestaShop and Google Ads
Why does Google Ads show fewer conversions than PrestaShop shows orders?
Almost always because the conversions arrive without a click id. Google Ads attributes on gclid, gbraid or wbraid; a conversion without one cannot be tied to a campaign and is dropped. The module captures the click id when the visitor arrives, stores it in a first-party cookie, and attaches it to the purchase built at order validation.
What are gbraid and wbraid, and why do they matter?
They are the click ids Google sends INSTEAD of gclid when the journey crosses an app or a browser with restricted cookies, iOS in particular. An integration that only handles gclid quietly loses that traffic. The module captures all three, and the dispatcher has validated them since day one.
Do I need to create conversion actions in Google Ads?
Yes, and you map them once in your DataFirefly console: our event name to your conversion action. Events without a mapping are skipped rather than sent to a wrong action, because a conversion attributed to the wrong thing is worse than a missing one.
Do I have to paste a Google API token into PrestaShop?
No. You connect your Google account with OAuth from the console, and the token lives encrypted on our side. Your shop only holds the connection key. That is also what lets you revoke access without touching the module.
Does Enhanced Conversions work with this?
Yes. The validated order gives hashed email and phone alongside the click id, which is what Enhanced Conversions uses to recover attribution when the click id alone is not enough. Hashing happens in your shop, before anything leaves.
Which PrestaShop versions are supported?
PrestaShop 1.7 and 8, installed as a standard ZIP from the module manager. No core override, no theme change, and the click-id capture works on the default themes without touching a template.
Give Google Ads the click id it needs
Install the module, connect your Google account, map your conversion actions. The next order that came from an ad will carry the click that paid for it.