The formula, the data sources, the pitfalls — and how to keep new customers current across platforms without rebuilding it every week.
The single most important definition in your whole report — the activation event that turns an install into a customer.
new customers 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. 1,910 first transactions attributed this week against 12,480 installs — reporting installs as 'customers' would overstate the real number by more than 6×.
Counting installs as customers, or letting attribution-window changes silently move the count between reports.
Opera pulls the inputs across AppsFlyer and your ad platforms, applies your new customers / purchases 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 new customers report with this week's numbers by channel, and flag anything off target."
Skip automation while the new customers / purchases 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.