Magento + Google Ads: integration for complex catalogues
Magento, now Adobe Commerce, powers large, complex catalogues where feed generation and tracking are engineering problems, not plugin toggles. There is no single native channel that does everything, so the setup is deliberate: a robust feed, server-side conversion tracking, and reconciliation against the store's real revenue. This guide covers the approach iClick uses.
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, or Merchant Center will flag price mismatches.
- 2
Build a clean data layer
Implement a data layer that exposes order value, transaction ID, currency, and product data at the success page. On Magento this often requires developer work in the theme or a tag-management module.
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 is the reliable path. A server-side GTM container or a direct server-to-server integration captures the purchase and forwards a deduplicated conversion to Google Ads.
Server-side is also more resilient to the caching and performance layers common on large Magento deployments, which can interfere with client-side tags.
- 4
Wire Enhanced Conversions and offline imports
Map hashed email and phone from checkout into Enhanced Conversions to recover privacy-limited conversions. For B2B or high-consideration Magento stores, add offline conversion import so confirmed or approved orders, not just initial checkouts, drive bidding.
This matters where orders pass through fulfilment or credit approval before they are real revenue.
- 5
Reconcile against store revenue
With a complex checkout, discrepancies are common. Reconcile Google Ads reported conversions against Magento's own sales report, and apply brand exclusions so PMax does not inflate its ROAS on branded search.
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. Large Magento stacks with full-page caching can interfere with client-side tags. Move critical conversion tracking server-side for reliability.
Fix. If orders need fulfilment or credit approval, the checkout event overstates revenue. Use offline conversion import to send the confirmed order as the real conversion.
Common questions
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.
