How is Apple Search Ads ROAS computed?

ROAS = Revenue ÷ Ad Spend over a defined attribution window. For ASA, revenue comes from your backend (deterministic per-user) or from SKAN conversion values (aggregate). Spend comes from the Ad Services API. The two are joined at campaign or ad group level.

What ROAS is considered good?

A healthy 30-day ROAS depends on margin and payback tolerance. Rough guides: gaming 0.5-1.0× by Day 7, 1.5-2.0× by Day 30; subscription 0.3-0.5× by Day 7, 0.8-1.2× by Day 30; e-commerce 1.5-3.0× by Day 7. Long-term ROAS (90/180/360 day) is the real test.

Should I optimize for ROAS or CPI?

For revenue-monetized apps, ROAS. For ad-monetized free apps where every install carries similar value, CPI. For subscription apps with multi-month payback, monitor both: CPI as the leading indicator, ROAS as the lagging truth.

What is ROAS in Apple Search Ads? Return on Ad Spend Explained

What is ROAS?

Return on Ad Spend (ROAS) is the ratio of revenue generated by an ad campaign to the amount spent. It is the cleanest single-number efficiency metric for revenue-monetized apps.

The formula:

ROAS = Revenue / Ad Spend

A campaign that spent $1,000 and generated $3,500 has a ROAS of 3.5× (or 350%). A campaign that spent $1,000 and generated $700 has a ROAS of 0.7× (still upside down).

ROAS is not the same as profit margin — ROAS includes revenue gross of platform fees, refunds, and operating costs. Always pair it with margin context.

ROAS over time windows

ROAS is window-dependent. The same campaign can have:

Day 1 ROAS: 0.3×
Day 7 ROAS: 0.8×
Day 30 ROAS: 1.4×
Day 90 ROAS: 2.1×
Day 360 ROAS: 3.8× (full LTV captured)

For SKAN-driven measurement, the new SKAN 4.0 postback windows (0-2 / 3-7 / 8-35 days) give you three discrete revenue snapshots per install — closer to a true ROAS curve than SKAN 3.0 ever was.

ROAS benchmarks by vertical (rough, 2026)

Vertical	Day 7 ROAS	Day 30 ROAS
Mobile games (casual)	0.4 – 0.8×	1.0 – 1.5×
Mobile games (mid-core)	0.3 – 0.6×	1.0 – 1.8×
Subscription apps	0.2 – 0.5×	0.7 – 1.2×
E-commerce	1.0 – 2.5×	1.8 – 3.5×
Finance	0.3 – 0.7×	1.0 – 1.8×
Health & fitness	0.2 – 0.5×	0.8 – 1.4×

These are extremely rough — your own ROAS curve will depend on cohort retention, ARPU, and seasonality.

How to improve ROAS

ROAS depends on three things: traffic quality, conversion rate, and ARPU per acquired user.

Improve traffic quality. Brand and high-intent Category keywords convert and monetize far better than broad Search Match. Reallocate budget toward proven high-ROAS clusters.
Lift conversion rate. Custom Product Pages targeted to keyword intent typically lift tap-to-install CR by 10-25%, with downstream lift on ROAS.
Raise ARPU through monetization. Outside ASA’s scope but the biggest ROAS lever long-term: better paywalls, retention loops, and upsell sequences.

ROAS in Apple Search Ads tooling

Apple Search Ads dashboard does not show ROAS directly — only spend and install data. ROAS measurement requires:

First-party: Your backend joins ASA campaign IDs to revenue events per user.
MMP-based: AppsFlyer / Adjust / Kochava / Branch ingest ASA data via the API and expose ROAS dashboards.
SKAN-based: SKAN conversion values encode revenue tiers; aggregate ROAS comes from the postbacks.

For ASA-only operators (no MMP), first-party measurement is usually enough — and is deterministic, unlike SKAN.

How ASAPilot helps

ASAPilot connects to your Apple Search Ads account via the official API and supports joining external revenue data (via webhook or scheduled CSV import) to compute ROAS per campaign and per ad group. ROAS metrics appear in account audit findings — anything below your defined target threshold gets flagged.

See audit guide and pricing.

CPI — the upstream install cost
CPA — cost per acquired customer
SKAdNetwork — privacy-preserving attribution standard