If you're using FullStory to track user behavior, you're probably sitting on a goldmine of insights. But if those insights never leave your browser tab, they're not helping your team. This guide is for people who want to get real value out of FullStory—not just watch session replays, but actually share findings with product, engineering, design, or support. I'll walk you through how to export and share what matters, skip what's not worth the trouble, and avoid common headaches.
1. Know What’s Actually Worth Sharing
Before you even think about exporting, get clear on what your teammates care about. Not everyone needs to see a 40-minute rage-click session. Ask yourself:
- Who’s this for? (Design, engineering, support, leadership?)
- What’s the point? (Is it a bug, a usability issue, a conversion drop-off?)
- Do they want raw data, highlights, or just the “aha” moment?
Pro tip: Don’t dump everything on Slack. People tune out fast. Curate.
2. Use Notes and Shares Inside FullStory First
FullStory makes it easy to add notes and share sessions directly, so you might not need to export anything at all. This saves time and keeps the context intact.
How to do it:
- While watching a session, add a note (look for the sticky-note icon).
- Tag teammates with
@usernameto send them a notification. - Use the “Share” button to copy a link to the session or segment. Paste it into Slack, Jira, or email.
What works:
This is fast, and the person you share with can see exactly what you saw—no need to explain context.
What doesn’t:
If your teammates don’t have access to FullStory, this hits a wall. Or if they’re too busy to watch a replay, you’ll need to pull out the key moments some other way.
3. Exporting Sessions: The Good, the Bad, and the Ugly
Sometimes you need to get data out of FullStory—maybe for legal, compliance, or just because someone doesn’t want “one more login.” Here’s how you can do it:
Exporting Session URLs
- Go to a session or list of sessions (like a segment).
- Click the “Share” or “Copy URL” button.
- Paste wherever your team communicates.
Reality check:
They’ll still need the right permissions to view. Session links are only as useful as your team’s willingness to click and watch.
Downloading Session Videos
- Open the session.
- Look for the “Download” option (not always available—depends on your plan and privacy settings).
- Save as MP4 and upload to your team’s preferred tool.
What to watch out for: - Downloading is slow and clunky, especially for long sessions. - Session videos lose interactivity—no event details, no click tracking, just a video.
When to use:
For one-off “look at this bug” moments, or when you need to show something to someone outside your org (like a vendor).
Exporting Event Data
If you need raw data for analysis:
- Use FullStory’s Data Export (available on some plans—Enterprise only as of this writing).
- Export to CSV, connect to BigQuery, or use their API.
Heads up:
- This is overkill unless you need to do deep analysis.
- The CSVs are dense and not easy for most people to read.
- Most teams don’t need this unless they’re building dashboards or running custom queries.
4. Create Highlight Reels Instead of Sharing Everything
People won’t watch a dozen 30-minute session replays. If you want your insights to stick, create a “highlight reel”:
- Use FullStory’s “Favorite” or “Add to Playlist” features to collect key moments.
- Add short notes to each session: what’s the problem, where in the video to watch, and why it matters.
- Share the playlist link or export a summary.
Why this works:
You’re doing the curation for your team, so they don’t waste time.
What to skip:
Don’t try to automate this—AI-generated highlight reels are usually not as good as what a human picks out.
5. Turn Insights into Actionable Summaries
If you want a decision made or a bug fixed, don’t just share a session—write a plain-English summary with links to the evidence.
How to write a good summary:
- What happened? (“Users can’t find the Save button on mobile.”)
- Where is it? (“Checkout page, iOS Safari, steps 3-4.”)
- How often? (Reference a segment or number of sessions, not just one.)
- Why does it matter? (Tie to customer complaints, drop-offs, or support tickets.)
- Include links to session(s) for proof.
Templates work:
Drop the summary into Jira, Asana, Slack, or Notion. Paste session links for those who want more detail.
Don’t:
- Copy-paste the same note everywhere.
- Send every session to everyone.
- Assume people will “just know” why it matters.
6. Use Integrations, But Don’t Rely on Magic
FullStory offers integrations with Jira, Slack, Zendesk, and more. They’re useful, but not perfect.
What works:
- Create Jira tickets with a FullStory link, so engineers can see the problem in context.
- Send alerts to a Slack channel when a segment triggers (like “users encountering error X”).
- Attach sessions to Zendesk tickets so support can show evidence.
What doesn’t:
- Integrations won’t magically make people care. If your Slack channel is noisy, your insights will get lost.
- Jira tickets with just a link and no summary will get ignored.
Keep it human:
Use integrations to reduce manual work, but always add a line or two explaining why it matters.
7. Respect Privacy and Permissions
Not every session should be widely shared. FullStory can capture sensitive data, and privacy rules matter.
- Always check if the session contains PII (personally identifiable information).
- Don’t download or share sessions outside your company without checking legal/compliance rules.
- Use FullStory’s privacy tools (like masking sensitive fields) before exporting or sharing.
Pro tip:
If in doubt, ask your privacy officer or legal team. Better safe than sorry.
8. Common Pitfalls (and How to Dodge Them)
- Oversharing: Flooding channels with too many sessions = people stop paying attention.
- No context: Sharing a session with zero explanation is a waste. Always add a note.
- Exporting for the sake of it: Don’t export unless someone actually needs the file.
- Chasing every “interesting” session: Focus on patterns, not one-offs.
9. Keep Your Workflow Simple and Repeatable
If you find yourself spending hours every week exporting and sharing, step back. The goal is to make insights actionable, not to become the “FullStory admin” for your company.
- Set up a routine: Weekly highlights, monthly digests, or “only when something major happens.”
- Automate what makes sense, but don’t trust bots to do the thinking.
- Ask your team what’s actually helpful. Adjust as you go.
Bottom line:
Sharing FullStory insights isn’t about flooding your team with data. It’s about picking the right moments, adding context, and making it easy for others to act. Start simple, get feedback, and don’t overcomplicate it. The best insights are the ones people actually use.