resolved
FullStory
fullstory.com/ui/{org-id}/dashboards
landed in 38msBookSlash for FullStory · Design
b/fullstory.
Replays, funnels, dashboards.
FullStory holds the answer to "what did the user do before they hit that error?" — but the URLs are forgettable. BookSlash flattens session-replay search, funnels, and dashboards to slugs designers and PMs type.
fullstory
other shortcuts you might save
b/fullstoryb/replaysb/funnels-fsb/segments-fs
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for FullStory, with notes on why each one survives the URL changes that break personal bookmarks.
- b/fullstory
FullStory home.
Universal entry point for session-replay work.
https://app.fullstory.com/ui/{org-id}/dashboards - b/replays
Session replay search.
PMs and designers reach it daily.
https://app.fullstory.com/ui/{org-id}/segments/everyone/sessions - b/funnels-fs
Conversion funnels.
Growth and marketing reach it weekly.
https://app.fullstory.com/ui/{org-id}/funnels - b/segments-fs
Saved segments.
Cross-team analyses live in segments.
https://app.fullstory.com/ui/{org-id}/segments - b/heatmap
Page heatmaps.
Designers and conversion analysts reach them weekly.
https://app.fullstory.com/ui/{org-id}/heatmaps
Common workflows
Three patterns that pay back in week one.
01
Bug-replay investigation
When a customer reports a bug, support and engineering reach b/replays to find the session.
02
Funnel drop investigation
Growth opens b/funnels-fs to inspect drop-off; pairs with b/replays for context.
03
Design review
Designers reach b/heatmap during weekly design reviews.
With and without
Same FullStory. Different team experience.
Without shortcuts
Each PM bookmarks FullStory separately. Cross-team handoffs include 100-character segment URLs.
With BookSlash
b/fullstory, b/replays, b/funnels-fs, b/segments-fs, b/heatmap. Five slugs cover FullStory.
Frequently asked
BookSlash + FullStory
Yes — namespace cleanly: b/fullstory-* vs b/mixpanel-*.
No — querying happens in FullStory.
b/replays (FullStory) for user sessions, b/errors (Sentry) for application errors. Together: full incident reproduction.
Some teams use both. Namespace: b/hotjar.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial