Magento PPC Checklist
Work through these in order. Each one is verifiable on your own store and account, and each one changes what the numbers mean.
| Area | Check | Why it matters |
|---|---|---|
| Feed accuracy | Variant and store-view prices and stock in the feed agree with what the storefront shows for that store view, including tax and currency presentation. | Google requires submitted price and availability to match the landing page, and mismatches lead to disapprovals or suspended items. |
| Purchase event | Purchase tracking is validated against confirmed orders, and transaction IDs are implemented consistently and tested rather than assumed. | Events fired on a checkout success page before payment confirmation inflate conversions and mis-train bidding. |
| Value and currency | Conversion values reconcile to back-office orders for a sample period, each order reports in the correct currency, and the treatment of tax, shipping and refunds is documented. | Bidding optimises against the value you send. If it disagrees with the ledger, every target is measured against the wrong number. |
| Consent and attribution | Consent state is passed correctly, and click identifiers survive guest checkout, payment redirects and any AJAX checkout steps. | Lost identifiers show up as unattributed revenue, which looks like poor campaign performance rather than a measurement gap. |
| Landing pages | Category and product templates are tested on mobile for load, stock display and add-to-basket, on the exact URLs the ads point at. | Landing page experience is one of the components Google reports in Quality Score diagnostics, and a broken template wastes every click. |
| Ownership | Someone is named as owner of the feed, the tracking and the templates before budget is scaled. | Feed and tracking faults are not always visible in the account. Without an owner, nobody is checking for them. |
The feed row follows Google's own requirement that submitted price and availability match the landing page (Merchant Center: price and availability). The landing page row refers to Quality Score, which Google describes as a diagnostic tool rather than an input to the ad auction (About Quality Score).
The Complexity Tax
Magento installations differ from one another. That is the point of the platform, and it comes with a cost that accumulates across integrations, extensions and custom checkout flows.
We call it the "complexity tax": the additional time, cost, and risk required to make things work on Magento that would be straightforward on a more constrained platform.
Magento gives you control. But control means responsibility. Every customisation that improves one thing can break assumptions somewhere else.
Extensions modify behaviour, so an integration that works on a vanilla install can behave differently on a customised one. The practical implication is to test the integration on the actual build rather than trusting a vendor's documentation of the default.
Feed Management Challenges
Product feed generation on Magento requires more than exporting product data. Custom attributes, complex pricing, and multi-store configurations each need a decision. The feed engineering side of this is covered in more detail on our product feed engineering, and how those feeds are then traded sits with Google Shopping management.
Custom Attributes
Magento's EAV model allows unlimited custom attributes. Feed tools expect standard fields, so mapping custom attributes to Shopping requirements needs explicit configuration rather than a default export.
Configurable Products
Parent and child structures need careful handling. Which variants are submitted, and how images and prices are inherited, is a commercial decision rather than a technical default.
Multi-Store Complexity
Pricing, inventory and availability can differ per store view. The feed has to reflect the store view a shopper lands on, because Google requires the submitted price and availability to match that landing page (Merchant Center documentation).
Tracking and Attribution
Conversion tracking is worth checking early on a customised Magento build, because a fault here is not always visible in the account. One-page checkouts, custom payment flows and AJAX-heavy experiences all change when and whether a tag fires.
Common Tracking Failures
- •Purchase event fires before payment confirmation
- •Transaction IDs missing or applied inconsistently, so duplicates go unresolved
- •Order values don't treat tax and shipping consistently
- •AJAX checkout doesn't trigger pageview-based tags
- •Guest checkout or a payment redirect loses the click identifier
- •Currency applied inconsistently across store views
Where Server-Side Collection Fits
Start by validating purchase tracking against confirmed orders. A correctly configured browser tag can work. Where a custom checkout loses events, evaluate server-side collection or conversion import alongside your consent and attribution requirements, rather than treating it as a default. Be precise about the mechanism: the Measurement Protocol is a Google Analytics 4 interface. It augments existing GA4 tagging with server-sent events and needs the same client identifiers to join those events to a session. It is not a Google Ads conversions API, and it is not a replacement for on-site tagging. Google Ads conversions are sent through Google Ads' own mechanisms, such as offline conversion imports or a server-side tagging setup.
The Customisation Trap
Every customisation creates maintenance burden, and that burden compounds when Google changes requirements.
Extension Dependencies
Feed extensions depend on core Magento behaviour. When other extensions modify that behaviour, feeds can break in ways that aren't immediately obvious from the account.
Upgrade Fragility
Upgrades can break customisations, which is one reason some sites run older versions for longer. If a version predates the tracking approach you need, that constraint belongs in the plan rather than being discovered mid campaign.
Documentation Gaps
Where custom development was not documented, and the original developer has moved on, working out why something behaves as it does takes time before anything can be changed safely.
Page Speed and Landing Pages
Landing page behaviour affects both what shoppers do and what Google reports back to you.
Page Speed and Quality Score
Landing page experience is one of the components reported in Quality Score. Google describes Quality Score as a diagnostic tool for spotting where ads and pages could be improved, not as an input used in the ad auction (About Quality Score). Treat a slow template as a conversion-rate problem you can measure, and read the diagnostic as a signpost rather than a price list.
JavaScript Bloat
Extensions add JavaScript, and multiple tracking scripts add more. The cumulative effect slows pages and can stop conversion tracking from firing at all.
Working Solutions
Managing Google Ads on Magento successfully means accepting the complexity and building around it:
1. Decide Where the Feed Is Built
A native extension or a dedicated feed platform can both work. What matters is that the chosen route can express variant-level and store-view-level price and availability correctly, and that someone can change a rule without a development cycle.
2. Validate Purchases Against Confirmed Orders
Check that recorded purchases match confirmed orders, and that transaction IDs are implemented consistently and tested. Where a checkout success page can be reloaded or a custom flow drops the event, evaluate server-side collection or conversion import against your consent and attribution requirements.
3. Reconcile Before You Scale
Compare a period of platform-reported conversions and values against back-office orders. Our audit approach starts here for the same reason: the numbers have to be trustworthy before any target is meaningful.
4. Document and Own It
Keep a record of customisations, integrations and workarounds, and name an owner for the feed, the tracking and the templates. On retained accounts this is part of ongoing management rather than a one-off project.
Magento can work well with Google Ads. It asks for more investment in integration quality than a more constrained platform, and that cost is worth naming before budget grows.
Frequently Asked Questions
What does Magento PPC involve that other platforms don't?
Three areas do most of the work: getting the product feed to agree with what the store view actually shows on price and availability, getting a purchase event that fires only on a confirmed order and carries a transaction ID, and getting values and currency to reconcile with the orders in the back office. The rest of Google Ads management is the same as anywhere else.
Why is Google Ads harder to manage on Magento than Shopify?
Magento's flexibility means installations differ from one another. Extensions can modify checkout behaviour, custom attributes need mapping to feed fields, and multi-store views can carry different prices and stock. Shopify's tighter defaults make integrations more predictable. Neither platform is better for Google Ads in itself; what matters is whether feed, tracking and landing pages are correct.
How do I fix conversion tracking on a heavily customised Magento site?
Start by validating purchase tracking against confirmed orders. A correctly configured browser tag can work. Where a custom checkout loses events, evaluate server-side collection or conversion import alongside your consent and attribution requirements. Transaction IDs need to be implemented consistently and tested, rather than assumed to de-duplicate every refresh or retry. The Google Analytics 4 Measurement Protocol is a GA4 interface: it supplements your existing GA4 tagging with server-sent events and requires the same client identifiers. It is not a Google Ads conversions API and it does not replace on-site tagging.
Is Adobe Commerce better for Google Ads than open-source Magento?
Adobe Commerce is the licensed edition with vendor support, and the integrations available to you depend on the edition and the build in front of you. The same feed, tracking and landing page work applies to both. How the implementation was built matters more than the licence.
Running Magento or Adobe Commerce?
If you want a second read on the feed, the tracking and what the account is actually being measured against, see what our Magento PPC management covers across Search, Shopping and Performance Max.
Book a commercial reviewGet our insights in your inbox
Plain-English thinking about Google Ads. No spam, unsubscribe anytime.