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

# Conversion values (/docs/concepts/conversion-values)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1744 · updated: 2026-11-16 -->
Related: [How Product Metrics works](/docs/concepts/how-it-works.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)

> What Product Metrics sends with each order, where each value comes from, and which Google Ads action, Meta event or ChatGPT Ads event carries it.

Every paid order is sent as several conversions, one per value. Google Ads, Meta and ChatGPT Ads (OpenAI) only know "conversion value". Product Metrics gives each value its own conversion action or event, so you choose which one bidding steers on. The pipeline that produces them is [How it works](/docs/concepts/how-it-works). This page is the model.

## Revenue vs profit

|                       | **Revenue**                                      | **Profit**                                                          |
| --------------------- | ------------------------------------------------ | ------------------------------------------------------------------- |
| **What**              | What the customer paid for products and shipping | Revenue excluding tax minus product costs and your additional costs |
| **Example**           | €108.00                                          | €48.46                                                              |
| **Needs**             | Nothing: sent from the first paid order          | Your additional costs active, and every cost of the order known     |
| **Bid on it as**      | ROAS                                             | POAS                                                                |
| **Loss-making order** | Not possible                                     | Sent as 0                                                           |

Both are sent for every paid order. Only the one you make primary in Google Ads, or optimise on in Meta or ChatGPT Ads, steers bidding.

## Rules

1. **Only paid orders.** A pending order isn't sent. It goes once your platform marks it paid.
2. **One conversion per value.** Each value has its own Google Ads action, Meta event and ChatGPT Ads custom event, so values never mix.
3. **Profit only when complete.** If one cost of the order is unknown, the profit conversions aren't sent. Revenue still is.
4. **New customer once.** A customer's new customer conversion is sent for their first paid order only.
5. **Observed, not predicted.** Lifetime value is what the customer has paid you so far.
6. **Fixed per order.** A later change to a product's cost price doesn't rewrite the profit of orders already sent.

## The values

### Revenue

The order's products and shipping. Google Ads gets it as **Product Metrics - Revenue**; Meta as `Purchase` and `PMOrderRevenue`; ChatGPT Ads as `order_created` and `pm_order_revenue`.

```text
Order #1042   products €98.00, shipping €10.00
  → Revenue 108.00
```

The Meta `Purchase` and ChatGPT Ads `order_created` values subtract refunds already made on the order.

### Profit

Revenue excluding tax, minus product costs and the additional costs you set. Order #1042's costs line by line, and how each is found: [Profit](/docs/concepts/profit).

```text
Order #1042   revenue ex tax 89.26 − costs 40.80
  → Profit 48.46
```

### New and returning customer

The same order, sent again under the customer's type, as revenue and as profit. How customers are matched is on [New and returning customers](/docs/concepts/new-and-returning-customers).

```text
Order #1042   no earlier paid order from this customer
  → New Customer 108.00, New Customer Profit 48.46
Order #1077   same customer, second order
  → Returning Customer 64.00, Returning Customer Profit 22.40
```

An order Product Metrics can't match to a customer is sent as revenue and profit only. ChatGPT Ads doesn't get new and returning customer conversions yet.

### Lifetime value

What the customer has paid you over their paid orders in this store, as revenue and as profit. It needs a recognised customer: customer ID, email or phone number.

```text
Order #1042   first order   revenue 108.00
Order #1077   second order  revenue  64.00
  → Meta PMRevenueLTV value 64.00, pm_cumulative_ltv 172.00
```

Meta gets each order's addition as the value, and the running total in `pm_cumulative_ltv` (when all the customer's orders share one currency).

ChatGPT Ads gets each order's addition as `pm_revenue_ltv` and `pm_profit_ltv`, so its sum over a customer's orders is their lifetime value.

### Released capital

With the **Profit + clear stock** strategy, the purchase cost of slow stock sold above its normal stock level is added to every value of that order, revenue and profit alike. With any other strategy nothing is added.

## Types

| Value                      | Sent when                               |
| -------------------------- | --------------------------------------- |
| Order revenue              | Every paid order                        |
| Order profit               | Every cost known                        |
| New customer revenue       | The customer's first paid order         |
| New customer profit        | First paid order, every cost known      |
| Returning customer revenue | A later paid order                      |
| Returning customer profit  | A later paid order, every cost known    |
| Revenue LTV                | A recognised customer                   |
| Profit LTV                 | A recognised customer, every cost known |

The Google Ads action, Meta event and ChatGPT Ads event that carries each value: [Conversion actions and events](/docs/concepts/conversion-actions-and-events). ChatGPT Ads gets revenue, profit and the two LTV values, not new or returning customers.

Meta also gets the standard `Purchase`, `AddToCart` and `InitiateCheckout` events; ChatGPT Ads gets `order_created`, `items_added` and `checkout_started`.

## Try it

**Ask your assistant:** "For my last order, what revenue and profit did Product Metrics work out, and was it a new customer?"

You should see order #1042 as paid, with revenue €108.00, profit €48.46 and a new customer.

## What you don't do

You don't calculate or upload values. You:

1. Connect your store ([choose your platform](/docs/platforms/overview))
2. Add your additional costs, for profit ([Profit](/docs/concepts/profit))
3. Choose which value bidding steers on ([Conversion actions and events](/docs/concepts/conversion-actions-and-events))

## Where next

| If you need…                      | Go to                                                                    |
| --------------------------------- | ------------------------------------------------------------------------ |
| How profit is worked out          | [Profit](/docs/concepts/profit)                                               |
| How new and returning are decided | [New and returning customers](/docs/concepts/new-and-returning-customers)     |
| Which action or event to bid on   | [Conversion actions and events](/docs/concepts/conversion-actions-and-events) |
| Bidding on profit                 | [POAS and ROAS bidding](/docs/features/poas-bidding)                          |
| Bidding on lifetime value         | [LTV bidding](/docs/features/ltv-bidding)                                     |
