Stop exporting Google 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 Google Ads reporting in Google Sheets without exporting anything or breaking a formula. Opera reads your existing sheet, pulls spend, impressions & clicks, conversions (modeled) 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.
Google Ads API (GAQL) — queries like SELECT campaign.name, metrics.cost_micros, metrics.conversions, segments.date FROM campaign per customer ID. Cost arrives in micros (÷ 1,000,000); conversions are modeled and credited to the click date, so recent days restate upward.
Opera pulls with an explicit date range and conversion window, and re-pulls a trailing window so restated days update in your report instead of silently diverging.
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 Google 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 & clicks, conversions (modeled) from Google 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.
Google reports modeled conversions — estimated, not a 1:1 observed count — and credits them to the click date, not the conversion date. So today's numbers for recent days keep revising upward as conversions land. Auto-tagging (GCLID) and your own UTMs can also disagree. Pull with a stable conversion window and expect the last several days to change after the fact.
Google Ads's self-reported numbers won't match what your MMP attributes. Opera lines Google 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 Google 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.