Understand how a feature is being used
Ask Fullstory MCP how your users are engaging with any part of your product and it will pull the data, review real sessions, and give you a complete picture: usage patterns, friction points, and what's working well.
Example questions
How are people using our saved wishlist feature?
Do they actually come back and buy from it?
How is our new one-page checkout performing?
Where are people dropping off?
Which product categories have the highest cart abandonment?
How are first-time visitors behaving differently from returning customers on our homepage?
What you get back
A usage and friction report grounded in both aggregate data and session evidence. For example:
Saved Wishlist: Usage Report (last 30 days)
By the numbers:
- 3,200 users added at least one item to their wishlist
- 41% returned to their wishlist at least once
- 18% of users who returned to their wishlist completed a purchase within 7 days
How people use it:
- Most users add items during browsing sessions on mobile, then return on desktop to purchase
- The "Save for later" button in the cart is the most common entry point (62%)
- Users who add 3+ items have a significantly higher return rate than those who add 1
Friction:
- Dead clicks on the wishlist icon in the product grid; users click it
multiple times in quick succession before navigating away (affects ~8% of wishlist visitors)
- Users who don't return to their wishlist within 3 days almost never come back
What's working:
- The wishlist → checkout path is fast: users who return complete checkout
in under 2 minutes on average
- Users who add 3+ items convert at a significantly higher rate than those who add 1
Follow-up questions
Tell me more about those dead clicks on the wishlist icon.
What are users expecting to happen?
Show me sessions from users who added items but never came back.
Is there a common drop-off point?
Compare wishlist usage between mobile and desktop users.
Example follow-up
You: Show me sessions from users who added to their wishlist
but never returned. What's going wrong?
AI: Reviewed 5 sessions. Two patterns:
Pattern 1 (3 of 5 sessions): Users added items during
a browsing session, never received any re-engagement
touchpoint, and didn't return organically. No friction,
just no pull-back mechanism.
Pattern 2 (2 of 5 sessions): Users tried to find their
wishlist on a return visit. One user searched "saved items"
in the site search. Neither user navigated to the wishlist
through the standard path; both ended up on unrelated pages
before abandoning the session entirely.
The bigger opportunity here is discoverability on return
visits, not the add-to-wishlist flow itself.