FullStory Device Mode (Actions)
Destination Info
- Accepts Page, Alias, Group, Identify and Track calls.
- Refer to it as Fullstory, or Fullstory (Actions) in the Integrations object
- This destination is not compatible with Destination Insert Functions.
- This integration is partner owned. Please reach out to the partner's support for any issues.
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.
- 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.
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.
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.
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.
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.
- 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.
Optional
Enables FullStory debug mode.
The organization ID for FullStory.
Optional
Enables FullStory inside an iframe.
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 |
Build your own Mappings. Combine supported triggers with the following Fullstory-supported actions:
Mapping limits per destination
Sets user identity variables
Identify User is a Web action. The default Trigger is type = "identify"
Optional
The user's id
Optional
The user's anonymous id
Optional
The user's display name
Optional
The user's email
Optional
The Segment traits to be forwarded to FullStory
Track events
Track Event is a Web action. The default Trigger is type = "track"
The name of the event.
Optional
A JSON object containing additional information about the event that will be indexed by FullStory.
Sets page properties events
Viewed Page is a Web action. The default Trigger is type = "page"
Optional
The name of the page that was viewed.
Optional
The properties of the page that was viewed.
Track events
Track Event V2 is a Web action. The default Trigger is type = "track"
The name of the event.
Optional
A JSON object containing additional information about the event that will be indexed by FullStory.
Sets page properties
Viewed Page V2 is a Web action. The default Trigger is type = "page"
Optional
The name of the page that was viewed.
Optional
The properties of the page that was viewed.
Sets user identity properties
Identify User V2 is a Web action. The default Trigger is type = "identify"
Optional
The user's id
Optional
The user's anonymous id
Optional
The user's display name
Optional
The user's email
Optional
The Segment traits to be forwarded to FullStory
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 |