WebmasterID logoWebmasterID
Analytics metrics

Return on ad spend (ROAS)

Return on ad spend (ROAS) is the revenue attributed to advertising divided by the cost of that advertising, usually expressed as a ratio or percentage. It answers 'how much revenue did each unit of ad spend bring back'. ROAS is not ROI — it ignores product margins and other costs — and its numerator depends entirely on the attribution model, so the same campaign can show very different ROAS under different rules.

Verified against primary sources

What this means

ROAS = revenue attributed to ads ÷ ad cost. A ROAS of 4 (or 400%) means four units of revenue for every one spent on advertising. It is the headline efficiency metric for revenue-driven ad campaigns and the target many automated bidding strategies optimize toward.

ROAS is not ROI

ROAS uses gross revenue, not profit. It ignores the cost of goods, fulfilment, and overhead, so a high ROAS can still be unprofitable if margins are thin — return on investment (ROI), which nets out costs, is the profitability metric. ROAS also inherits all attribution sensitivity: last-click, data-driven, or view-through models credit revenue differently, and a longer lookback window pulls more revenue into the numerator. Compare ROAS only when the attribution rules are held constant.

How it appears in analytics and logs

A ROAS figure tells you the revenue returned per unit of ad spend. A change can reflect real performance or simply a different attribution model crediting more or less revenue to ads.

Diagnostic use case

Use ROAS to compare revenue efficiency across campaigns, while remembering it excludes margins and is only as reliable as the attribution behind the credited revenue.

What WebmasterID can help detect

WebmasterID can capture purchase and value events first-party, so the revenue numerator in ROAS is grounded in your own measured outcomes rather than third-party-cookie attribution.

Common mistakes

Privacy and accuracy notes

ROAS is a revenue-to-cost ratio reported in aggregate; it needs no personal identifiers. Revenue values should be modelled without exposing individual purchases.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.