The formula, the data sources, the pitfalls — and how to keep ROAS current across platforms without rebuilding it every week.
Decide blended vs cohort up front: blended ROAS divides all revenue in a window by all spend; cohort ROAS tracks revenue from a specific install cohort as it matures. They answer different questions.
ROAS pulls from multiple platforms, each with its own definition and refresh lag. The moment you finish the report it's out of date — so it gets rebuilt next week. The fix is to automate the inputs and the write-back, not just the chart on top.
Illustrative. A week-20 install cohort has generated $61,000 against $25,000 of spend → cohort ROAS = 2.44. That same week's blended ROAS read 1.9, only because newer cohorts hadn't matured yet.
Mixing cohort revenue with blended spend, or reading recent ROAS as final — revenue lag (especially under SKAN) makes the last few days look artificially low.
Opera pulls the inputs across AppsFlyer and your ad platforms, applies your return on ad spend definition, reconciles the sources, and appends the result to your existing report — append-only, formulas preserved — then schedules it and posts a summary.
"Refresh the ROAS report with this week's numbers by channel, and flag anything off target."
Related: CAC · LTV · retention
Skip automation while the return on ad spend definition is still being argued about, while the report's structure changes weekly, or for one-off analyses. Automation pays on stable, recurring reports — lock the definition first, then put it on a schedule.
Opera is built to touch production reports and live ad accounts without breaking anything:
See this running on your own reports.A 45-minute workflow audit maps your current process and shows exactly what Opera automates — step by step.
Estimate the hours and fully-loaded labor cost your team spends on recurring reports — and what Opera gives back.