> ## 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

# How Product Metrics works (/docs/concepts/how-it-works)

<!-- agent-signals: reading_time_min: 3 · est_tokens: 1189 · updated: 2026-11-16 -->
Related: [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), [Server-side tracking](/docs/concepts/server-side-tracking.md)

> How a purchase on your store becomes a conversion in Google Ads, Meta and ChatGPT Ads, with its revenue, profit, new or returning customer and lifetime value.

This is the tracking pipeline: the part of Product Metrics that bidding, the profitability dashboard and Product Segmentation build on.

A visit is seen in the browser by **Full Signal Tracking**, the order is confirmed from your **shop's own order data**, and only then does Product Metrics work out its values and send them from its server. You don't place a Google tag or write code.



![Full Signal Tracking on your own domain sees the visit, your shop confirms the paid order, consent decides what may be sent, the customer is classified as new or returning, values are worked out, and Product Metrics sends the conversion to Google Ads, Meta and ChatGPT Ads.](/docs/_assets/6cbd27de73fec1fb966cf74f6adfa1e71bfdbc1538cbf233ad969cd223ad8fa6)

*Figure: How a paid order becomes a conversion.*

## The stages

Every order passes the five stages in the diagram, in this order:

1. **Observe.** Full Signal Tracking, on your own domain, records which ad the visitor clicked (Google, Meta or ChatGPT Ads), together with the visitor's cookie choice. Stage 3 applies that choice.
2. **Confirm.** Your shop confirms the order from its own data, and a pending order waits until your platform marks it paid. A purchase reported only by the browser is never trusted.
3. **Consent.** The visitor's choice decides what may go to each channel. See [Consent](/docs/concepts/consent).
4. **Classify.** The customer is new or returning, matched against earlier paid orders in the same store. See [New and returning customers](/docs/concepts/new-and-returning-customers).
5. **Value.** Revenue, profit and lifetime value are worked out. Profit waits until every cost is known. See [Conversion values](/docs/concepts/conversion-values) and [Profit](/docs/concepts/profit).

After the fifth stage, the order leaves Product Metrics in two steps:

* **Delivery.** Product Metrics sends the conversion from its server: to eight conversion actions in Google Ads (through Google's Data Manager), and as events to Meta and ChatGPT Ads. See [Conversion actions and events](/docs/concepts/conversion-actions-and-events).
* **Adjustment.** A refund or cancellation adjusts the Google Ads conversion. Meta and ChatGPT Ads events are not revised.

*Click IDs recorded: Google's `gclid`, `gbraid` and `wbraid`, Meta's `fbp` and `fbc`, and ChatGPT Ads' `oppref`.*

## Where the order comes from

| Platform                                          | How your shop confirms the order                                |
| ------------------------------------------------- | --------------------------------------------------------------- |
| [Shopify](/docs/platforms/shopify)                     | The Product Metrics Shopify app reads it from Shopify           |
| [WooCommerce](/docs/platforms/woocommerce)             | The plugin sends orders with a status you marked as paid        |
| [Magento](/docs/platforms/magento)                     | The module sends order changes every two minutes (Magento cron) |
| [Lightspeed](/docs/platforms/lightspeed)               | Order webhooks Product Metrics registers for you                |
| [Shopware](/docs/platforms/shopware)                   | The Product Metrics plugin                                      |
| [Any website (Cloudflare)](/docs/platforms/cloudflare) | The purchase your page reports; refunds are tracked too         |

## Workspaces and properties

Your **workspace** is your company. A **property** is one Google Ads account in your workspace, with the store assigned to it. A property's conversions go to its Google Ads account, its Meta pixel and its ChatGPT Ads pixel. See [Workspaces and properties](/docs/concepts/workspaces-and-properties).

## Try it

Place a test order, then open **Tracking**: the badge reads **Tracking active**, and **Conversion actions** reads **Tracking ready**.

**Ask your assistant:** "Show me the last order Product Metrics received from my store, and whether it counted as a new customer."

You should see order #1042 as paid, with revenue €108.00, its profit and a new or returning customer. What each status means, and the checks for a website on Cloudflare, are on [Check tracking](/docs/using/check-tracking#statuses).

## Where next



* [Conversion values](/docs/concepts/conversion-values): what is sent per order, and which action or event carries it.
* [Server-side tracking](/docs/concepts/server-side-tracking): your own domain, ad blockers and Safari ITP.
* [Check that tracking works](/docs/using/check-tracking): the checks to run after your first order.
* [Connect your store](/docs/platforms/overview): choose your platform: Shopify, WooCommerce, Magento, Lightspeed, Shopware or Cloudflare.
