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

# POAS bidding: bid on profit in Google Ads, Meta and ChatGPT Ads (/docs/features/poas-bidding)

<!-- agent-signals: reading_time_min: 7 · est_tokens: 2493 · updated: 2026-11-16 -->
Related: [Server-side conversion tracking that gets through ad blockers](/docs/features/ad-blocker-proof-tracking.md), [Customer Match lists in Google Ads, updated after every order](/docs/features/customer-list.md), [Enhanced Conversions, Meta Advanced Matching and OpenAI Conversions API](/docs/features/enhanced-conversions.md), [LTV bidding: bid on customer lifetime value in Google Ads, Meta and ChatGPT Ads](/docs/features/ltv-bidding.md), [New customer bidding in Google Ads and Meta](/docs/features/new-customer-bidding.md), [Returning customer bidding in Google Ads and Meta](/docs/features/returning-customer-bidding.md)

> Send each paid order's revenue and profit to Google Ads, Meta and ChatGPT Ads, then bid on profit (POAS) or revenue (ROAS) with a target ROAS.

Product Metrics sends every paid order to Google Ads, Meta and ChatGPT Ads twice: once with its **revenue**, once with its **profit**. In each channel you bid on the value you choose; in Google Ads and Meta with a **target ROAS**, as a percentage.

The conversions are sent server-side, from your store's own order data.

## Pick your platform

One guide per platform and channel: connect, set up the conversions and costs, bid, check.



| Store                    | Google Ads                                                       | Meta                                                 | ChatGPT Ads                                                   |
| ------------------------ | ---------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------- |
| Shopify                  | [Shopify + Google Ads](/docs/bidding/poas/shopify-google-ads)         | [Shopify + Meta](/docs/bidding/poas/shopify-meta)         | [Shopify + ChatGPT Ads](/docs/bidding/poas/shopify-openai)         |
| WooCommerce              | [WooCommerce + Google Ads](/docs/bidding/poas/woocommerce-google-ads) | [WooCommerce + Meta](/docs/bidding/poas/woocommerce-meta) | [WooCommerce + ChatGPT Ads](/docs/bidding/poas/woocommerce-openai) |
| Magento                  | [Magento + Google Ads](/docs/bidding/poas/magento-google-ads)         | [Magento + Meta](/docs/bidding/poas/magento-meta)         | [Magento + ChatGPT Ads](/docs/bidding/poas/magento-openai)         |
| Lightspeed               | [Lightspeed + Google Ads](/docs/bidding/poas/lightspeed-google-ads)   | [Lightspeed + Meta](/docs/bidding/poas/lightspeed-meta)   | [Lightspeed + ChatGPT Ads](/docs/bidding/poas/lightspeed-openai)   |
| Shopware                 | [Shopware + Google Ads](/docs/bidding/poas/shopware-google-ads)       | [Shopware + Meta](/docs/bidding/poas/shopware-meta)       | [Shopware + ChatGPT Ads](/docs/bidding/poas/shopware-openai)       |
| Any website (Cloudflare) | [Website + Google Ads](/docs/bidding/poas/cloudflare-google-ads)      | [Website + Meta](/docs/bidding/poas/cloudflare-meta)      | [Website + ChatGPT Ads](/docs/bidding/poas/cloudflare-openai)      |

Developers: do the same with the [CLI](/docs/cli/commands#google-ads) or the [API](/docs/api/google-ads/create-conversion-actions).

## Set it up with AI



Paste the prompt into your assistant.



First connect the Product Metrics MCP server ([https://www.productmetrics.io/mcp](https://www.productmetrics.io/mcp); see [Connect your assistant](/docs/mcp/connect)).

**Claude or ChatGPT:** "Set up POAS bidding in Google Ads with Product Metrics, so my campaigns bid on profit. Check my setup status first, walk me through each open step, and give me the link when I need to click something."

**Claude Code or Codex:** "Set up POAS bidding in Google Ads with Product Metrics: check my costs are active and the conversion actions exist, then tell me which action to make primary. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first)."

## In the app

### 1. Activate your additional costs

In **Tracking → Complete your tracking setup → Add your additional costs**, check the defaults and select **Activate additional costs**. Details: [Costs](/docs/using/costs).

You should see the **Profit tracking** section say your additional costs are active.

### 2. Create the conversion actions

In **Tracking → Create Google Ads conversions**, select **Create 8 conversion actions**. They start as secondary. Details: [Conversion actions](/docs/using/conversion-actions).

You should see **Conversion actions** read **Tracking ready**.

### 3. Make Product Metrics - Profit primary

In Google Ads, make **Product Metrics - Profit** primary and your old purchase action secondary, then set a profit target ROAS: [Make an action primary](/docs/using/conversion-actions#3-make-an-action-primary).

You should see **Product Metrics - Profit** as a primary action under **Goals → Conversions**. Once it runs, ask your assistant: *"What is my POAS per campaign over the last 30 days? Which campaigns are below break-even?"*

On Meta and ChatGPT Ads, you create the profit conversion yourself: see [By channel](#by-channel).

## ROAS vs POAS

The same order, sent both ways. Order #1042 from [Profit](/docs/concepts/profit), bought after €36.00 of ad spend:

* **ROAS bids on revenue.** The order sends €108.00 to **Product Metrics - Revenue**: €108.00 ÷ €36.00 = ROAS 3.0, which is a target ROAS of 300%. Every order counts by its revenue.
* **POAS bids on profit.** The same order sends €48.46 to **Product Metrics - Profit**: €48.46 ÷ €36.00 = POAS 1.35. Orders with a higher margin get more priority.

€108.00 is what the customer paid for products and shipping; profit starts from revenue **excluding tax**, €89.26. On Meta, profit is the `PMOrderProfit` event; on ChatGPT Ads, `pm_order_profit`. See [Conversion actions and events](/docs/concepts/conversion-actions-and-events).

New customers ([New customer bidding](/docs/features/new-customer-bidding)), returning customers ([Returning customer bidding](/docs/features/returning-customer-bidding)) and lifetime value ([LTV bidding](/docs/features/ltv-bidding)) each come as a revenue and a profit version too.

## How profit is built

**Profit = revenue excluding tax − product costs − additional costs**, before advertising. Only complete profit is sent, and a loss is sent as 0.



![Revenue excluding tax of 89.26 minus product costs 32.00, outbound shipping 5.50, payment fee 1.80, pick and pack 1.50 and returns 0.00 leaves a profit of 48.46. Product cost comes from your store first, then Google Merchant Center, then your fallback percentage.](/docs/_assets/330def2f4635e18a6c19bbebbefa1386d51bc7f1888d8d6144da0bb9849a0e54)

*Figure: Profit for order #1042: revenue ex tax minus every cost.*

Where each cost comes from, per platform, and the edge cases are on [Profit](/docs/concepts/profit). The **Profit + clear stock** strategy is on [Conversion values](/docs/concepts/conversion-values#released-capital).

## When to switch to POAS

* **Start with ROAS** when your costs aren't in Product Metrics yet. Revenue is sent from the first paid order.
* **Switch to POAS** once your additional costs are active, especially when margins differ between products.
* **Both are always sent.** Only the one you make primary in Google Ads, or optimise on in Meta or ChatGPT Ads, steers bidding.

Moving a campaign from revenue to profit, lower the target: profit is a fraction of revenue. On profit, a target ROAS of **100% is break-even**, and 150% is a POAS target of 1.5. Read [how to set a target ROAS from your margin](https://www.productmetrics.io/blog/target-roas-from-margin), or work it out with the [POAS calculator](https://www.productmetrics.io/poas-calculator). The terms: [POAS](https://www.productmetrics.io/glossary/poas), [target ROAS](https://www.productmetrics.io/glossary/target-roas) and [break-even ROAS](https://www.productmetrics.io/glossary/break-even-roas).

## By channel

* **[Google Ads](/docs/channels/google-ads):** Product Metrics creates the conversion actions as secondary; you make one primary. Follows your consent platform. Sent from the moment tracking is live.
* **[Meta](/docs/channels/meta):** you connect your pixel and create the custom conversion in Events Manager. Needs marketing consent; profit and revenue events also analytics consent. Past orders aren't imported; Meta rejects events older than 7 days.
* **[ChatGPT Ads](/docs/channels/openai):** you connect your pixel and create a conversion on `pm_order_profit` in Ads Manager → **Conversions**. Needs marketing consent (ad user data). Past orders aren't imported.

Events and consent per channel: [Conversion actions and events](/docs/concepts/conversion-actions-and-events), [Consent](/docs/concepts/consent).

## Troubleshooting

### Profit action empty

**Product Metrics - Profit** has no conversions while **Revenue** does: your additional costs aren't active. In **Tracking**, the **Profit tracking** section should say they are; if not, select **Add costs**.

### Revenue but no profit

One cost is unknown, for example a line with no cost price while **Product cost fallback (%)** isn't set. Add cost prices in your store, or set the fallback.

### Spend dropped after switching

The target ROAS is still set for revenue. Lower it to a profit target, for example 150%, or 100% to break even.

### PMOrderProfit missing in Meta

Meta only lists an event after receiving one. It needs complete costs and a visitor who accepted marketing and analytics cookies. Place a test order with a test event code.

### Purchases counted twice

Only one purchase action should be primary. Set your old purchase action to secondary: [Make an action primary](/docs/using/conversion-actions#3-make-an-action-primary).

## FAQ

### Is POAS bidding set up the same way in every channel?

The profit is the same; the setup differs per channel. In Google Ads you make **Product Metrics - Profit** primary, in Meta you create a custom conversion on `PMOrderProfit`, and in ChatGPT Ads you add a conversion on `pm_order_profit` in Ads Manager → **Conversions**.

### Which store platforms support POAS bidding?

Shopify, WooCommerce, Magento, Lightspeed, Shopware and any website through Cloudflare Tracking. A website sends no product costs, so its profit uses your **Product cost fallback (%)**.

### Can I bid on profit from new customers or LTV too?

Yes. New customers, returning customers and lifetime value each come as a revenue and a profit version. ChatGPT Ads has no new or returning customer conversions yet; LTV works there.

### What is sent when an order makes a loss?

A profit of 0, because Google Ads and Meta accept no negative value. Meta also gets the signed profit in `pm_contribution_profit`.
