> ## Documentation Index
> Fetch the complete documentation index at: https://996f455-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://996f455-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://996f455-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://996f455-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Rules of Product Metrics (/docs/concepts/rules)

<!-- agent-signals: reading_time_min: 4 · est_tokens: 1328 · updated: 2026-11-16 -->
Related: [How Product Metrics works](/docs/concepts/how-it-works.md), [Conversion values](/docs/concepts/conversion-values.md), [Profit](/docs/concepts/profit.md), [New and returning customers](/docs/concepts/new-and-returning-customers.md), [Conversion actions and events](/docs/concepts/conversion-actions-and-events.md), [Consent](/docs/concepts/consent.md)

> Best practices for setting up Product Metrics tracking and bidding, and the mistakes that cost conversions or count them twice.

These are rules of thumb from setting up Product Metrics on real stores. They aren't hard limits: they save you lost conversions, double counting and confusing bidding. The model behind them is [How it works](/docs/concepts/how-it-works).

## Setting up tracking

### Check before you remove anything

Don't remove your existing Google Ads conversion actions, Google tag or Meta pixel. Product Metrics creates its own actions next to them, as **secondary**, so nothing changes until you choose. On Home, Product Metrics compares its actions with your current ones 14 days after the first order.

**Ask your assistant:** "Compare my Product Metrics conversion actions with my current purchase action over the last 30 days."

If you keep the Meta Pixel, pass the same event ID to it so Meta counts each event once. See [Meta](/docs/channels/meta#running-the-meta-pixel-as-well).

### Set consent first

Choose your banner under **Tracking → Configure consent** before you send traffic.

With a wrong or missing banner, Product Metrics can't read the visitor's choice and treats it as not given. Orders then reach Google Ads without customer data or clicks, and nothing reaches Meta. See [Consent](/docs/concepts/consent).

| Store shows                                | Choose                                              |
| ------------------------------------------ | --------------------------------------------------- |
| Shopify's own banner                       | **Shopify Customer Privacy**                        |
| Shopware's own cookie manager              | Leave **Not configured**                            |
| OneTrust, Cookiebot, Usercentrics or Osano | That banner                                         |
| Anything else on Magento                   | Call `ProductMetrics.setConsent()` from your banner |

### One store per property

Assign each storefront to the property whose Google Ads account advertises it. Don't feed two stores into one property, and don't connect the same store twice: check **Ecommerce platforms** before you connect. See [Workspaces and properties](/docs/concepts/workspaces-and-properties).

### Check with a real order

A setup screen showing green isn't proof. Place and pay for a test order, then find it:

**Ask your assistant:** "Did Product Metrics receive my last order?"

A website on Cloudflare Tracking has its own checks: see [Check tracking](/docs/using/check-tracking).

## Profit and costs

### Set costs before you bid on POAS

Profit conversions are only sent once your additional costs are active and every cost of the order is known. Start on ROAS (revenue is sent from the first order), activate your costs, check that orders show a complete profit, then switch to POAS. See [Profit](/docs/concepts/profit).

### Fill product costs at the source

Put cost prices in your store platform or Merchant Center. The **Product cost fallback (%)** is a safety net for lines without a cost, not a substitute: it applies one percentage to every such line. On a website via Cloudflare, it is the only product cost, so set it carefully.

### Expect losses as 0

Google Ads and Meta accept no negative values. A loss-making order is sent as profit 0. Meta also gets the signed profit in `pm_contribution_profit`.

## Bidding

### Make one action primary, deliberately

Make **one** Product Metrics action primary for the campaign's goal. Don't make Revenue and Profit primary together: every order would count twice. Which action fits which goal, and the steps: [Make an action primary](/docs/using/conversion-actions#3-make-an-action-primary).

### Write targets as percentages

Google Ads, Meta and ChatGPT Ads steer on whatever value you send. A ROAS of 4.2 is a target ROAS of 420%. On profit, a target ROAS of 150% is a POAS of 1.5.

### Switch once the actions have history

The Product Metrics actions collect conversions as secondary from the first order. Product Metrics compares them with your current actions 14 days after that first order (**Home** shows **Collecting** until then), so you can make the switch on data.

## Meta

* **Send a test event first.** Meta lists an event in the custom conversion selector only after receiving it. Save a test event code, place a test order, then remove the code: events under **Test events** don't count in reporting.
* **One custom conversion per value**, with the rule `pm_purpose` equals the purpose. See [Conversion actions and events](/docs/concepts/conversion-actions-and-events).
* **Mark orders paid within 7 days.** Meta refuses events older than 7 days.

## Agents and the CLI

Rules for assistants and scripts (read before you write, browser steps stay with a person, dry runs) are on [CLI for agents](/docs/cli/for-agents).

## Where next

| If you need…          | Go to                                            |
| --------------------- | ------------------------------------------------ |
| The pipeline          | [How it works](/docs/concepts/how-it-works)           |
| What each value means | [Conversion values](/docs/concepts/conversion-values) |
| Bid on profit         | [POAS and ROAS bidding](/docs/features/poas-bidding)  |
| Connect an assistant  | [Connect Claude or ChatGPT](/docs/mcp/connect)        |
