The assistant

The assistant is the conversational layer over your analytics: ask questions in plain language and it answers from your real event data by writing and running queries instead of guessing.

What it can do

• Answer questions: ask “How many unique users did we have yesterday?” and it inspects your live event schema, writes the SQL, runs it, and answers with the result.
• Build dashboards: described in Dashboards & reports; every widget query is verified against real data before anything is saved.
• Write reports: frozen, shareable analyses with the executed queries attached as an audit trail.
• Learn your vocabulary: tell it “remember that wl_join means a waitlist signup” and it writes that into your project’s data dictionary for every future conversation.

Grounding: the honesty guarantees

Assistants that invent numbers are worse than useless, so the platform enforces Narrato’s guardrails mechanically instead of relying on instructions to the model:

• Scoped by construction. Every query the assistant runs is bounded to your projects server-side, with the same enforcement as the query API. It cannot read another account’s data no matter what it’s asked.
• No queries, no report. Saving a report is refused unless queries actually ran in that conversation turn. Reports carry those queries as a receipt.
• Verified widgets. Dashboard widgets execute before they persist; queries that fail don’t ship.
• Visible work. In chat, the activity log shows each schema inspection and query as it happens, so you can inspect the reasoning.

Context: teach it your product

The Context page is a per-project data dictionary: a product description, per- event meanings (with per-property notes and a deprecated flag), and free-form guidance. The assistant reads it on every question, so a few minutes of annotation noticeably improves answer quality. Your answers during first-run onboarding are saved into it automatically.

Limits

Free-plan workspaces get a daily assistant message allowance (Limits & billing); Pro allows 500 a day.

Conversation history

Every chat conversation is saved to your workspace. The conversation sidebar on the chat page lists your recent conversations, and you can resume or delete any of them. History follows your account, not your browser, so a conversation started on one machine picks up on another. Durable product knowledge still belongs in Context, not chat history: the assistant reads Context on every question, but it only remembers a past conversation when you resume it.