Every account change, written down.
Account Diary is the always-on logbook that backs the rest of Lyra. Manual notes from your team, actions taken in Lyra, change-history events from Google, and Slack messages from the channels you configure — every entry attributed, every entry timestamped, every entry searchable. The Lyra Agent reads it for context; actions you confirm in chat are logged, and it does not write notes of its own.
Four sources, one unified timeline.
Each Lyra account writes to one diary. Manual notes go in via the API or UI. Actions taken in Lyra log themselves. Slack messages sync daily. Google Ads change-history events sync daily. All four land in `account_diary_entries` with the same attribution shape.
- manual · performance_note
- decision
- slack_message
- change_history_*
- created_by
- source_user_name
- created_at
- By type · source · author
- By importance level
- By date range
An audit trail you can search.
Illustrative example: a few entries from one account. Different sources, different actors, one timeline. The badges show importance level; the type chip shows where the entry came from.
One table, four ways in.
All entries live in a single `account_diary_entries` table with a consistent attribution shape. The differences are upstream — how they get there, who writes them, when they fire.
Notes you write.
Free-text entries from your team via the diary UI or API. Title, content, importance level, optional decision metadata for entries you want flagged as a decision.
Lyra actions, logged.
When an action is taken in Lyra — a recommendation applied, reopened or closed, a change undone, an action you confirm in chat — it writes a decision entry.
Channel messages, captured.
For agencies: configure a Slack channel per client; the daily sync captures recent messages with `source_user_name` set to the Slack author. Useful for tying client questions and decisions back to a specific account.
Google's audit log, mirrored.
Google Ads change-history events (budget edits, status changes, keyword, ad group and ad edits) sync into the diary daily.
Who wrote it · always answerable.
Every entry has `created_by` (Lyra user or 'system') and `created_at`. Slack entries also carry `source_user_name`, the Slack author.
Context for the chat, not authorship.
The Lyra Agent reads diary entries when answering account questions in chat. Actions you confirm in chat are logged as entries; the Agent does not write notes of its own.
The honest answers about Diary.
What gets captured?
Four sources: (1) manual notes from your team via API or UI, (2) actions taken in Lyra (a recommendation applied, reopened or closed, a change undone, an action you confirm in chat), (3) Slack messages from channels you've configured (daily 03:45 UTC sync), (4) Google Ads change-history events (budget edits, status changes, keyword, ad group and ad edits), synced daily.
Does the Lyra Agent write entries?
The Agent reads the diary for account context (so questions like "remember when we paused that ad group?" resolve to real entries). Actions you confirm in chat are logged as entries; the Agent does not write notes of its own — keeps authorship clear and avoids the risk of synthesising history.
How is attribution tracked?
Every entry has `created_by` (Lyra user or 'system') and timestamps. Slack entries also carry `source_user_name`, the Slack author.
How do I find a specific entry?
Filter by entry type, source, author (Lyra, team, system), importance level (normal / important / critical), or date range, or search title and content. Common patterns: 'all change-history events on a customer ID in the last 14 days', 'all critical entries this week'.
How does Slack capture work?
You configure one or more Slack channels per client account. The daily 03:45 UTC sync pulls recent messages; each becomes an entry with `source_user_name` set to the Slack author and the Slack timestamp used as the dedup key. Dedup means re-running the sync is idempotent — the same message never lands twice.
What's the retention?
Entries are kept while the account is active.
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