Fullstory analytics workflow. Use when answering a question that requires measuring user behavior — counts, rates, trends, breakdowns, or cohort comparisons. Builds segments and metrics, computes results, then investigates sessions to explain what the numbers mean.
Generate click and interaction heatmaps from session data — visualize where users click, tap, and hover on any page. Use when asking "what do users click on most", "are users clicking non-clickable elements", or "where should we place the CTA".
Structured incident response workflow — detect, investigate, communicate, and resolve using session data as evidence. Use when an incident is declared, a production issue is reported, or the on-call engineer needs session evidence.
Create detailed bug reports from session evidence — auto-populate Jira tickets with session URLs, error messages, device info, and reproduction steps. Use when the user wants to file a bug from a Fullstory session.
Build, compute, and update Fullstory Journey objects from natural language — visualize common user paths, find drop-off points, and compare journey variants. Use when asking about user flows, path analysis, journey maps, or "what paths do users take.".
Analyze the user lifecycle — new, active, at-risk, and churned users. Use when understanding user progression, identifying at-risk users, or measuring lifecycle conversion rates.
Audit existing metrics and segments for staleness, duplicates, bad configuration, and naming issues. Use when the user wants to clean up their Fullstory account, find redundant objects, or understand what already exists.
Mobile-specific UX analysis — touch interactions, viewport issues, scroll behavior, mobile vs desktop patterns, and responsive design validation. Use when investigating mobile experience, responsive design bugs, or mobile conversion rates.
Behavioral proxy for user satisfaction — use frustration signals, engagement patterns, and conversion behavior as a real-time NPS alternative. Use when the user wants to measure satisfaction but doesn't have survey data in Fullstory.
Interactive onboarding guide for new Fullstory MCP users — teaches the mental model, walks through first queries, and explains how to use each skill. Use when a new team member needs to learn how to use Fullstory through Claude.
Page-level performance analysis — load times, errors by page, device breakdown, and page-to-page navigation patterns. Use when asking about specific page health, comparing pages, or finding pages with performance issues.
Build behavioral user personas from session data — identify distinct user types by their actual behavior, not demographics. Use when the team needs data-driven personas, wants to understand who their users really are, or needs to align product decisions to real user behavior.
Proactive alerting based on trend analysis — predict when a metric will cross a threshold and alert before it happens. Use when setting up early warning systems, monitoring for regressions, or creating proactive alert rules.
Audit Fullstory session capture for PII leaks, verify privacy rules, and check recording block rules. Use when the user is concerned about privacy compliance, wants to verify masking rules, or needs to find sessions that may contain sensitive data.
Translate vague business questions into precise Fullstory queries — help users who know what they want to ask but not how to express it. Use when the user says "I want to know X but I'm not sure how to ask Fullstory.".
Lightning-fast answers to simple numeric questions — "how many users yesterday", "what's the conversion rate", "how many sessions today". Use when the question is a single number, no analysis needed. Skips the full general-analysis workflow.
Turn Fullstory research findings into a presentation-ready report — slide structure, speaker notes, and export to PPTX or PDF. Use when the user asks for a deck, slides, presentation, or report from their analytics.
User retention analysis — N-day retention, cohort stickiness, returning vs new user patterns, and churn signals. Use when asking about retention rates, user stickiness, churn analysis, or "are users coming back?".
Attach revenue estimates to UX issues and conversion problems. Use when the user wants to know what a friction point or conversion drop is costing in dollars.
Analyze how far users scroll on key pages — content visibility, where users stop reading, and whether important content is being seen. Use when evaluating page layout, content effectiveness, or CTA placement.
Interactive guided segment building for non-technical users — helps construct complex user cohorts with validation and preview. Use when a non-analyst user needs to build a segment but doesn't know how to express it in a query.
Curate playlists of Fullstory sessions for team review — bundle related sessions with notes, timestamps, and context. Use when sharing session evidence with the team, preparing for a bug review, or creating a highlight reel of user behavior.
Use when diagnosing user-reported issues, investigating bugs, analyzing user behavior, or validating UI correctness using Fullstory session recordings.
Search across sessions by user properties, device, browser, custom events, or page — find the needle in the haystack. Use when you need to find specific sessions without a pre-built metric or segment.