FullStory Destination

Segment makes it easy to send your data to FullStory (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to FullStory in the format they understand. Learn more about how to use FullStory with Segment.

Getting Started

When you toggle on FullStory in Segment, we’ll start sending data to the FullStory API for your account. Currently, FullStory will send data from our analytics.js library.

To start pushing user data to FullStory, toggle the destination on and add your FS Org. This key can be found in the recording snippet in your FullStory settings.


The first thing you’ll want to do is to identify a user with any relevant information as soon as they log-in, or sign-up. You record this with our identify method.

Identify takes the userId of a user and any traits you know about them.

When you call identify, we’ll call FullStory’s FS.identify method with the userId if supplied, or the anonymousId if not. We also send any traits that you provide, such as gender, or age.

Both email and displayName are special traits that will be passed to Fullstory as they expect to be used in their interface as explained in Fullstory’s docs.

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Enter FS debug mode

This will enable FullStory’s debug mode

FS Org

You can find your _fs_org on the FullStory settings page by logging into your account, clicking the settings icon on the bottom left, and looking in the recording snippet for window[‘_fs_org’]

If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!