FullStory Device Mode (Actions)
Additional versions of this destination are available
This page is about the FullStory Device Mode (Actions). See below for information about other versions of the FullStory destination:
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.
FullStory’s device mode Segment integration auto-captures high-fidelity user sessions and allows you to enrich FullStory data by sending user properties, page properties, and custom events from your website so you can apply it to your analysis throughout FullStory. For example, you could build a funnel to analyze drop-off of users who engaged with a certain marketing campaign.
Benefits of FullStory Device Mode (Actions) vs FullStory Classic
- Greater control over the page properties you send.
- Send events specific to individual pages.
- Select by name the specific user properties or custom events to send.
Overview
The FullStory device mode destination sends information about your users, pages, and related events to FullStory. It uses the FullStory Browser API. The recommended presets, ending in “V2”, use the most up-to-date version of the FullStory Browser API. The corresponding non-versioned presets use the legacy FullStory Browser API.
Identify user V2
If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like the following:
analytics.identify('userId123');
When you use an Identify call, Segment calls FullStory’s Set Identity API. Use this to identify a user and set custom attributes which can then be used to search and segment within FullStory.
If an Identify call contains a userId
, it will be applied to the identifying uid
in FullStory. All traits
will be passed along as custom user properties with the exception of traits.name
which is mapped to displayName
. If you set an anonymousId
in Segment, you can search for it under segmentAnonymousId
in FullStory.
Track custom event V2
If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like the following:
analytics.track('Clicked Button');
When you use a Track call, Segment calls FullStory’s Track Event API. Use this to capture more context about your user’s experience on your site.
Viewed Page V2
If you’re not familiar with the Segment Specs, take a look to understand what the Page method does. An example call would look like the following:
analytics.page('Retail Page');
When you use a Page call, Segment calls FullStory’s Set Page Properties API. Use this to set custom page names and properties about pages your users visit. Either category
or name
with be mapped to FullStory’s pageName
property.
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 Device Mode (Actions), then click Configure FullStory Device Mode (Actions).
- Select an existing Source to connect to FullStory Device Mode (Actions).
- Click Customized Setup to start from a blank mapping.
Destination Settings
Setting | Description |
---|---|
Debug mode | Enables FullStory debug mode. |
FS Org | Required. The organization ID for FullStory. |
Capture only this iFrame | Enables FullStory inside an iframe. |
Available Presets
Fullstory (Actions) has the following presets:
Preset Name | Trigger | Default Action |
---|---|---|
Identify User | Event type = "identify" |
Identify User V2 |
Track Event | Event type = "track" |
Track Event V2 |
Viewed Page | Event type = "page" |
Viewed Page V2 |
Available Actions
Build your own Mappings. Combine supported triggers with the following Fullstory-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Identify User
Sets user identity variables
Identify User is a Web action. The default Trigger is: type = "identify"
Field | Description |
---|---|
User ID | Type: STRING The user’s id |
Anonymous ID | Type: STRING The user’s anonymous id |
Display Name | Type: STRING The user’s display name |
Type: STRING The user’s email |
|
Traits | Type: OBJECT The Segment traits to be forwarded to FullStory |
Track Event
Track events
Track Event is a Web action. The default Trigger is: type = "track"
Field | Description |
---|---|
Name* | Type: STRING The name of the event. |
Properties | Type: OBJECT A 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. The default Trigger is: type = "page"
Field | Description |
---|---|
Page Name | Type: STRING The name of the page that was viewed. |
Properties | Type: OBJECT The properties of the page that was viewed. |
Track Event V2
Track events
Track Event V2 is a Web action. The default Trigger is: type = "track"
Field | Description |
---|---|
Name* | Type: STRING The name of the event. |
Properties | Type: OBJECT A JSON object containing additional information about the event that will be indexed by FullStory. |
Viewed Page V2
Sets page properties
Viewed Page V2 is a Web action. The default Trigger is: type = "page"
Field | Description |
---|---|
Page Name | Type: STRING The name of the page that was viewed. |
Properties | Type: OBJECT The properties of the page that was viewed. |
Identify User V2
Sets user identity properties
Identify User V2 is a Web action. The default Trigger is: type = "identify"
Field | Description |
---|---|
User ID | Type: STRING The user’s id |
Anonymous ID | Type: STRING The user’s anonymous id |
Display Name | Type: STRING The user’s display name |
Type: STRING The user’s email |
|
Traits | Type: OBJECT The Segment traits to be forwarded to FullStory |
Migration from the classic FullStory destination
Follow the table below to map your existing FullStory destination configuration to FullStory Device Mode (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: 04 Mar 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!