> ## Documentation Index
> Fetch the complete documentation index at: https://5332bee-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://5332bee-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://5332bee-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://5332bee-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Magento server-side tracking for Google Ads (/docs/tracking/server-side/magento-google-ads)

<!-- agent-signals: reading_time_min: 10 · est_tokens: 3896 · updated: 2026-11-17 -->
Related: [Shopify server-side tracking for Google Ads](/docs/tracking/server-side/shopify-google-ads.md), [WooCommerce server-side tracking for Google Ads](/docs/tracking/server-side/woocommerce-google-ads.md), [Lightspeed server-side tracking for Google Ads](/docs/tracking/server-side/lightspeed-google-ads.md), [Shopware server-side tracking for Google Ads](/docs/tracking/server-side/shopware-google-ads.md), [Server-side tracking for Google Ads on any website with Cloudflare](/docs/tracking/server-side/cloudflare-google-ads.md), [Shopify server-side tracking with the Meta Conversions API](/docs/tracking/server-side/shopify-meta.md)

> 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](/docs/concepts/server-side-tracking), through Google's **Data Manager**. Nothing in the browser talks to Google, so an [ad blocker](/docs/features/ad-blocker-proof-tracking) has nothing to block.



* **Store:** [Magento](/docs/platforms/magento). The module, installed once by a developer.
* **Channel:** [Google Ads](/docs/channels/google-ads). Your Google Ads account, connected with Continue with Google.
* **Result:** Every paid order sent server-side to the eight **Product Metrics** conversion actions.

## Set it up with AI



Setting it up with AI takes one prompt and 60 seconds: paste it into your assistant.



First connect the Product Metrics MCP server ([https://www.productmetrics.io/mcp](https://www.productmetrics.io/mcp); see [Connect your assistant](/docs/mcp/connect)).

**Claude or ChatGPT:** "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."

**Claude Code or Codex:** "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."

## Prerequisites

* **[Workspace admin](/docs/using/team#1-choose-a-role)** in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking). Google Ads needs [Merchant Center](/docs/using/merchant-center) connected.
* **Your Magento store view connected**: Magento 2.4, 2.0 or 1.9 / OpenMage, Magento Admin access, the public HTTPS shop address and the **store-view ID**, and a **developer** with access to your server who installs the Product Metrics module (Composer or ZIP), adds the store view's private configuration file and keeps Magento cron running. The connection reads **Active** before you link your property. See [Magento](/docs/platforms/magento).

## 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](/docs/platforms/magento).



1. **Open Ecommerce platforms.** Go to **Integrations → Ecommerce platforms** and select **Connect** on **Magento**.

   ![The store platform list in Ecommerce platforms: WooCommerce, Magento, Shopware 6, Lightspeed and Custom Store / Webhook Integration, each with a Connect button, with Magento outlined.](/docs/_assets/5d48e2070be161722db01c31447901650ce87360fe351da6c9b68b7a7e3157ef)

2. **Start the setup.** The Magento page lists three steps: connect your store, install the module and link a property. Select **Connect Magento**.

   ![The Magento page under Integrations → Ecommerce platforms, for Magento 1.9 and 2: 0 of 3 steps done, step 1 Connect your store with the Connect Magento button, then Install the module and Link a property.](/docs/_assets/559ef5687b68660aa29f64600cebe006fdab68ae079bbeeabe7863c7310e5295)

3. **Describe your store.** Choose your **Magento version**, enter the **Store URL** and the numeric **Store view ID**, then select **Create module configuration**. Download the configuration file and share it with your developer privately: it holds a private key.

   ![The Connect Magento dialog: Magento version set to Magento 2, a closed Advanced custom checkout mapping section, empty Store URL and Store view ID fields, and the Cancel and Create module configuration buttons.](/docs/_assets/d99894bd7f20dcd4ce41dfb8621390e9fe26c10fac65787229e88e2beb744927)

4. **Install the module.** Your developer installs the module. Select **Setup guide** and choose your Magento version and installation method: it walks your developer through installing the module and verifying the connection.

   ![The Magento setup guide panel, set to Magento 2.4, Composer and Technical: Download Word document, the Magento version tabs 2.4, 2.0 (legacy) and 1.9 / OpenMage, Installation method Composer or ZIP upload, Guide mode Technical or Descriptive, and the first two points of Before you begin.](/docs/_assets/ef4ff40c9aa03d31d381dbcc9154ee934cba71e3e3794de9f3bf58dbf194cf34)

**Google Ads:** connect it in onboarding (**Connect Google Ads and Merchant Center**) or on **Integrations**, pick the client account that runs your campaigns and grant Data Manager access. See [Google Ads](/docs/channels/google-ads).



1. **Connect Google.** On **Connect Google Ads and Merchant Center**, select **Continue as** your Google account and sign in with the account that can see your Google Ads. Tick **Google Ads** on Google's screen: Merchant Center connects with the same sign-in.

   ![The Connect step of onboarding, Connect Google Ads and Merchant Center: Google Ads and Merchant Center both Not connected, a Use our manager account link for when you can't sign in with that Google account, and the Continue as sam@northwind-outfitters.example button.](/docs/_assets/0d2be369dbe5104c735cd1c7373a8e7ff08264ebea02c129bd51097490f525e3)

   *Example data.*

2. **Pick the client account.** Choose the Google Ads **client account** that runs your campaigns, not a manager account. The workspace is named after the account you pick.

Already have a workspace? Open **Integrations** and select **Connect Google Ads** on the **Google Ads** row (**Add account** once one is connected). The same sign-in and account steps follow.

**Connect through our manager account instead**

Use this when you can't sign in with a Google account that can see your Google Ads. Product Metrics' manager account invites your Google Ads account, with access to that one account only.

1. **Choose the manager account.** On the **Connect** step, select **Use our manager account**.

   ![The Connect step of onboarding with the Use our manager account link, for when you can't sign in with the Google account that sees your Google Ads.](/docs/_assets/4795c769c1dc46b2348ec5796a84155e4bb0f4d0de7212fffd32ca30801c7727)

2. **Name the workspace.** Enter a name for the workspace the invite belongs to, then select **Continue**.

   ![The workspace name field of the manager account route, with the Continue button.](/docs/_assets/4fa654128e9a60d95e2ae0545925409921419a320e8b5f14f87d092342f2b85e)

3. **Enter your customer ID.** Enter your Google Ads customer ID and select **Send invite**.

   ![The Use our manager account form on the Connect step: enter the account's customer ID and send the invite, the account owner accepts it in Google Ads under Admin → Access and security → Managers, and Product Metrics checks access every 2 minutes. A Google Ads customer ID field, a Check access link, Connect with Google instead, and the Send invite button.](/docs/_assets/eaee093b9a33fc6b0e91382fb830909287363dcdfbdccd09a822b1be7a2fb4c1)

4. **Accept the invite in Google Ads.** In Google Ads, open **Admin → Access and security → Managers** and accept the invite. Product Metrics checks access every few minutes and starts the analysis once it has access.

**You should see:** under **Manage Magento**, the connection is **Active** and your property is linked; your Google Ads account shows on **Integrations**.

### 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](/docs/concepts/consent).



1. **Open Tracking.** Go to **Integrations → Tracking**. The checklist shows six steps: start by connecting your store, or use Cloudflare Tracking if you have no store platform.

   ![Tracking in Product Metrics with the Complete your tracking setup checklist of six steps, starting with Connect your store.](/docs/_assets/09a584afb1797a0439b68310c4d6085412eafebba1524c019f42a90f3ed4ea37)

2. **Follow the next step.** Once your store is connected and linked, the checklist opens the next open step. Each step says what it does.

   ![The Complete your tracking setup checklist in Tracking: 3 of 6 essential steps completed, with Connect your store, Link the store to this property and Install storefront tracking ticked, and Configure consent open as step 4 with the consent platform still Not configured.](/docs/_assets/b385237058280a34dca53f7f1e42704faa9a8aee59024bd5baafc2211e201e7e)

3. **Configure consent.** Under **Configure consent**, pick the cookie consent platform your storefront uses. The storefront script collects nothing until the visitor agrees.

   ![The Consent management panel in Tracking: the storefront script collects nothing until your cookie banner says the visitor agreed, a Not configured status, and the Consent platform dropdown.](/docs/_assets/f0a8d61eaa086657ce840c85899df48d5f3a7a52fb6c552710f93b1482b90e72)

**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](/docs/using/conversion-actions).



1. **Create Google Ads conversions.** Under **Create Google Ads conversions**, select **Create 8 conversion actions**. Product Metrics manages one Google Ads conversion action per purpose; they start as secondary goals, and you choose the primary goal in Google Ads.

   ![The Conversion actions page in Product Metrics, opened from Tracking: Not configured, 0 of 8 managed and the Create 8 conversion actions button. Below it, Customer types (New customer revenue and profit, Returning customer revenue and profit) and Order value (Order revenue, Order profit), each Missing with Google goal status Unknown, and the Lifetime value group heading.](/docs/_assets/816fdc81f1068f5d013a17d0d26166a0834cc61c69943d0c05d5171b557e0652)

Then [add your additional costs](/docs/using/costs), so the profit actions carry profit.



1. **Add your additional costs.** Product costs come from your store where it reports them. Under **Add your additional costs**, add shipping, handling, returns and payment fees, set **Product cost fallback (%)** and select **Activate additional costs**, so the profit conversions carry real 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](/docs/using/check-tracking).

## How it works on Magento

|                                    | On Magento                                                                                                                                                                                  |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Script and collector served by** | The Product Metrics module, on its own paths of your store domain, set for each store view by the module's configuration file. Nothing loads from another domain and there is no script tag |
| **Purchase confirmed from**        | Your Magento orders                                                                                                                                                                         |
| **Sent**                           | When the order is paid; the module sends changes every two minutes through cron                                                                                                             |
| **Delivered**                      | Server-side, through Google's Data Manager, to the eight **Product Metrics** conversion actions                                                                                             |
| **Refunds and cancellations**      | Refunds and cancellations come from the module; the Google Ads conversion is adjusted                                                                                                       |
| **Consent read from**              | OneTrust, Cookiebot, Usercentrics or Osano, or your own banner, passed on by your developer                                                                                                 |

## Troubleshooting

| Problem                              | Fix                                                                                                                                                                                             |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **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](/docs/concepts/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](/docs/platforms/magento): the full platform setup
* [Google Ads](/docs/channels/google-ads): what Product Metrics sends and how to troubleshoot it
* [Server-side tracking for Magento in Meta](/docs/tracking/server-side/magento-meta): the same store view, the other channel
* [Enhanced conversions for Magento in Google Ads](/docs/tracking/enhanced-conversions/magento-google-ads): add hashed customer data
* [Server-side conversion tracking](/docs/features/ad-blocker-proof-tracking): every platform and channel

On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [ad blocker conversion tracking check](https://www.productmetrics.io/ad-blocker-conversion-tracking), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie), [Product Metrics for Magento](https://www.productmetrics.io/platforms/magento)

Developers: do the same with the [CLI](/docs/cli/commands#google-ads) or the [API](/docs/api/google-ads/create-conversion-actions).
