Magento server-side tracking for Google Ads
Send every purchase from your Magento store view to Google Ads from the server, with the script served from your own domain.
Each purchase is confirmed from your Magento orders and sent to Google Ads from the server, through Google’s Data Manager. Nothing in the browser talks to Google, so an ad blocker has nothing to block.
Prerequisites
- Workspace admin in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking). Google Ads needs Merchant Center connected.
- Magento 2.4, 2.0 or 1.9 / OpenMage and a developer with terminal access to the server: the module is installed with Composer or as a ZIP.
- Magento cron running, and the store-view ID and public HTTPS address of the store view you track.
Set it up with AI
Connect your assistant
First time? Add the Product Metrics MCP server to your assistant, then paste the prompt below.
In Claude, choose Add custom connector; in ChatGPT, Settings → Apps & Connectors. Paste this URL:
https://www.productmetrics.io/mcpClaude Code: run this in your terminal.
claude mcp add --transport http product-metrics https://www.productmetrics.io/mcpPaste the prompt into your assistant.
Set up server-side conversion tracking for my Magento store in Google Ads with Product Metrics. Check my setup status first, walk me through each open step, and give me the link when I need to click something.Set up server-side conversion tracking for my Magento store in Google Ads with Product Metrics. Check my setup status first, walk me through each open step, and give me the link when I need to click something.Set up server-side conversion tracking for my Magento store in Google Ads with Product Metrics. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first), and tell me when a step needs me in a browser.Set up server-side conversion tracking for my Magento store in Google Ads with Product Metrics. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first), and tell me when a step needs me in a browser.In the app
1. Connect Magento and Google Ads
- Store: create the module configuration under Ecommerce platforms → Connect Magento, have your developer install the module, then verify the store view. See Magento.
- Google Ads: under Ecommerce platforms, select your store → Connect Google Ads → Continue with Google, pick the client account that runs your campaigns and grant Data Manager access. See Google Ads.
You should see: under Manage Magento, the connection is Active and your property is linked; Product Metrics lists your Google Ads account under your store.
2. Choose your consent banner
In Product Metrics, open Tracking → Configure consent and choose the banner your shop shows: OneTrust, Cookiebot, Usercentrics or Osano. Magento’s own cookie restriction notice does not grant consent. With any other banner, your developer passes the visitor’s choices to Product Metrics; anything not set stays denied. See Consent.
You should see: Configure consent names the banner your store view actually shows.
3. Create the conversion actions
In Product Metrics, select Tracking → Create Google Ads conversions → Create 8 conversion actions. All eight are secondary, so nothing changes in your campaigns until you make one primary. See Conversion actions.
Then add your additional costs, so the profit actions carry profit.
You should see: the badge next to Tracking reads Tracking active.
4. Check it works
Place a paid test order in the connected store view with your payment provider’s test mode, and allow a few minutes for cron.
You should see: under Manage Magento, the desired and active revision numbers are the same, and the order appears for the linked property. More checks: Check tracking works.
Troubleshooting
Orders are missing in Google Ads
Check that Tracking → Configure consent names the banner your store actually shows: Product Metrics sends an order only with the consent this page lists. See Consent.
FAQ
Do I need a developer for Magento tracking?
Yes, once: a developer with terminal access installs the Product Metrics module with Composer or as a ZIP and makes sure Magento cron runs. Everything after that happens in Product Metrics and Google Ads.
How fast does a paid Magento order reach Google Ads?
Within minutes: the module sends order changes every two minutes through Magento cron, so cron has to keep running.
Does Magento’s cookie notice count as consent?
No. Magento’s own cookie restriction notice does not grant consent. Use OneTrust, Cookiebot, Usercentrics or Osano, or have your developer pass your banner’s choices to Product Metrics; anything not set stays denied.
Are Magento refunds and cancellations sent to Google Ads?
Yes. The module reports refunds and cancellations, and the Google Ads conversion is adjusted.
Where next
- Magento: the full platform setup
- Google Ads: what Product Metrics sends and how to troubleshoot it
- Server-side tracking for Magento in Meta: the same store view, the other channel
- Enhanced conversions for Magento in Google Ads: add hashed customer data
- Server-side conversion tracking: every platform and channel
- On the website: Full Signal Tracking, ad blocker conversion tracking check, first-party cookie, Product Metrics for Magento