Skip to content
Connect your store

Magento server-side tracking and profit bidding (POAS)

Have your developer install the Product Metrics Magento module, get server-side conversion tracking live in Google Ads, Meta and ChatGPT Ads, and bid on profit, new customers or lifetime value.

The Product Metrics module reads every paid order from Magento, with its product costs and customer, and serves tracking from your own domain. Product Metrics adds profit, new or returning customer and lifetime value, and sends it server-side to each ad channel. Works with Magento 2.4, Magento 2.0 and Magento 1.9 / OpenMage.

Magento needs a developer: the module is installed on your server with Composer or as a ZIP, which Magento Admin can’t do. Everything else you do yourself, in Product Metrics and Magento Admin.

Prerequisites

  • Magento administrator access, editor or admin access to your workspace, and Magento cron running: the module sends order changes every two minutes through cron.
  • A developer with terminal access and Composer (recommended for Magento 2.4), or private file access for the ZIP. They need your exact Magento and PHP release, the installation directory and the account PHP and cron run as. On Magento 2, they check PHP has enough memory first: Adobe recommends 1G for compilation.
  • For a live store, a backup and a maintenance window. For the test order: a linked property, consent set up, cron running and your payment provider’s test mode.
  • Your public HTTPS shop address and the store-view ID to track. Each store view connects on its own.

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/mcp

Claude Code: run this in your terminal.

claude mcp add --transport http product-metrics https://www.productmetrics.io/mcp

CodexAll clients and details →

Paste the prompt into your assistant.

Help me connect my Magento store to Product Metrics. Check my setup status first, walk me through each open step, and tell me exactly what my developer needs to do.
Help me connect my Magento store to Product Metrics. Check my setup status first, walk me through each open step, and tell me exactly what my developer needs to do.
Help me connect my Magento store to Product Metrics: walk me through each open setup step and tell me exactly what my developer needs to do, and never ask for the configuration file's contents. 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).
Help me connect my Magento store to Product Metrics: walk me through each open setup step and tell me exactly what my developer needs to do, and never ask for the configuration file's contents. 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).

In the app

1. Create the module configuration

  1. Find the store-view ID. In Magento Admin, open Stores → All Stores (Magento 1.9 / OpenMage: System → Manage Stores) and select your store view in the Store View column (for example Default Store View), not the website or store. The number after /store_id/ in the address is the ID. On Magento 2.4, once the module is installed, Magento Admin → Product Metrics also shows each store view’s ID and public address. Note the public HTTPS shop address too, not the Admin address.
  2. Create the configuration. In Product Metrics, open Ecommerce platforms → Connect Magento and fill in Magento version (Magento 1.9 / OpenMage or Magento 2), Store URL and Store view ID. Leave Advanced custom checkout mapping closed unless your shop has a custom checkout. Select Create module configuration.
  3. Download the file. Select Download 1.json (the number is your store-view ID). It holds a private key: share it with your developer privately, never in a screenshot or shared chat.

You should see the configuration file downloaded.

2. Your developer installs the module

Your developer installs the module on your server with Composer or as a ZIP, adds the configuration file and makes sure Magento cron runs. Product Metrics shows the exact commands, filled in for your release, in its Magento setup guide.

On Magento 2.4 you can import the file yourself once the module is installed: Magento Admin → Product Metrics, choose the Store view, choose the file under Private JSON configuration, select Import configuration. You should see Configuration saved privately.

3. Verify the module

Once the module, configuration file and cron are in place, select Verify installed module in Product Metrics. If it says Module verified. Tracking configuration is still publishing., wait and select Check publication, then Finish Magento setup if it appears.

You should see the connection Active under Manage Magento → Connection details and removal, with the same desired and active revision numbers.

4. Send the orders to a property

Under Manage Magento, choose the property that should receive the store view’s orders.

5. Finish tracking setup

The setup checklist in Tracking opens each of these in turn:

You should see the badge next to Tracking read Tracking active.

6. Check it works

Place a paid test order in the connected store view and allow a few minutes for cron. Then follow Check tracking, or ask your assistant whether the order arrived.

You should see your test order arrive. If it doesn’t, send the order number and store-view ID to support.

How it works on Magento

On Magento
InstallA developer: Composer or ZIP, Magento cron, one configuration file per store view
Product costThe cost on each order item (order currency = base currency); you add the rest
ConsentOneTrust, Cookiebot, Usercentrics or Osano, or your own banner (your developer connects it)
Customer identityPer store view: customer account or guest email
RefundsRefunded orders are sent without a profit figure
Several store viewsOne module installation; one configuration and file per store view
RemoveManage Magento → Remove connection; the developer disables and removes the module and moves the old file out. Reinstall with a new file, never the old one

What you get on Magento

FeatureChannelsOn this platform
Server-side conversion trackingGoogle Ads · Meta · ChatGPT AdsThe module serves the script and collector on random paths of your domain.
Enhanced ConversionsGoogle Ads · Meta · ChatGPT AdsLogged-in customer details and guest email, only with ad user data consent.
Customer listsGoogle AdsSix Customer Match lists, filled from your Magento orders.
POAS and ROAS biddingGoogle Ads · Meta · ChatGPT AdsCost per order item when order and base currency match; refunds go without profit.
New customer biddingGoogle Ads · MetaPer store view, by customer account or guest email; cancelled orders don’t count.
Returning customer biddingGoogle Ads · MetaSame matching as new customers: per store view.
LTV biddingGoogle Ads · Meta · ChatGPT AdsObserved value from paid orders, not a prediction.

Troubleshooting

Verify installed module fails

Check HTTPS reachability, the store-view ID, and that the package matches your Magento release. Your developer checks that the configuration file belongs to the PHP and cron account and only that account can read it. Then verify again.

“Allowed memory size exhausted”

Your developer reruns that one command with a higher memory limit (for example 1G), once the server has the memory.

“crontab: not found”

The server has no cron scheduler. Your developer or host has to enable one; without cron, order changes don’t reach Product Metrics.

The Product Metrics menu is missing in Magento Admin

The module isn’t enabled yet, or your admin role can’t see it. Ask your developer to check the install steps, and check your admin permissions.

Import configuration reports folder permissions or an existing configuration

Your developer resolves it on the server first; then import again.

FAQ

Do I need a developer for Magento?

Yes, once. The module is installed on your server with Composer or as a ZIP, which Magento Admin can’t do. Everything after that you do yourself, in Product Metrics and Magento Admin.

Which Magento versions does Product Metrics support?

Magento 2.4, Magento 2.0 and Magento 1.9 / OpenMage. If your release isn’t one of these, contact Product Metrics support before installing.

OneTrust, Cookiebot, Usercentrics and Osano work without extra work. Any other banner needs your developer to connect it with ProductMetrics.setConsent(); Magento’s cookie restriction notice does not grant consent.

Where do product costs come from on Magento?

From the cost on each Magento order item, when the order currency matches the base currency. You add shipping, handling, returns and payment fees as additional costs.

Where next

Developers: do the same with the CLI or the API.