Friction investigator
The friction investigator is an AI assistant attached to each friction finding. Ask it about the people who hit the problem, and it runs real queries on your data and shows you the evidence behind every number.
Updated
What it is
A friction finding tells you what happened. The investigator helps with the next questions. Who were these people? Where did they come from? What did they do instead? Every conversation is scoped to the people who hit that finding on that page.
Ask a question
- Open a finding under Friction.
- In Ask about this, type a question or pick a suggestion, such as Which plans were these people on? or Where did they come from?
- The panel Ask about this finding opens, Scoped to the 312 people who hit this on /checkout, and the answer streams in.
- Ask follow-ups in the same panel. Each builds on the conversation so far.
What it can look at
The investigator can only read. It has a fixed set of tools:
- the finding’s own details
- your saved funnels
- your saved segments, and Overview’s page, referrer and country breakdowns
- a pre-filled experiment setup link, which it offers but never creates
It works from totals, not individuals: it never reads a single person, session or event, and personal-looking values are removed before anything reaches the model. To see one person’s journey, open them in People. It can’t change settings, create reports, or see anything outside your project. It treats the contents of your events as data, never as instructions.
Evidence and honesty
- Every answer lists Evidence this answer used: chips that open the exact events, settings or evidence, with the time window each covers.
- Every number in an answer comes from a query it ran. When the data can’t settle a question, it says so rather than guessing.
- It is careful about why. It tells you where a problem is concentrated, not what caused it.
- Every answer is labelled AI-generated — verify against the linked evidence. Open the chips before you act on an answer.
Limits
- 100 questions a month for your organization, shared with Ask and “Why did this change?”, reset at the start of each month (UTC). The panel shows how many are left.
- 20 questions per conversation. Conversations aren’t saved yet: leaving the page starts a new one.
- A very broad question may hit the per-question budget. The answer then suggests asking a narrower follow-up.
- Questions asked on Home (below) come out of the same monthly allowance.
Ask anything on Home
The same kind of assistant sits under the greeting on Home, in the Ask anything bar. It isn’t tied to one finding. Ask about the whole project, such as Why did signups drop on Tuesday?, or pick one of the suggested questions under the bar.
- It reads your analytics with the MCP server’s read-only report tools, except the one that lists individual events, and the answer lists Evidence this answer used. Small numbers in the text point to the chip each claim came from.
- When a report would answer it better, the answer offers a button such as Open insight, Open funnel or Open flow, which opens the builder filled in. Nothing is saved until you save it.
- It can also propose a board. Review board lists the tiles it would add, and only Create board makes it.
- Ask follow-ups in place, or click New question to start over. Esc clears the bar.
Ask is part of Pro, like the investigator. On other plans the bar stays visible but disabled, and says why. When 10 or fewer questions are left this month, the bar shows how many.
Good questions
Is this concentrated in one group?
- Ask: Is this concentrated in a saved segment?
- Then: Which browsers and devices were these people on?
Did it cost us conversions?
- Ask: What happened after people hit the Apply coupon button?
- Then: How did these people do in the Checkout funnel?
Show me one real example.
- The investigator doesn’t look up individuals. Open the finding’s page in Events, filtered to the element.
- Click a row’s person to read their full profile in People.