Clients
Client
Context
Recent activity for this client
Ask the Data
Advanced: raw GAQL query
Saved reports
Workflows
A workflow is a collection of saved reports (build reports in Ask the Data, then add them here or when saving). Run it any time — output is saved as a dated markdown report in History & Outputs — or put it on a schedule in Automations.
Automations
Run a workflow on a cadence, grouped by client. Runs happen while the dashboard server is running; a missed run fires on next startup. Outputs land in History & Outputs.
Context & Goals
Record the strategy behind each piece of each client's account (Context) and what each piece is trying to achieve (Goals) — at every level of the hierarchy. Both are stored with this connection and feed the AI engine during Assessments.
Assessments
Assess a goal against report data: the AI produces findings and suggestions; you approve, deny, or add context; approved changes get implemented in Google Ads by you, then followed up at an interval looking for the expected change.
New assessment
Change Log
Changes made in Google Ads itself (by any user or tool). Google retains ~30 days.
History & Outputs
Saved report files
Run log
Settings
Google Ads connections
A connection is one Google Ads API identity: a Google login (authorized via OAuth), a developer token, and the MCC it manages. Everything you build — reports, workflows, context, goals, assessments — belongs to a connection. Config is stored encrypted per connection.
AI engine
Powers Ask the Data suggestions, Assessments, and follow-up verdicts. Falls back
down the chain if an engine is unavailable. Per login — each login has its own
engine config and API keys, stored encrypted with your login.
Claude API
Local model (OpenAI-compatible: Ollama, LM Studio, vLLM…)
Logins
Each login is a separate dashboard: it has its own connections and sees only its own reports, workflows, context, and assessments.