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
- From the Segment web app, click Catalog, then click Destinations.
- Find the Destinations Actions item in the left navigation, and click it.
- Select FullStory (Actions), then click Configure FullStory (Actions).
- Select an existing Source to connect to FullStory (Actions).
- Click Customized Setup to start from a blank mapping.
Connection Settings
| 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.
| Field | Description |
|---|---|
| User ID | Default userIdThe user’s ID in FullStory. |
| Anonymous ID | Default anonymousIdThe user’s anonymousId in FullStory. |
| Display Name | Default traits.nameThe user’s display name. |
Default traits.emailThe user’s email address. |
|
| Traits | Default traitsThe Segment traits forwarded to FullStory. |
Track Event
Send event details to FullStory.
| Field | Description |
|---|---|
| Name | Default nameThe name of the event |
| Properties | Default propertiesA 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.
| Field | Description |
|---|---|
| Page Name | Default nameThe name of the viewed page. Defaults to |
| Properties | Default propertiesThe 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 |
|
| Track Categorized Pages Device-web |
||
| Track Named Pages Device-web |
||
This page was last modified: 21 Sep 2021
Need support?
Questions? Problems? Need more info? Contact us, and we can help!