CONTACT US

Resources

Tips, tutorials, guides, and product insights from FullStory’s Digital Experience Intelligence experts

Filter by Role
Filter by Industry
Filter by Type
FullStory Engineering Blog

Private by default: The hard way, but the right way to understand mobile experiences

FullStory privacy controls for mobile app analytics now allow you to avoid collecting sensitive data and only get data you need.

Read the post
Blog Post

Celebrating API Heritage Month at FullStory

A Q&A with the founding members of the Asian Pacific Islander Connection Employee Resource Group at FullStory.

Read the post
FullStory Engineering Blog

How we tamed GitHub CODEOWNERS with bots

After trying GitHub codeowners “out of the box,” we ran into a minor issue that quickly became a huge blocker. Here's how we discovered it.

Read the post
Blog Post

6 things to look for in a session replay platform

Get a detailed look at what sets FullStory’s session replay capabilities apart, and why you shouldn’t settle for anything else.

Read the post
FullStory Engineering Blog

Is go duck-typed?

In programming languages, duck typing can be approximated as the application of the duck test to objects. Here we explore if go is duck typed.

Read the post
Blog Post

Flexible analytics, AI, and the mobile experience: A conversation with FullStory Founder Scott Voigt

In a wide-ranging conversation on CRO.CAFE podcast, Scott spoke about founding FullStory, the importance of data privacy, AI, and more.

Read the post
FullStory Engineering Blog

Why you should be using errgroup.WithContext() in your Golang server handlers

How using errgroup.WithContext() can shave a few more milliseconds off of your end user latencies.

Read the post
Blog Post

Trajectory for growth: FullStory's product principles

The 4 core values that make our product great and are essential to helping our customers to the next level.

Read the post
FullStory Engineering Blog

How to answer the what and the why using FullStory data export

Knowing what's happening in your pathing analysis can only get you so far. You need to know the why too. FullStory provides both.

Read the post