Reporting and campaign operations built around the metrics mobile gaming teams actually answer for.
Gaming UA is high-volume and creative-hungry, with ROAS measured by network and cohort. Reporting has to keep pace with rapid creative turnover and spend that moves daily across many ad networks.
Front-end clicks and installs are the top of a longer funnel — and for mobile gaming, the metrics that decide profitability live further down it:
impression → install → tutorial complete → first purchase → payer retention
CPI and ROAS by network and install cohort; D1/D7 retention; ARPU and payer rate; creative-level spend and performance.
Creative fatigue is fast and ROAS is cohort-based, so report ROAS by install cohort and network — and expect recent cohorts to keep maturing (D7 and D30 ROAS rise for weeks after install). Judging a fresh cohort on day-1 revenue kills winning campaigns early.
"Update the UA report with installs, CPI and D7 ROAS by network for last week's cohorts, and flag creatives whose CPI rose week over week."
Opera pulls network spend, AppsFlyer installs and cohort revenue, computes D7 ROAS per install cohort (not blended), appends by network, and surfaces fatiguing creatives in the summary.
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.