Nothing changes in your account without a receipt .
Change History Alert sweeps your Google Ads account once a day, pulls the change_event log via the API, and shows you who did what and when. It reads who has access to your account, so the people who belong there are not reported as intruders — only the ones you asked about, and the ones nobody recognises.
A receipt of every hand that touched your account.
Each morning's sweep reviews every change Google Ads logged since the previous run, and surfaces the ones made by someone you chose to watch — or by anyone Lyra has not seen on the account before.
Illustrative example · one account · one morning's sweepThree small rails, one morning alert.
Change History Alert isn't clever. It's a scheduled read of Google's own change log, a bit of attribution work, and an alert in the app — plus Slack for agency accounts. That's the point — boring, reliable, auditable.
Reads Google's change_event log daily.
Each morning, Change History Alert queries Google Ads API v24.1 for every change_event logged in your account since the last sweep. One pass, your whole account.
Cadence: daily · every morningWho did what, and what was there before.
Each change is annotated with the user identifier (team member, agency, or Google automation), the exact timestamp, and the fields that changed — all pulled straight from Google's API. No inference, no guessing.
Source: change_event · Google Ads API v24.1One summary, every morning.
Findings appear in your Suggestions feed and Lyra raises them in chat. Agency-managed accounts also get a morning Slack digest. Every run is retained in tool_execution_logs for audit.
Channel: in-app · Slack for agencies · dailyThe honest answers to the usual onboarding questions.
Is this actually 24/7?
No — and we won't pretend otherwise. Change History Alert runs once a day. You get a summary every morning that covers the previous day's changes. Nothing in Lyra intercepts changes in real time. Auto-Apply Guard, also a daily sweep, reduces one common source of unrequested changes by turning off Google's auto-apply subscriptions you haven't whitelisted.
Does it read from Google Ads or from a scraped log?
Direct from Google Ads API v24.1, via the change_event GAQL query. Same source Google uses in its own UI. No scraping, no synthetic data.
Where do the alerts go?
Findings appear in your Suggestions feed inside Lyra, and Lyra brings them up in chat. If your account is agency-managed, a summary also goes to your shared Slack channel each morning. Either way the run is recorded, so there is a permanent audit trail.
Can I filter out certain change types?
The report groups changes by day, person and type of resource, so you can skim. Filtering by change type isn't a configurable feature; who you hear about is set in the roster.
What if the sweep fails?
The run record sits in tool_execution_logs. If the cron misses a morning, the next successful run covers the gap — we query Google since the last successful sweep's timestamp (up to the 30 days Google keeps), not since 24h ago. You don't lose changes to a failed run.
Run the audit.
Keep the findings.
Connect your account and let Lyra run its 8 tools for 14 days. If the projected waste recovery isn't worth at least 10× the $49, don't pay. You keep every insight either way.
Read-only connect · write access opt-in per tool · GDPR compliant