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

# What is Product Metrics? (/docs/overview/what-is-product-metrics)

<!-- agent-signals: reading_time_min: 4 · est_tokens: 1379 · updated: 2026-11-16 -->
Related: [Agents, skills and MCP](/docs/overview/agents-skills-and-mcp.md), [Should I use Product Metrics?](/docs/overview/comparison.md), [Customer Match lists in Google Ads on any website with Cloudflare](/docs/tracking/customer-lists/cloudflare-google-ads.md)

> The operating system of ecommerce. Server-side tracking, bidding on profit and customer value, a profitability dashboard and Product Segmentation in one product.

Product Metrics is **the operating system of ecommerce**: it maximises product performance and grows your profit. It combines four parts:

* **Server-side conversion tracking**: every paid order, confirmed from your shop and sent from the server, through ad blockers.
* **Bidding on POAS, new customers, returning customers and LTV** in Google Ads and Meta (POAS and LTV in ChatGPT Ads too).
* **A profitability dashboard**: profit, POAS and ROAS per product and campaign.
* **Product Segmentation**: machine learning puts every product in one of six segments, from Stars to Ghosts, based on profitability, inventory, product returns, potential and competitor price.

These are the building blocks:



* [Server-side tracking](/docs/features/ad-blocker-proof-tracking): Full Signal Tracking: every paid order, sent from your own domain.
* [Enhanced Conversions](/docs/features/enhanced-conversions): hashed customer data with each order, when the visitor consented.
* [Customer lists](/docs/features/customer-list): Six Customer Match lists in Google Ads, kept up to date.
* [POAS and ROAS bidding](/docs/features/poas-bidding): revenue and profit on every order.
* [New and returning customers](/docs/features/new-customer-bidding): each order marked as a first or a repeat purchase.
* [LTV bidding](/docs/features/ltv-bidding): each customer's lifetime revenue and profit.
* Profitability dashboard: profit, POAS and ROAS per product and campaign.
* [Product Segmentation](https://www.productmetrics.io/product-segmentation): Stars, Question Marks, Cash Cows, Dogs, Drainers and Ghosts.
* [MCP server](/docs/mcp/overview): ask Claude or ChatGPT about your store and your Google Ads account.
* [CLI and API](/docs/cli/overview): set up and check everything from the terminal or your own code.

With Product Metrics, Google Ads and Meta see every sale, including the ones behind ad blockers, and know what each sale was worth to you. You see which products make money and which drain it.

## How does tracking work? (at a glance)



![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.*

* You connect your **store** (Shopify, WooCommerce, Magento, Lightspeed, Shopware, or any website through Cloudflare) and your **channels** (Google Ads with its Merchant Center, Meta, ChatGPT Ads (OpenAI)).
* When an order is paid, Product Metrics reads it from the store, works out its **profit** from product costs and your additional costs, and checks whether the customer is **new or returning**.
* It sends the order server-side: to Google Ads as **eight conversion actions** (revenue and profit for every order, new customers, returning customers and lifetime value), and to Meta through the **Conversions API**.
* Your campaigns bid on the action you choose. The actions start as secondary, so nothing changes until you make one primary.

The full pipeline is in [How it works](/docs/concepts/how-it-works).

## Why send profit and customer data to your ad platforms?

Without it, Google Ads and Meta only see the conversions their browser tag catches, valued at revenue. They cannot see the orders an ad blocker hid, which products barely make money, or whether a buyer was new.

With it, your campaigns can:

* **Bid on profit (POAS)** instead of revenue, so a €100 order with €8 margin is not valued like one with €40.
* **Give new customers higher priority**, or steer on returning customers' revenue or profit.
* **Value customers who come back** with lifetime value.
* **Learn from every sale**, including the ones a standard tag misses.

ROAS bidding works as soon as your store is connected. Add your costs and you can switch to POAS.

## Why Product Metrics?

* **Server-side, adblocker-proof** — gets through every adblocker, and auto-rotates its endpoint if it is ever blocked: see [Server-side tracking](/docs/features/ad-blocker-proof-tracking).
* **Orders confirmed from the shop** — every conversion is a paid order your store reports, not only what a browser tag saw.
* **Profit on every order** — product costs come from your store; shipping, handling, returns and payment fees from your [cost settings](/docs/using/costs).
* **Google Ads and Meta from one setup** — the same revenue, profit, new and returning customer and LTV values go to both.
* **Consent respected** — customer data goes only with the visitor's consent. See [consent](/docs/concepts/consent).
* **Every door, one account** — the app, the [MCP server](/docs/mcp/overview), the [CLI](/docs/cli/overview) and the [API](/docs/api/overview) work on the same workspace.



> **Note:** Server-side tracking is included in the Product Metrics Pro subscription. It is not billed separately.

## Next steps



* [Quickstart](/docs/quickstart): from sign-in to tracked orders and a POAS report.
* [How it works](/docs/concepts/how-it-works): from paid order to conversion action.
* [Conversion values](/docs/concepts/conversion-values): what each order carries, and where each value comes from.
* [Agents, skills and MCP](/docs/overview/agents-skills-and-mcp): set Product Metrics up with Claude, ChatGPT or a coding agent.
