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

# Conversion actions and events (/docs/concepts/conversion-actions-and-events)

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

> The eight Google Ads conversion actions and the Meta and ChatGPT Ads events Product Metrics sends, what each is for, and how to make one steer bidding.

**Each value gets its own action or event, so you pick exactly what bidding steers on.**

What each value is: [Conversion values](/docs/concepts/conversion-values). This page is where each value lands.



* [Google Ads](#google-ads-conversion-actions): Product Metrics creates eight purchase conversion actions for you, all secondary
* [Meta](#meta-events): custom events tagged with `pm_purpose`. You create the custom conversions
* [ChatGPT Ads](#chatgpt-ads-events): ChatGPT Ads custom events. You create a conversion for each one in Ads Manager

## Google Ads vs Meta vs ChatGPT Ads

|                         | **Google Ads**                    | **Meta**                                                                          | **ChatGPT Ads (OpenAI)**                                                              |
| ----------------------- | --------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **What**                | Eight purchase conversion actions | Standard events plus eight custom events                                          | Standard events plus four custom events                                               |
| **Created by**          | Product Metrics                   | Product Metrics sends the events; you create custom conversions in Events Manager | Product Metrics sends the events; you create conversions in Ads Manager → Conversions |
| **Sent through**        | Google's Data Manager             | The Meta Conversions API                                                          | The OpenAI Conversions API                                                            |
| **Steers bidding when** | You make the action primary       | You optimise a campaign on the custom conversion                                  | Your campaign optimises on the conversion, value-based                                |
| **Refunds**             | The conversion is adjusted        | Events aren't revised                                                             | Events aren't revised                                                                 |

## Try it

**Ask your assistant:** "Create the Product Metrics conversion actions in my Google Ads account and tell me which are primary."

You should see all eight actions created, each secondary until you change it. Creating them needs a workspace admin, a connected Google Ads account and an active store assigned to the property. It is safe to repeat: existing actions are relinked, never duplicated or edited.

## Rules

1. **Secondary by default.** All eight actions are created as secondary goals, so nothing changes in your campaigns until you choose.
2. **Primary is your decision.** Product Metrics never makes an action primary. You do it in Google Ads, for the one value you want to bid on ([how](/docs/using/conversion-actions#3-make-an-action-primary)).
3. **One primary purchase action.** When you make a Product Metrics action primary, set your old purchase action to secondary, so the same purchase isn't counted twice.
4. **Your existing actions stay.** Product Metrics never edits conversion actions it didn't create.
5. **One workspace per action name.** Names are unique per Google Ads account. If another workspace already manages them, the actions show as a conflict.
6. **Meta and ChatGPT Ads need a received event.** An event shows in Meta's custom conversion selector, or as a conversion in ChatGPT Ads Manager, only after it has been received once.

## Google Ads conversion actions

All are purchase actions, counted every conversion (many per click), created secondary.

| Conversion action                           | Value                      | Use it for                           |
| ------------------------------------------- | -------------------------- | ------------------------------------ |
| Product Metrics - Revenue                   | Order revenue              | ROAS bidding                         |
| Product Metrics - Profit                    | Order profit               | POAS bidding                         |
| Product Metrics - New Customer              | New customer revenue       | New customer bidding                 |
| Product Metrics - New Customer Profit       | New customer profit        | New customer bidding on profit       |
| Product Metrics - Returning Customer        | Returning customer revenue | Returning customer bidding           |
| Product Metrics - Returning Customer Profit | Returning customer profit  | Returning customer bidding on profit |
| Product Metrics - Revenue LTV               | Revenue lifetime value     | LTV bidding                          |
| Product Metrics - Profit LTV                | Profit lifetime value      | LTV bidding on profit                |

## Meta events

**Standard events:** `AddToCart`, `InitiateCheckout` and `Purchase`. The `Purchase` value is order revenue: products and shipping, minus refunds.

**Custom events**, one per value. Create a custom conversion on the event with the rule `pm_purpose` equals the purpose, category **Purchase**, using the event's value.

| Value                      | Event                       | `pm_purpose`                |
| -------------------------- | --------------------------- | --------------------------- |
| Order revenue              | `PMOrderRevenue`            | `ORDER_REVENUE`             |
| Order profit               | `PMOrderProfit`             | `ORDER_PROFIT`              |
| New customer revenue       | `PMNewCustomer`             | `CUSTOMER_NEW`              |
| New customer profit        | `PMNewCustomerProfit`       | `CUSTOMER_NEW_PROFIT`       |
| Returning customer revenue | `PMReturningCustomer`       | `CUSTOMER_RETURNING`        |
| Returning customer profit  | `PMReturningCustomerProfit` | `CUSTOMER_RETURNING_PROFIT` |
| Revenue LTV                | `PMRevenueLTV`              | `CUSTOMER_REVENUE_LTV`      |
| Profit LTV                 | `PMProfitLTV`               | `CUSTOMER_PROFIT_LTV`       |

```text
Custom conversion "PM profit"
  Event      PMOrderProfit
  Rule       pm_purpose equals ORDER_PROFIT
  Category   Purchase, value from the event
```

Extra parameters: `pm_contribution_profit` (signed profit when a loss is sent as 0) and `pm_cumulative_ltv` (the customer's running total on LTV events).

## ChatGPT Ads events

**Standard events:** `order_created`, `items_added` and `checkout_started`. The `order_created` value is order revenue: products and shipping, minus refunds known at the time.

**Custom events**, one per value. In ChatGPT **Ads Manager → Conversions**, create a conversion with the matching custom event name, then choose it as the conversion your campaign optimises for, value-based. OpenAI lowercases custom event names.

| Value         | Custom event       |
| ------------- | ------------------ |
| Order revenue | `pm_order_revenue` |
| Order profit  | `pm_order_profit`  |
| Revenue LTV   | `pm_revenue_ltv`   |
| Profit LTV    | `pm_profit_ltv`    |

ChatGPT Ads doesn't get new or returning customer conversions yet. Setup and consent: [ChatGPT Ads](/docs/channels/openai).

## Statuses

In the app, **Conversion actions** shows **Tracking ready** when all eight are live ([app badges](/docs/using/check-tracking#app-badges)). An action another workspace already manages shows as a conflict.



**For developers: action states**

| State          | Meaning                                                                     |
| -------------- | --------------------------------------------------------------------------- |
| `missing`      | Not created yet                                                             |
| `unlinked`     | Exists in Google Ads but isn't linked to this property; creating relinks it |
| `provisioning` | Being created                                                               |
| `uncertain`    | Not confirmed yet                                                           |
| `managed`      | Created and linked: conversions go here                                     |
| `conflict`     | Another workspace manages an action with this name                          |

`goal_status` is `primary`, `secondary` or `unknown`. Commands: [CLI](/docs/cli/commands#google-ads), [API](/docs/api/google-ads/get-conversion-actions).

## Where next



* [Google Ads](/docs/channels/google-ads): set up Google Ads
* [Meta](/docs/channels/meta): set up Meta
* [ChatGPT Ads](/docs/channels/openai): set up ChatGPT Ads
* [POAS and ROAS bidding](/docs/features/poas-bidding): bid on profit or revenue
* [Conversion actions](/docs/using/conversion-actions): make actions primary step by step
