POAS vs ROAS: Profit or Revenue Per Ad Dollar
In short: Both divide something by ad spend, and only the numerator differs - revenue for ROAS, gross profit for POAS. POAS requires an accurate margin or cost-of-goods feed flowing into the calculation, or the bid strategy, or it collapses into a relabeled ROAS. ROAS just needs a purchase value and works natively in every platform without extra setup. Use ROAS when margin is roughly flat across your catalog, use POAS when it varies a lot by product.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
POAS
Gross profit attributed to advertising divided by ad spend, replacing the revenue numerator in ROAS with revenue minus cost of goods.
It exposes what revenue reporting hides: a catalog where cheap high-margin items and expensive low-margin ones look identical on ROAS but differ completely in contribution. Feeding margin into bidding usually shifts delivery toward better products. The main pitfall is a stale or incomplete margin feed, which produces confident optimization toward numbers that no longer reflect actual product costs.
Full definitionROAS
Revenue attributed to advertising divided by the ad spend that produced it, expressed as a ratio or multiple of spend.
It compares topline revenue against media cost and ignores everything else: margin, shipping, returns, fulfillment, and the fixed cost of operating. It also inherits every weakness of the attribution feeding its numerator. The most common misreading is taking a strong platform figure as proof of profit, when the same customers may well have purchased without ever seeing the ad.
Full definitionSide by side.
The differences that actually change what happens in your account.
| POAS | ROAS | |
|---|---|---|
| Numerator | Gross profit - revenue minus cost of goods sold. | Gross revenue from the attributed purchase. |
| Extra data required | A margin or cost-of-goods feed per SKU, kept current. | None beyond the purchase value itself. |
| Two products, same price, different margin | Clearly different - the higher-margin item shows a higher POAS. | Identical - ROAS can't tell them apart. |
| Effect on bidding when fed as conversion value | Shifts delivery toward higher-margin products and away from low-margin ones, even at equal conversion rates. | Treats every dollar of revenue the same, so a bidder chases the highest-converting or highest-priced item regardless of margin. |
| Native platform support | Not a built-in metric - requires custom conversion value uploads or a margin-aware feed. | Native column in every major ad platform's reporting. |
| Failure mode | A stale or wrong margin feed produces a confidently wrong number the bidder trusts completely. | A catalog-wide average return that hides which specific products are actually profitable to advertise. |
| Where it's most useful | Multi-SKU ecommerce with real margin variation across the catalog. | Single-product or service businesses, or lead gen, where margin doesn't vary meaningfully by conversion. |
What actually separates them.
POAS only functions correctly when a margin or cost-of-goods feed is wired into the conversion value; without it, POAS collapses into a relabeled ROAS.
Feeding POAS-style values into a bidder changes what it buys - it shifts delivery toward higher-margin SKUs - while ROAS-based bidding treats a dollar of revenue from any product as equally desirable.
A catalog can show a flat, healthy ROAS across products while POAS reveals wide swings, because ROAS cannot distinguish a low-margin item from a high-margin one at the same price.
ROAS is a native reporting column everywhere; POAS has to be built, either through a margin-adjusted conversion value upload or a spreadsheet blending ad data with cost data.
A margin feed going stale - a cost increase, a supplier change, a sale price not reflected - degrades POAS silently, while ROAS keeps working correctly because it never depended on cost data in the first place.
Which one should you use?
Use POAS when
- You sell a catalog where margin varies significantly by product - some items are commodity-priced, others are high-markup.
- You have a reliable, current cost-of-goods feed you can pipe into your conversion values or bidding.
- Your ROAS looks healthy and consistent but you suspect the business isn't actually more profitable, because revenue is hiding a margin problem.
- You want the bid strategy itself to favor higher-margin products, not just your reporting to reflect margin after the fact.
Use ROAS when
- Your margin is roughly consistent across whatever you're advertising, so revenue is a reasonable proxy for value.
- You don't have a reliable per-SKU cost feed and building one isn't practical right now.
- You are a service business or single-product seller where cost of goods doesn't meaningfully vary by conversion.
- You need a number every platform reports natively without any custom setup.
Common questions.
How do I actually get POAS into my ad platform?
You feed a profit-adjusted number as the conversion value instead of raw purchase revenue, typically by sending revenue minus cost of goods through your conversion tracking or a server-side feed, so what the platform calls conversion value is really gross profit. This usually requires a margin field per SKU or order that stays current, not a one-time setup.
Why would a product with a great ROAS have a bad POAS?
Because ROAS only sees the sale price, not what the product cost you. A high-ROAS item with thin margin - a loss leader, a heavily discounted SKU, a product with high fulfillment cost - can be an efficient revenue generator and a poor profit generator at the same time, and only POAS shows the difference.
Is POAS the same thing as feeding Target ROAS a lower number?
No. Lowering a Target ROAS just tells the bidder to accept a worse revenue-to-spend ratio across the board, it doesn't tell the bidder which products are actually more profitable. POAS changes what counts as value in the first place, so the bidder can favor a high-margin product over a high-revenue one even at the same price point.
What breaks a POAS setup the fastest?
A margin feed that goes stale - a cost increase that never gets updated, a promotional price not reflected in the cost basis, or a new SKU launched without a margin entry. Because the bidder trusts the number completely, a wrong feed doesn't cause an obvious error, it just quietly optimizes toward the wrong products.
Or stop choosing between them.
AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.
Related comparisons
- ROAS vs ROI
- MER vs ROAS
- ACoS vs ROAS
- Break-Even ROAS vs ROAS
- LTV vs ROAS
- AOV vs ROAS
- MER vs ROI
- POAS vs ROI