Skip to main content

Understand why users are behaving a certain way

When you see something unexpected in your data — a spike in drop-offs, a frustration signal you can't explain, a behavior pattern that doesn't make sense — ask Fullstory MCP to investigate. It will read real sessions and tell you what's actually happening.

Example questions

Why are users dropping off between our pricing page and the signup form?
Fullstory MCP
Why is there a spike in dropouts on the shipping step this week?
Fullstory MCP
Are users searching for our return policy before leaving checkout?
Fullstory MCP
Mobile conversion dropped after our most recent release. Find sessions that show what's happening.
Fullstory MCP

What you get back

A behavioral investigation. The MCP pulls sessions, reads what users did, and explains the pattern in plain language. For example:

AI Response

Shipping step abandonment (last 14 days)

Reviewed 6 sessions where users abandoned at the shipping step.

What they did

  • Average time on the shipping step: 30 seconds (vs. 8-second median for completers)
  • 5 of 6 users scrolled to the bottom of the page before leaving
  • 4 of 6 users hovered over the "Shipping policy" link without clicking it

What they were looking for

  • 3 sessions: users opened a new tab and navigated to /shipping-policy via Google search
  • 2 sessions: users typed "return" or "refund" in the on-page search field
  • 1 session: user sat for 22 seconds, then closed the tab without taking any other action

Why they're stuck

The shipping cost is shown but the delivery window and return policy are not visible on this step. Users want to confirm both before entering their address. The 40% drop-off rate at this step is information-seeking behavior, not a technical failure.

Suggested fix: surface delivery window and return policy inline on the shipping step, not behind a separate page.

Follow-up questions

Show me what one of those sessions actually looked like. Open it and walk me through what the user saw.
Fullstory MCP
Is the dropout rate different on mobile vs. desktop?
Fullstory MCP
Of users who left to read the shipping policy, how many came back and completed?
Fullstory MCP

Example follow-up

Fullstory MCP
Show me what one of those sessions actually looked like. Open it and walk me through what the user saw.
Fullstory MCP
AI Response

Opened session 3 (2m 18s). Walking through the key moments:

00:12 — User arrives at the shipping step. The page shows two options: Standard (5–7 days, $4.99) and Express (2 days, $12.99). No return policy or delivery window is visible.

00:31 — User scrolls slowly past the address form and shipping options to the page footer.

00:47 — User hovers over the "Shipping policy" link in the footer for 3 seconds without clicking. Scrolls back up.

01:04 — User opens a new browser tab and navigates away from the site.

01:52 — User returns to the original tab. The form is still in its initial state.

02:18 — User closes the tab without selecting a shipping option.

The pause-and-hover at the footer is the tell. The user was looking for delivery and return information at the decision point and couldn't find it without navigating away.

Behind the scenes

The MCP routes the chain above through: get_sessions, get_session_events, session_open, session_view, and build_segment.