Magento + Google Ads: integration for complex catalogues
Magento, sold as Magento Open Source and Adobe Commerce, has a built-in Google AdWords conversion setting, but nothing native that handles the feed, enhanced conversions, and reconciliation together. Large catalogues make the feed and tracking engineering work: a price-accurate feed, a reliable purchase event, and reconciliation against the store's own sales report.
A 47-point written audit of your Google, Meta or Shopping account, back in five business days.
Get your auditBook a callWhat this integration unlocks
- A controlled product feed to Merchant Center for Shopping and PMax
- Purchase conversion tracking suited to a complex checkout
- Dynamic remarketing audiences at catalogue scale
- Enhanced Conversions through a properly built data layer
- Server-side tracking that handles high order volume reliably
Setup steps
- 1
Generate a controlled product feed
Magento's scale means the feed is usually built with a dedicated extension or a custom export rather than a simple app. Ensure it outputs GTINs, accurate pricing including tier and catalogue price rules, availability, and custom labels.
Catalogue price rules and multiple store views are the classic Magento trap: the feed must reflect the price and currency a shopper actually sees, not a base price. Googlebot crawls landing pages and compares them with the feed price, and products with a mismatch may be disapproved.
- 2
Build a clean data layer
Magento has a built-in option at Stores > Settings > Configuration > Sales > Google API > Google AdWords: enable it, enter the conversion ID and label, and set Conversion Value Type to Dynamic so the order amount is passed. It fires on the Success page. The built-in Google Tag Manager option is only in Adobe Commerce, so Magento Open Source stores need an extension or theme work for GTM.
For anything beyond a basic purchase tag, implement a data layer that exposes order value, transaction ID, currency, and product data at the Success page. Because Magento checkouts are frequently customized, verify the success event fires reliably across payment methods, including redirect-based gateways that can drop the user back on a non-standard page.
- 3
Deploy server-side conversion tracking
For a high-volume Magento store, server-side tracking gives you one controlled source for the purchase event. A server-side GTM container or a direct server-to-server integration captures the purchase and forwards a deduplicated conversion to Google Ads.
It is a choice, not a requirement. It earns its keep where redirect-based payment gateways make the Success page unreliable, or where several tags are firing purchase events and need to be collapsed into one.
- 4
Wire Enhanced Conversions and offline imports
Pass email, phone, name, and address from checkout into enhanced conversions, which hashes them with SHA256 before sending, to improve conversion matching. For B2B or high-consideration Magento stores, also import confirmed or approved orders so they, not just initial checkouts, drive bidding. Google now treats offline conversion import as legacy and recommends Data Manager for conversion imports.
Mind the windows: a conversion matched on GCLID can be uploaded up to 90 days after the click, and one matched on hashed customer data through enhanced conversions for leads only up to 63 days. Orders that take longer to approve than that never reach bidding.
- 5
Reconcile against store revenue
With a complex checkout, discrepancies are common. Reconcile Google Ads reported conversions against Magento's own sales report.
Then apply brand exclusions to Performance Max, which you can do yourself in campaign settings. They cover Search, Shopping, and YouTube search inventory, with an option to keep Shopping ads on brand searches. Our brand cannibalization workflow walks through it.
Common issues
Fix. The feed is exporting base prices while shoppers see catalogue-rule or store-view prices. Correct the feed to output the price and currency the customer actually pays per store view.
Fix. Redirect-based gateways can return users to a non-standard page where the tag does not fire. Ensure the purchase event fires reliably across every payment path, ideally server-side.
Fix. The built-in GTM setting is an Adobe Commerce feature and is not in Magento Open Source. Use an extension or add GTM in the theme, and turn off the built-in AdWords tag if GTM fires the purchase too.
Fix. Uploads must land within 90 days of the click for GCLID matches, or 63 days for enhanced conversions for leads. Send the confirmed order as soon as it is approved instead of batching months later.
Fix. If orders need fulfilment or credit approval, the checkout event overstates revenue. Import the confirmed order as the real conversion, within the upload window.
Common questions
- Adobe Experience League: Magento Open Source 2.4.9 release notes
- Adobe Experience League: Google AdWords
- Adobe Experience League: Sales > Google API
- Google Merchant Center Help: Mismatched product price
- Google Ads Help: About enhanced conversions
- Google Ads Help: Offline conversion imports FAQs
- Google Ads Help: Import offline conversions
- Google Ads Help: Apply brand exclusions to Performance Max or Search campaigns
Want this checked on your own account?
A 47-point written audit of your Google, Meta, or Shopping account. Five business days, no sales call.

