EasyRingo's planned Google Ads API use case
EasyRingo is a self-funded English listening and pronunciation learning product. We advertise only EasyRingo through our own Google Ads account. We are not an agency, do not manage client accounts, and do not sell or white-label advertising software.
Who will use it
One authenticated EasyRingo owner/operator will request a private performance report from the existing operations dashboard. No learner, advertiser client, or other third party will receive Google Ads API access.
What it will read
After Basic Access approval, the server will use GoogleAdsService.SearchStream to read campaign-level aggregate impressions, clicks, cost_micros, and conversions for EasyRingo's owned account. The expected volume is about one report request per day.
Data flow and security
- OAuth credentials, refresh tokens, and the developer token remain server-side secrets and are never sent to the browser.
- The Edge Function verifies the signed-in operator against an administrator allow-list before any report request.
- A sanitized daily snapshot is cached so dashboard reloads do not repeat the API report request.
- Stored values contain aggregate campaign performance and timestamps only; no learner or end-user personal data is requested from or sent to the Google Ads API.
Strictly excluded
This integration will not create or change campaigns, ads, bids, budgets, audiences, billing, remarketing, or conversion tracking. It will not call mutate operations, access third-party accounts, offer public API access, or resell Google Ads data.
Private reporting card
The placeholders intentionally contain no fabricated metrics. Reporting will be implemented only after Google approves the required access and OAuth setup is complete.