Reporting and campaign operations built around the metrics multi-market apps teams actually answer for.
Multi-market growth runs market by market — each market has its own CAC, creative and seasonality. Reporting means slicing AppsFlyer and ad-platform data by market and tying spend to purchases across many markets at once.
Front-end clicks and installs are the top of a longer funnel — and for multi-market apps, the metrics that decide profitability live further down it:
impression → install → registration → first purchase → repeat purchase
Purchases and cost per purchase by market; market-level CAC; first-purchase and repeat-purchase rates; spend reconciled with attribution per market.
Markets behave like separate businesses — different economics, seasonality and creative. A single blended CAC across markets is actively misleading; the report has to slice by market first, then roll up.
"Fill last week's US weekly report with AppsFlyer spend and purchases from US_ campaigns."
Opera resolves the market workbook, reads the weekly tab's structure, pulls spend (Master API) and event-level purchases (Raw Data Pull API) filtered to geo = US and the US_ prefix, computes cost per purchase, previews and appends — then repeats the same run for every other market on its own schedule.
Opera reads your existing report, pulls fresh data across platforms, appends it safely (formulas preserved), reconciles spend against attribution, and posts a summary to Slack or email — on the cadence you set.
"Update this week's report with spend and new customers by channel and market, and flag anything off target."
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.
Three minutes: a plain-language request, a Sheet schema read, an AppsFlyer pull, a previewed append, a Slack summary — then a paused campaign launch.