Stop exporting Apple Search Ads data and pasting it into Google Sheets by hand. Opera reads your existing sheet, appends the right numbers to the right rows, and keeps it current.
Yes — you can automate Apple Search Ads reporting in Google Sheets without exporting anything or breaking a formula. Opera reads your existing sheet, pulls spend, impressions & taps, tap-through & view-through installs at your grain, and appends each period to the right rows on a schedule you set.
Opera pulls at the exact grain you report on and uses your KPI definitions, not generic defaults.
Campaign Management API reports — spend, impressions, taps and installs at campaign, ad group and keyword grain, by storefront and day. Keyword-level rows explode quickly, so Opera pulls at the grain your report actually uses.
ASA's own tap-through and view-through installs overlap MMP-attributed installs — Opera keeps them in separate columns, never summed.
A correct pull is mostly correct filtering. Opera applies this client's rules on every run — not whoever-exported-it's defaults:
Date ranges resolve in the right timezone, campaign prefixes scope to the right market, and event names match this client's taxonomy exactly.
Every cycle, someone exports Apple Search Ads, reshapes the columns, finds the right week, pastes it in, fixes formatting, and hopes no formula broke. It's an hour lost on every report, every client, every week.
"Update last week's report with spend, impressions & taps, tap-through & view-through installs from Apple Search Ads, by channel."
Opera reads your sheet's structure first — tabs, headers, weekly blocks, monthly sections — then appends the new data to the right row. Formulas are extended, never overwritten; writes are append-only by default.
Apple Search Ads reports its own tap-through and view-through installs, which overlap with the installs your MMP attributes — sum both and you double-count. ASA's superpower is keyword-level reporting, but the row count explodes fast, so decide the grain (campaign vs keyword) before you automate or the sheet becomes unreadable.
Apple Search Ads's self-reported numbers won't match what your MMP attributes. Opera lines Apple Search Ads spend up against AppsFlyer (or Adjust) and your other platforms in the same report, so the blended picture holds together.
Illustrative — the structure of one appended week, not real figures.
| Week | Spend | Clicks | Conversions | CPA | ROAS |
|---|---|---|---|---|---|
| Wk 23 | $22,400 | 41,900 | 1,180 | $18.98 | 2.4 |
| Wk 24 | $24,150 | 44,300 | 1,305 | $18.51 | 2.6 |
Opera turns the weekly Apple Search Ads export into a scheduled job that keeps your existing Google Sheets current and reconciled — so your team spends its time on decisions, not data entry.
Run it daily, weekly or monthly. Opera refreshes the data, updates the sheet, and posts a Slack or email summary — without anyone touching an export again.
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.