Every format that matters
PDFs, plain text, manual notes, emails — and scraped URLs with weekly diffing, so a quiet landing-page rewrite never slips past unnoticed.
[04/07]Context Hub
/ the product tour
If ROAS drops, you’ll know why.
Upload your landing pages, brand briefs, dated promos, and client notes. When an anomaly lands, ROASt cross-references the drop against everything it knows — events, platform changes, creative refreshes, URL shifts — and writes a one-paragraph narrative to explain it.
[01]The store
/ everything ROASt knows
A memory for each client.
The context that explains performance lives in inboxes, Notion pages and meeting notes — everywhere except your reporting tool. Context Hub gives it one home, per client.
Indexed on upload
Documents are chunked and embedded automatically within seconds of upload, then retrieved on demand by Flume and the narrative generator. No manual tagging, no curation chores.
External Changes timeline
URL diffs, CSV imports, manual entries, per-platform creative-change dates synced automatically — the ledger of everything that happened outside ROASt that might have moved the numbers.
Why bother? Because every PPC manager has had the “why is
ROAS down?” call where the honest answer takes 45 minutes of clicking across
Google Ads, GA4, Slack and the client’s Notion — and still ends with a
hedge. ROASt compresses that to one click.
[02]Ask why
/ answers with receipts
One click from anomaly to answer.
When something moves, the explanation draws on everything in the store — and points at the exact document and date, so there’s no guessing which change caused the dip.
“Explain this” on every anomaly
One click on any anomaly → a narrative paragraph synthesising ranked causes, relevant context, and engagement signals — with hedged language when confidence is low. Pasteable straight into a client reply.
Cites your own docs
“ROAS dipped two days after the landing-page rewrite logged on the 14th” beats “performance fluctuated.” The narrative names the source it drew from, every time.
The weekly brief
Monday morning, dashboard + email: pacing, top movers, anomalies, creative and keyword opportunities, competitor watch — same causal plumbing, written for an operator triaging multiple clients.
It teaches itself. Every narrative lists the data sources it
couldn’t consult because they’re empty — “I couldn’t
check your landing page because it’s not connected, add it here” —
with a deep link straight into Context Hub. Richer context in, richer answers out.