Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 20 additions & 11 deletions docs/root-cause-analysis.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ sidebarTitle: "Root Cause Analysis"

Investigating anomalies or trends in your data is extremely manual. Teams spend hours each week running the same repetitive process (picking properties, running breakdowns, eyeballing segments) to figure out what drove a change in a metric.

Mixpanel's **AI-Powered Root Cause Analysis (RCA)** feature does that work for you. Launch RCA from any Insights report or fired alert and an AI agent automatically diagnoses what changed: it validates the anomaly, runs the relevant breakdowns, ranks the dimensions that contributed most, and writes up an interpretation with a confidence level and suggested next steps — all delivered as a Board you and your team can keep working from.
Mixpanel's **AI-Powered Root Cause Analysis (RCA)** feature does that work for you. Launch RCA from any Insights report, a fired alert, or the Mixpanel Agent and an AI agent automatically diagnoses what changed: it validates the anomaly, runs the relevant breakdowns, ranks the dimensions that contributed most, and writes up an interpretation with a confidence level and suggested next steps — all delivered as a Board you and your team can keep working from.

## How it works

Expand All @@ -27,16 +27,21 @@ Cards stream into the Board as each step completes, with a live progress banner
## Where to launch RCA

<Steps>
<Step title="From an Insights report">
Open any Insights chart, hover over a data point that looks unexpected, and choose **Root Cause Analysis** from the popover. RCA launches scoped to that event, segment, and time window.

<Frame>
![Image](/images/image-6.png)
</Frame>
</Step>
<Step title="From a fired alert">
When an alert fires, the notification (Slack, email, or webhook) includes a link that runs Root Cause Analysis and generates a Board for that alert. See [Alerts](/docs/features/alerts#root-cause-analysis) for how RCA fits into alerting.
</Step>

<Step title="From an Insights report">

Open any Insights chart, hover over a data point that looks unexpected, and choose **Root Cause Analysis** from the popover. RCA launches scoped to that event and time window, and picks up any breakdown or segment already applied to the report so it analyzes the same slice you're looking at.
Comment thread
greptile-apps[bot] marked this conversation as resolved.
</Step>

<Step title="From a fired alert">

When an alert fires, the notification (Slack, email, or webhook) includes a link that runs Root Cause Analysis and generates a Board for that alert. See [Alerts](/docs/features/alerts#root-cause-analysis) for how RCA fits into alerting.
</Step>

<Step title="From the Mixpanel Agent">

Ask the [Mixpanel Agent](/docs/mixpanel-agent) to investigate a change (for example, _"explain this spike in signups"_) and it can kick off Root Cause Analysis for you. The analysis runs right in your Agent chat and produces the same RCA Board you can open and keep working from.
Comment thread
greptile-apps[bot] marked this conversation as resolved.
</Step>
</Steps>

## The RCA Board
Expand All @@ -48,6 +53,10 @@ Because RCA generates a standard Mixpanel Board, it inherits all the capabilitie
- **Cards include contribution factor analysis.** Each ranked dimension lands as its own card with the breakdown, contribution percentage, and supporting context. You can edit this as needed before sharing.
- **The interpretation card summarizes findings.** The AI's written explanation, confidence level, and suggested next steps live at the top of the Board so anyone scanning the results gets the punchline first.

<Note>
RCA only surfaces data the person running it already has permission to see. It won't expose personal information (PII) that wouldn't otherwise be visible to that user.
</Note>
Comment thread
greptile-apps[bot] marked this conversation as resolved.

## Custom RCA Settings

Oftentimes, customers know which properties matter for their business and want to direct the root cause analysis to focus there first.
Expand Down