FullStory (Actions)

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.

This document is about a feature which is in beta. This means that the Destination Actions are in active development, and some functionality may change before it becomes generally available

Good to know: This page is about the Actions-framework FullStory Segment destination. There’s also a page about the non-Actions FullStory destination. Both of these destinations receives data from Segment.

Getting started

  1. From the Segment web app, click Catalog, then click Destinations.
  2. Find the Destinations Actions item in the left navigation, and click it.
  3. Select FullStory (Actions), then click Configure FullStory (Actions).
  4. Select an existing Source to connect to FullStory (Actions).
  5. Click Customized Setup to start from a blank mapping.

Connection Settings

Click to expand fields

Setting Description
Debug mode

Enables FullStory debug mode

FS Org (required)

The organization ID for FullStory

Pre-built subscriptions

By default a new FullStory (Actions) destination comes with the following subscriptions.

You can select these subscriptions by choosing “Quick Setup” when you first configure the destination. You can enable, edit, and disable them from the screen that appears.

Subscription Name Trigger FullStory Action
Identify User All identify calls from the connected source Identify User
Track Event All track calls from the connected source Track Event
Track Page Events All page calls from the connected source Track Event

Available FullStory actions

Combine the supported triggers with the following FullStory-supported actions:

Identify User

Set user identity variables.

Click to expand fields

Field Description
User ID Default userId

The user’s ID in FullStory.

Anonymous ID Default anonymousId

The user’s anonymousId in FullStory.

Display Name Default traits.name

The user’s display name.

Email Default traits.email

The user’s email address.

Traits Default traits

The Segment traits forwarded to FullStory.

Track Event

Send event details to FullStory.

Click to expand fields

Field Description
Name Default name

The name of the event

Properties Default properties

A JSON object that contains additional information about the event, and is indexed by FullStory.

Viewed Page

Set the properties of a page event, and send them to FullStory.

Click to expand fields

Field Description
Page Name Default name

The name of the viewed page. Defaults to category. If category is not present, name is used.

Properties Default properties

The properties of the viewed page.

Migration from the classic FullStory destination

Follow the table below to map your existing FullStory destination configuration to FullStory (Actions).

Fullstory settings mapping

fullstory Classic Destination Setting How to enable in fullstory (Actions)
Connection Settings
FS Org
Device-web

Set during initial configuration, or on the Settings tab after you create the destination.

Other Settings
Enter FS debug mode
Device-web

Available on the Settings tab of the destination.

Track All Pages
Device-web

Available as a subscription where the trigger Event Type is Page triggers the Viewed Page action.

Track Categorized Pages
Device-web
Track Named Pages
Device-web

This page was last modified: 14 Oct 2021



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account