EN DE
Get a Free Audit

ROAS vs POAS: Are You Buying Revenue or Profit?

If you run e-commerce ads and your dashboard says 4x ROAS, you still do not know whether you made money. ROAS (Return On Ad Spend) measures revenue against ad cost. POAS (Profit On Ad Spend) measures gross profit against ad cost. The gap between those two numbers is where most online stores quietly lose margin while celebrating a healthy-looking return.

Here is the short answer: ROAS is the right metric when your products have similar margins and you mostly need a fast, simple efficiency signal. POAS is the right metric the moment your catalog mixes high-margin and low-margin SKUs, runs discounts, or carries returns, because that is exactly when revenue stops being a reliable stand-in for profit. The bigger and more varied your range, the more ROAS lies to you.

This page breaks down how the two metrics behave, what it takes to feed profit data into Google Ads and Meta, and a practical sequence for moving from ROAS to POAS without breaking your existing campaigns. The goal is simple: stop optimizing toward the number that looks good and start optimizing toward the number that pays your salary.

Head-to-Head Comparison

Feature ROAS POAS
What it measures Revenue generated per euro of ad spend. A 5x ROAS means 5 euros of revenue for every euro spent Gross profit generated per euro of ad spend, after cost of goods, shipping and returns are subtracted from revenue
Formula Revenue divided by ad spend, easy to read straight from any ad platform or GA4 report Gross profit divided by ad spend, needs a margin figure attached to every order before it can be calculated
Data needed Conversion value and spend, both already tracked by default in Google Ads, Meta and GA4 Conversion value plus per-product cost of goods, shipping cost and a returns assumption fed back to the platform
Setup effort Low, works out of the box once conversion tracking is in place Medium to high, requires sending profit as the conversion value via the feed, server-side tracking or a margin tool
Risk of misleading you High when margins vary, because the algorithm chases cheap, high-revenue, low-profit products Low, the algorithm bids toward the orders that actually contribute money to the business
Effect on smart bidding Target ROAS pushes spend toward whatever drives revenue, regardless of whether that revenue is profitable Profit-as-value bidding teaches the algorithm to favor your genuinely profitable SKUs and audiences
Handling discounts Treats a discounted sale and a full-price sale as equally good if revenue matches Automatically downranks discount-heavy orders because the profit attached to them is lower
Handling returns Counts returned orders as wins unless you manually subtract them later Bakes a returns rate into the profit value, so high-return products stop looking like top performers
Best for Single-margin or flat-margin catalogs, early-stage stores, quick efficiency checks Multi-margin catalogs, marketplaces, stores running frequent promotions, scaling accounts
Reporting clarity Easy to explain to anyone, but disconnected from the P&L Maps directly to contribution margin, harder to game, board-ready
Typical benchmark talk Teams chase round targets like 3x or 4x ROAS that mean nothing without margin context Teams target a POAS above 1.0 as breakeven on gross profit, then push for the margin buffer they actually need

ROAS Strengths

  • Available instantly with no extra plumbing, so you can read it the day conversion tracking goes live
  • Universally understood across teams, agencies and platforms, which makes it easy to brief and benchmark
  • Perfectly adequate when every product carries roughly the same margin, where revenue and profit move together
  • A fast efficiency signal for spotting campaigns that are obviously bleeding before deeper analysis
  • Built natively into Target ROAS bidding, so the whole platform ecosystem already speaks its language

POAS Strengths

  • Optimizes toward money the business actually keeps, not vanity revenue that evaporates after costs
  • Stops smart bidding from over-investing in low-margin and discount-driven SKUs that look good on revenue
  • Bakes returns into the value signal so high-return products stop quietly draining your margin
  • Aligns ad reporting with the P&L, which makes budget conversations with finance far easier
  • Scales cleanly: the more varied your catalog gets, the bigger the advantage over plain ROAS

When to Use ROAS

Stick with ROAS when your catalog has flat or similar margins across products, when you are early and just need a clean efficiency read, or when you do not yet have reliable per-product cost data to feed back to the platforms. There is no shame in running ROAS well: a single-margin dropshipping store or a service business with one offer gets almost nothing extra from POAS and a lot of added complexity. Use ROAS as your daily steering metric, but pair it with a monthly margin check so a shift in product mix does not sneak past you. ROAS is also the sensible starting point while you build the data pipeline POAS depends on.

When to Use POAS

Move to POAS when your margins genuinely vary, when discounts and promotions are a regular part of your calendar, or when returns are material to your category, think apparel, footwear or furniture. The signal that you have outgrown ROAS is usually this: a campaign with great ROAS that somehow does not grow the bank balance. That mismatch means the algorithm is buying revenue you cannot bank. POAS fixes it by sending profit as the conversion value, so smart bidding starts favoring the orders that contribute real margin. It is more work to set up, but for any store past the early stage with a mixed catalog, it is the metric that should drive bidding decisions.

Our Verdict

For most growing e-commerce businesses, the honest recommendation is to treat ROAS as the training wheels and POAS as the destination. ROAS is not wrong, it is incomplete: it answers how much revenue you bought without telling you whether that revenue was worth buying. The day your catalog spans different margins, runs promotions or sees returns, ROAS starts steering budget toward the wrong products and you will feel it in the P&L long before you see it in the dashboard.

The sequencing that works in practice: start on ROAS to get clean conversion tracking and a stable account, then build the data layer that POAS needs (per-product cost of goods, shipping, a returns assumption) and feed profit as the conversion value into Google Ads and Meta. Run both metrics side by side for a few weeks so you can see exactly which products and campaigns look very different under profit. Only once you trust the profit value should you switch your smart bidding to optimize on it. This is squarely a tracking and measurement project, and getting the conversion value right is the part that makes or breaks it.

Bottom line: if you sell one thing at one margin, ROAS is fine, keep it simple. If you sell a varied catalog at scale, POAS is not a nice-to-have, it is the metric that should govern your bidding, because it is the only one tied to the money you actually keep. The accurate profit value depends on solid GA4 reporting and server-side conversion data underneath, so treat the measurement setup as the foundation, not an afterthought.

Frequently Asked Questions

ROAS divides revenue by ad spend, so a 4x ROAS means four euros of revenue per euro spent. POAS divides gross profit by ad spend, so it tells you how much money you actually kept after cost of goods, shipping and returns. ROAS can look great while POAS is barely above breakeven, which is exactly why a store with strong ROAS can still struggle to turn a profit. POAS is the metric tied to your real contribution margin.

No. POAS is better when margins vary, when you discount often or when returns are material, because those are the situations where revenue stops being a good proxy for profit. If you sell products with roughly identical margins and few returns, ROAS and POAS move together, and the extra setup work POAS demands buys you little. Pick the metric that matches your catalog, not the one that sounds more sophisticated.

You send profit, rather than revenue, as the conversion value. That means attaching a margin figure to each order, usually by enriching your data layer with per-product cost of goods and shipping, then passing the calculated profit through your conversion tracking, often via server-side tagging or a dedicated margin tool. Once profit is the value the platform sees, Target ROAS bidding effectively becomes Target POAS bidding. The accuracy of that profit number is everything, so the tracking setup matters more than the metric itself.

A POAS of 1.0 means your gross profit exactly equals your ad spend, which is breakeven before overheads. Most stores need a POAS comfortably above 1.0 to cover fixed costs and still make money, but the exact target depends on your margin structure and how much profit you are willing to reinvest into growth. Rather than chasing a generic number, set the POAS that leaves the contribution margin your business actually needs after ad spend.

Yes, and you should during the transition. Keep ROAS visible because it is universally understood and useful for quick efficiency checks, but build POAS alongside it so you can spot the campaigns and products that look very different under profit. Running both for a few weeks before you switch your bidding gives you the confidence that the profit value is accurate. A clean GA4 reporting layer makes maintaining both views straightforward.

Get your bidding optimized for profit, not just revenue

We set up the tracking and measurement layer that lets you feed real profit into Google Ads and Meta, then move your campaigns from ROAS to POAS without losing performance along the way. Book a call and we will map out the profit data you need first.