Send PrestaShop purchase conversions with revenue data so Google Ads bidding learns from real orders
Google Ads is a module for PrestaShop stores that reports every purchase to Google Ads with its real paid value and currency, so bidding optimises on truth. Setup is copying two values from the Ads account, the conversion identifier and the purchase label, into the store's panel.
Google Ads is the advertising platform itself: campaigns, budgets and bidding stay in your Google account, and its automated bidding decides how much a click is worth based on the conversions it receives. That is exactly why the conversion data must be right; a campaign fed wrong numbers spends the budget in the wrong places.
The module is simple to start and precise where it counts. You control whether the purchase event fires, whether the order value travels with it, whether hashed customer data improves matching, whether consent gates the tag, and whether staff sessions are excluded; the last three are on from the start. Each order carries its transaction identifier, so a refreshed confirmation page never becomes a second conversion, and a customer returning from the payment provider by a detour still produces exactly one.
The purchase event carries the tax-included total, the currency and the items with their names, quantities and prices. The module also recognises a Google tag already loaded by your theme or another module and does not insert a second one, which removes the most common cause of doubled conversions. In a multistore, each shop uses its own conversion identifier. The readiness panel in the store's own settings states plainly whether everything is in place to fire.
Bidding learns from the order book instead of a sample of it, budgets flow to the campaigns that sell, the agency audit ends with a tag that is simply correct, and consent enforcement keeps the measurement itself defensible.
Summary of what the module offers
Google Ads makes the one number that steers your advertising, the purchase conversion, arrive complete and correct. The map below covers the six sections.
- The purchase reported with real paid value, currency and items
- No double counting: transaction identifiers and duplicate-tag detection
- A conversion that survives the customer's detour back from payment
- Better matching through hashed customer data
- Consent respected before anything fires, staff sessions excluded
- Two-field setup with a readiness panel that says what is missing
What does Google Ads learn about a sale?
Everything bidding needs: the purchase, its tax-included paid total, its currency and the items in the order with their names, quantities and prices. Value-based bidding stops treating a 900 euro order and a 9 euro order as the same event.
The value travels with each conversion automatically; there is nothing to calculate and nothing to maintain when prices or currencies change.
Why does nothing get counted twice?
Each conversion carries the order's transaction identifier, so a customer refreshing the confirmation page, or opening it again from an email, still counts once. That deduplication is on from the first day.
The module also detects a Google tag that your theme or another module already loads and does not insert a second one, which removes the most common cause of silently doubled numbers in an audit.
What happens when the customer takes a detour?
Payment providers send customers back along winding paths, and a confirmation page that never renders normally is a conversion that never fires. The module notes the order the moment it is validated and completes the report when the customer lands back in the shop.
The sale that was hardest to win, paid and confirmed, is exactly the one that no longer disappears from the campaign that produced it.
What about conversions browsers hide?
Browser privacy features cut the thread between click and purchase for a share of customers. With enhanced matching enabled, the module sends hashed customer data alongside the conversion, and Google matches the purchase to the click on its side.
The hashing happens before anything leaves the shop, so what travels is a fingerprint for matching, never readable personal data.
How do consent and setup work?
The tag waits for the visitor's marketing consent and cooperates with the shop's consent banner; a visitor who declines is never measured. Staff sessions are excluded from the start, so your own team's test orders stop training the bidding.
Setup is two values copied from the Ads account. Until they are in place the module names what is missing, and the readiness panel confirms, check by check, that the tag will fire. In a multistore, each shop uses its own conversion identifier.
-
Referencemprgoogleads
-
In stock2147483647 Items
-
PrestaShop CompatibilityPS 1.6 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeFront-office
-
GDPR RelevantYes
-
Business GoalMarketing & Retargeting
-
External Account NeededYes
-
Module ComplexityLightweight Widget
-
Customer Journey StageAttract Visitors
-
Works With PlatformGoogle Services
What customers say about us
Company reviews
5.0
★
★
★
★
★
(4 reviews)
Loading customer reviews...
No product reviews yet
Be the first to share your experience with this module.
Write a Review
MPR Google Ads adds direct Google Ads conversion tracking to your PrestaShop store, including purchase value, currency and order transaction ID. Use it when you want Google Ads conversions through gtag.js without managing the purchase tag in Google Tag Manager.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1301
questions
9
categories
2013
building modules since
1.6–9
PrestaShop versions
v1.0.02026-05-20
- AddedGoogle Ads product listing content, product documentation, recommended module links, and product-page changelog metadata.
- Documents direct Google Ads purchase conversion tracking with value, currency, transaction reference, and optional enhanced conversion data.
- Clarifies when to use this standalone module versus Google Analytics GA4, Google Tag Manager, and Social Revolution.
Loading full changelog...
Works Well With Google Ads
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Complement
Running the Google Ads module, your store sends purchase signals from order confirmation directly into Google Ads through a Conversion ID and purchase label, giving campaigns clear revenue feedback from paid orders. That focused conversion feedback is most powerful for Shopping campaigns, which depend on structured product data that the Ads conversion module itself neither generates nor organises.
Smart Google Merchant Feed Manager is a separate module that generates and shapes product data for Google Merchant Center, with separate feed profiles for markets, languages, currencies, target countries and sync modes, and can publish protected XML feed links. It handles the catalogue side that Shopping ads rely on to show the right products at the right prices.
Used together, they let you supply well-structured product data to Merchant Center while sending clean purchase conversions to Google Ads, two complementary tools covering feed and conversion tracking. The payoff is that paid-product campaigns rest on both organised catalogue data and dependable revenue signals: your feed is disciplined and market-appropriate, your conversions are focused and accurate, and each side of a Shopping campaign is looked after by the tool built for it.
Measurement
With the Google Ads module running, your store sends focused purchase conversions from order confirmation into Google Ads, which is exactly enough to give campaigns clear revenue feedback from paid orders. That conversion signal is narrow by design, though: it reports purchases but does not give you a broad reporting home for everything that happens across the funnel before a shopper buys.
Google Analytics GA4 is a separate module that sends ecommerce activity to your GA4 property after validating the Measurement ID, covering product views, cart activity, checkout starts, purchases, searches, logins and account creation. It provides the wider funnel and cross-channel reporting that a purpose-built purchase conversion does not attempt to cover.
Used together, they let you keep a clean purchase-conversion path into Google Ads while GA4 shows how paid traffic behaves on the way to buying, two complementary tools serving different needs. The payoff is that campaign optimisation and full-funnel analysis each have the right data source: Ads gets the focused conversion it needs to bid on, GA4 gives you the behavioural and cross-channel view you need to understand and improve the journey.
Workflow
A store using the Google Ads module keeps a deliberately focused setup: a Conversion ID and purchase label sending order-confirmation conversions into Google Ads. That is ideal when a single clean conversion is all you need, but as a store grows it tends to add more tags over time, and those benefit from organised, event-aware delivery rather than being scattered as loose snippets across the theme.
Google Tag Manager is a separate module that adds your GTM container and feeds it GA4-formatted ecommerce events from real shopping behaviour, giving surrounding marketing and analytics tags a consistent delivery layer while your focused Ads conversion stays exactly as it is.
Used alongside the Google Ads module, GTM lets you keep the direct purchase conversion simple while managing the broader tag landscape through a container, two complementary tools with distinct jobs. The payoff is a setup that stays clean as it scales: your Ads signal remains focused and reliable, the rest of your tracking sits in a tidy, maintainable structure, and adding future tags no longer means threading more snippets through your theme by hand.
Governance
Because the Google Ads module tracks purchase conversions and sends signals to Google Ads, a store using it is processing marketing data EU visitors should be able to accept or decline. The module tracks conversions; it does not present and enforce a consent choice, so on its own it leaves you without a reliable way to hold marketing tracking until a shopper has actually agreed.
Cookies Revolution is a separate consent manager that collects and enforces choices for necessary, functional, analytics and marketing cookies. It rewrites matching external and inline scripts before consent, reactivates allowed ones afterwards, records each decision, and connects categories to Google Consent Mode v2 signals, which apply to Google Ads, GA4 and Google Tag Manager.
Used alongside the Google Ads module, it lets you gate marketing scripts until a shopper agrees and reflect real choices through Consent Mode, two complementary tools handling tracking and consent separately. The payoff is that your Ads conversion tracking runs on a consent-respecting foundation: you keep measuring the shoppers who opt in, you can evidence how consent was captured, and you are not managing consent by hand around your conversion setup.
Loading feature requests...
30 days return right
Easy return - no questions asked
Plug & Play Modules
Install, set up and take profit
Dedicated Support First
Priority Help & Satisfaction Over Sales
You might also like
