AdsLedger
Google Ads reporting, without touching your campaigns.
AdsLedger gives teams one clean workspace for OAuth connectors, Google Ads cabinets, campaign rows, monthly spend, and creative asset performance. It is built for review, not campaign editing.
How AdsLedger turns OAuth into reporting.
A connector does not become a black box. Every step from authorization to dashboard rows stays visible, named, queued, and easy to explain.
Add a named Google Ads connector and keep its status visible.
Review customer accounts inside the connector without losing context.
Data refreshes run in workers, not inside a long browser request.
Campaigns, monthly spend, and asset rows land in one workspace.
One workspace for campaigns, spend, and assets.
The page is built around what users actually need to inspect: which connector is active, which cabinet is selected, what campaigns spent money, and which assets produced rows.
Designed so reviewers know what the app will not do.
- AdsLedger does not create, edit, pause, delete, or modify Google Ads campaigns.
- AdsLedger does not change bids, budgets, billing settings, or account configuration.
- Google Ads data is used for reporting views, connector status, exports, and internal review only.
- Users can request a refresh, while background queue workers keep API syncs controlled.
Users grant reporting access per Google Ads account.
Workers request metrics and asset rows from approved scopes.
Rows become dashboard tables, KPIs, and monthly summaries.
Teams can inspect and export data without edit controls.
Refreshes run in the background, not in the browser.
A user can request fresh data, then continue working. AdsLedger shows queue state, sync progress, last sync, and the next automatic refresh with no campaign-editing controls.
Open the prototype, then connect real reporting.
The demo subdomain shows the intended product shape with sample data, clear prototype labeling, and the same read-only boundaries used by the production workspace.