Memory
Memory is a chronological record of what changed in your marketing stack and what your team decided to do about it.
Open it from Data → Timeline in the sidebar — the page appears as Timeline in the app. (A separate Labs experiment, also called Memory, stores persistent context for the AI Agent; that is not what this page describes.)
Entry Types
Memory combines four types of entries in one unified view:
Auto-detected Changes
Vendo can log changes from connected ad platforms when change-history support is enabled:
| Platform | What’s tracked |
|---|---|
| Google Ads | Budget changes, bid strategy updates, campaign pauses, creative swaps |
| Meta Ads | Budget shifts, audience changes, placement updates, ad status changes |
| TikTok Ads | Campaign and ad group modifications |
| Snap Ads | Budget and targeting changes |
| Microsoft Ads | Campaign structure and bid updates |
These entries appear alongside manual context so teams can connect performance shifts to the changes that may have caused them.
Decisions
Log what your team decided and why. Decision entries include:
- Title — what was decided (“Shift 15% of Meta budget to TikTok”)
- Statement — full context and reasoning
- Owner — who owns the call
- Status — draft → decided → reviewing → closed
- Alternatives considered — what other options were on the table
- Review date — when to revisit and evaluate the outcome
Decisions appear alongside the changes that prompted them, creating a complete narrative: what changed → what we decided → what happened next.
Experiments
Track every experiment across your stack in one registry:
- Title — what’s being tested (“TikTok creative test — 3 variants”)
- Hypothesis — what you expect to happen
- Status — planned → running → concluded / canceled
- Platform — where the experiment runs
- Variants — the test variations
- Success metric — what you’re measuring (CPA, ROAS, conversion rate)
- Start/end dates — experiment duration
- Results — outcome, winner, and confidence (filled when concluded)
Annotations
Simple notes mark important events:
- Product launches
- External events such as seasonality, competitor moves, or market changes
- Team notes and context
- Categories: marketing, product, external, other
Using Memory
Adding Entries
Click + Add New in the Memory header and choose:
- Decision — to log a decision
- Experiment — to log an experiment
- Annotation — to add a note
Each opens a slide-in form on the right side of the screen.
Filtering the Memory
Use the header filters to narrow the record:
- Date range — last 7, 14, 30, or 90 days
- Event type — all events, ad changes only, decisions only, experiments only, annotations only
Reading the Memory
Events are grouped by date and displayed chronologically. Each entry shows:
- Type badge — color-coded by source
- Status badge — for decisions and experiments
- Summary — what happened or what was decided
- Timestamp — relative (“2h ago”) or absolute (“Mar 20”)
Why Memory Matters
Without Memory, marketing decisions happen in Slack threads, spreadsheets, and meetings with no durable record of what was decided, why, or whether it worked. Memory creates an institutional record that answers:
- “Why did we change the budget last week?”
- “What experiments are running right now?”
- “Did the TikTok reallocation actually improve ROAS?”
- “When did Meta CPM spike, and what did we do about it?”
Memory connects what changed to what you decided to what happened next, building a feedback loop for future decisions.
Platform Details
| Setting | Value |
|---|---|
| Data source (changes) | Ad platform audit logs via pipeline when supported |
| Data source (decisions/experiments/annotations) | Supabase |
| Update frequency | Changes: on sync. Manual entries: real-time |
| Retention | Unlimited |
| Access | All team members can view and create entries |
| Permissions | Deleting entries requires settings.manage permission |