ROAS Checklist for Growth Leads

Why ROAS Alone Fails

ROAS measures efficiency, not profitability. A channel can deliver 4.0 ROAS and still lose money if CAC payback exceeds cash runway or if unit economics don't account for fulfillment, returns, and platform fees.

ROAS also ignores customer lifetime value (LTV) contribution. A channel with 2.5 ROAS on first purchase but 60% repeat rate generates different long-term value than a 4.0 ROAS channel with 10% repeat rate.

Attribution windows create false comparisons. A 7-day click window captures different revenue than 30-day view-through attribution. Channels measured on different windows cannot be ranked by ROAS alone.

ROAS Thresholds by Channel and Stage

Threshold setting depends on business model, margin structure, and growth stage. Early-stage brands (< £500k MRR) often operate at 2.0 - 2.5 ROAS to fund growth; mature brands (> £2M MRR) typically require 3.5 - 5.0 ROAS to justify continued spend.

Paid Search (Google, Bing): 3.5 - 5.0 ROAS baseline. Below 3.0 = pause or restructure. Seasonal variance of ±20% is normal.
Meta (Facebook, Instagram): 2.5 - 3.5 ROAS baseline. Highly dependent on audience saturation and creative refresh cycles. Below 2.0 = signal to test new audiences or pause.
TikTok / Emerging platforms: 1.5 - 2.5 ROAS acceptable during scaling phase. Treat as customer acquisition investment, not immediate profitability.
Email / SMS (owned channels): 4.0 - 8.0 ROAS typical. Below 3.0 = list hygiene or segmentation issue.
Affiliate / Performance partnerships: 1.5 - 2.5 ROAS after commission. Validate incrementality before scaling.

Calculation and Attribution Setup

ROAS calculation requires clean data separation. Use platform-native attribution (Meta Conversions API, Google Analytics 4 conversion tracking) as primary source, then validate against backend order data.

Set a consistent attribution window across all channels. 7-day click is standard for paid social; 30-day click + 1-day view for search. Document the window and review quarterly.

Exclude test orders, employee purchases, and refunds from ROAS calculation. Include shipping revenue only if it's a material margin driver (typically not for DTC).

Revenue denominator: Use attributed revenue only (not gross sales). Deduct refunds within the attribution window.
Cost numerator: Include all platform spend, management fees, and creative production costs if > 5% of monthly ad spend.
Multi-touch: If using multi-touch attribution, report both first-click and last-click ROAS separately. Last-click is standard for channel comparison.
Holdout testing: Run 5 - 10% of traffic as control group monthly to measure true incrementality. Adjust ROAS downward by 20 - 40% if incrementality testing shows overlap.

Common Failure Modes

ROAS inflation occurs when attribution windows don't match actual customer behavior. A 7-day window on a 21-day consideration cycle will undercount assisted conversions and inflate channel ROAS.

Audience overlap between channels creates double-counting. The same user may see Meta ads and then search for the brand, triggering both a Meta conversion and a Search conversion on the same order. Measure overlap monthly and adjust spend allocation accordingly.

Seasonal and promotional noise distorts trend analysis. Black Friday ROAS is not comparable to January ROAS. Segment reporting by promotion type and compare year-over-year.

Platform attribution drift happens after iOS privacy changes and cookie deprecation. Expect 15 - 30% variance between platform-reported and GA4-reported ROAS. Use backend order source as truth.

Decision Rules for ROAS Thresholds

Use ROAS as a screening metric, not a stopping rule. Pair it with CAC payback, LTV contribution, and cash flow impact before pausing a channel.

If ROAS > threshold AND CAC payback < 90 days: Scale spend 20 - 30% month-over-month.
If ROAS > threshold AND CAC payback > 120 days: Hold spend flat. Investigate LTV or repeat rate.
If ROAS < threshold AND channel is < 3 months old: Run incrementality test. If true ROAS (after holdout adjustment) is still below 70% of threshold, pause.
If ROAS < threshold AND channel is > 6 months old: Audit creative, audience, and bid strategy. If no improvement in 2 weeks, reduce spend by 50%.
If ROAS declines > 20% month-over-month: Investigate creative fatigue, audience saturation, or platform algorithm changes within 48 hours.

Reporting and Monitoring Cadence

Daily monitoring of ROAS is noise. Weekly reporting (Monday morning, 7-day rolling average) is standard. Monthly reporting for strategic decisions.

Set up alerts: Notify team if any channel ROAS drops below 80% of threshold for 3 consecutive days.
Track ROAS by campaign, audience segment, and creative variant. Aggregate to channel level for threshold comparison.
Report both attributed ROAS and incrementality-adjusted ROAS. Show the gap to stakeholders.
Maintain a ROAS trend sheet (12-month rolling). Flag seasonal patterns and platform changes.

ROAS vs. Profitability Reconciliation

A profitable business can have low ROAS if margins are high. A brand with 60% gross margin and 2.0 ROAS is more profitable than a 40% margin brand with 3.0 ROAS.

Calculate true unit economics: (Revenue - COGS - Fulfillment - Payment Processing - Returns) / Ad Spend. This is the real ROAS for profitability decisions.

For every £1 of ad spend, track how much reaches contribution margin. If contribution margin is 40% and ROAS is 3.0, true margin-based ROAS is 1.2 - still positive, but lower than headline ROAS suggests.

Questions

FAQ

What ROAS should we target for a new DTC brand?

Start with 2.0 - 2.5 ROAS as a floor during the first 6 months. Prioritize customer acquisition and LTV data collection over immediate profitability. Once you have 500+ repeat customers and LTV data, raise the threshold to 3.0 - 3.5. Mature brands (> £2M MRR) should target 4.0+.

How do we handle ROAS when we run promotions?

Segment promotion ROAS separately from baseline ROAS. A 40% discount will inflate ROAS short-term but may cannibalize full-price sales. Report both promotional and non-promotional ROAS, and measure incrementality via holdout testing to isolate true lift.

Should we use platform-reported ROAS or GA4 ROAS?

Use platform-reported ROAS for day-to-day optimization (it's faster and more granular). Use GA4 or backend order data as the source of truth for monthly reporting and threshold decisions. Document the variance and investigate if it exceeds 15%.

How do we account for customer lifetime value in ROAS decisions?

Calculate repeat rate and average repeat order value for each channel. If Channel A has 2.5 ROAS but 50% repeat rate vs. Channel B with 3.5 ROAS and 10% repeat rate, Channel A may have higher true LTV. Report both metrics and weight ROAS decisions by LTV contribution, not ROAS alone.

Want this on your account?

Thirty minutes. Bring the number that keeps you up.

Book a demo