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.
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.
Benefits of FullStory (Actions) vs FullStory Classic
- Greater control over the page properties you send.
- Send events specific to individual pages.
- Select by name the specific to send.
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.
Destination Settings
| Setting | Description |
|---|---|
| Debug mode | Required. Enables FullStory debug mode. |
| FS Org | Required. The organization ID for FullStory. |
Available Presets
Fullstory (Actions) has the following presets:
| Preset Name | Trigger | Default Action |
|---|---|---|
| Identify User | Event type = "identify" |
Identify User |
| Track Event | Event type = "track" |
Track Event |
Available Actions
Build your own subscriptions! Combine supported triggers with the following Fullstory-supported actions:
Identify User
Sets user identity variables
Identify User is a Web action.
| Field | Description |
|---|---|
| User ID | Type: STRINGThe user’s id |
| Anonymous ID | Type: STRINGThe user’s anonymous id |
| Display Name | Type: STRINGThe user’s display name |
Type: STRINGThe user’s email |
|
| Traits | Type: OBJECTThe Segment traits to be forwarded to FullStory |
Track Event
Track events
Track Event is a Web action.
| Field | Description |
|---|---|
| Name | Type: STRINGThe name of the event. |
| Properties | Type: OBJECTA JSON object containing additional information about the event that will be indexed by FullStory. |
Viewed Page
Sets page properties events
Viewed Page is a Web action.
| Field | Description |
|---|---|
| Page Name | Type: STRINGThe name of the page that was viewed. |
| Properties | Type: OBJECTThe properties of the page that was viewed. |
Migration from the classic FullStory destination
Analytics.js 2.0
Actions-based destinations may require features found in Analytics.js 2.0. If the destination has Web actions and is connected to a javascript source, upgrade your Analytics.js source to ensure compatibility.
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: 02 Dec 2021
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!