You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

FullStory Destination

Destination Info

Accepts Identify calls.
Refer to it as FullStory in the Integrations object

Components

Browser

Connection Modes

Device-mode	Cloud-mode
✅ Web	❌ Web
❌ Mobile	❌ Mobile
❌ Server	❌ Server

(information)

Additional versions of this destination are available

This page is about the FullStory Destination. See below for information about other versions of the FullStory destination:

(warning)

Warning

This destination is currently under maintenance. Please check back later or contact support.

FullStory lets product and support teams easily understand everything about the customer experience. The Segment integration for FullStory helps accurately identify your customers within the FullStory dashboard.

Getting Started

From the Segment web app, click Catalog.
Search for "FullStory" in the Catalog, select it, and choose which of your sources to connect the destination to. Note the source must be sending events using our JavaScript library Analytics.js.
Add your FS Org in the destination settings. You can find this in FullStory by navigating to Settings > General > and copying the value found on the line window['_fs_org'] = 'fullstory_org_here';

Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading FullStory's recording snippet on your page and sending data.

Identify

If you're not familiar with the Segment Specs, take a look to understand what the identify method does. Identify calls sent to Segment will be transformed and sent to FullStory's FS.identify method.

An example call which does not include a userId will send FullStory the value of the anonymousId and would look like:

analytics.identify();

If an identify call does contain a userId, that will be the ID sent along to FullStory.

analytics.identify("userId");

In addition, Segment will send over along any traits included in the identify call. The example call below would send over both plan and logins.

1analytics.identify("userId123", {
2  plan: "premium",
3  logins: 5
4});

Specifying display name and email

Both email and displayName are special traits that will be passed to FullStory to be used in their interface as explained in FullStory's docs. These traits are optional.

1analytics.identify("userId123", {
2  email: "john.doe@example.com",
3  displayName: "John Doe"
4});

Track

If you're not familiar with the Segment Specs, take a look to understand what the track method does. Track calls sent to Segment will be automatically passed directly to FullStory using FullStory's FS.event method, including all the properties passed in the event.

An example call would look like:

1analytics.track('Product Purchased', {
2    order_ID: '2969302398',
3    category: 'boots',
4    product_name: 'yellow_cowboy_boots',
5    price: 99.95,
6    currency: 'EUR'
7});

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

Property nameTypeRequiredDescription

Enter FS debug modeboolean

Optional

This will enable FullStory's debug mode

Default: false

Capture only this iFrameboolean

Optional

This will enable FullStory within an iframe.

Default: false

FS Orgstring

required

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']

Track All Pagesboolean

Optional

Sends all page calls as tracking events to FullStory.

Default: false

Track Categorized Pagesboolean

Optional

Sends pages that specify a category to Fullstory as tracking events.

Default: false

Track Named Pagesboolean

Optional

Sends pages with names to FullStory as tracking events.

Default: false