FullStory Cloud Mode (Actions)
Additional versions of this destination are available
This page is about the FullStory Cloud 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 FullStory.
FullStory's cloud mode Segment integration allows you to enrich FullStory data by sending user properties and events from your servers and Cloud Apps so that you 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.
FullStory's cloud mode destination requires that you also use FullStory's tagless autocapture, available through the FullStory Device Mode (Actions) web destination. However, if you want to enrich the autocapture data with custom user properties and events from other server-side sources or cloud apps, such as recurring subscription purchases, use this cloud mode destination.
The FullStory cloud mode destination sends information about your users and related events to FullStory. It uses FullStory's REST APIs.
- Identify User: Converts Segment Identify calls to FullStory Set User Properties API calls. Use this to set custom attributes which can be used to search and segment within FullStory.
- Track Custom Event: Converts Segment Track calls to FullStory custom event API calls. Use this to capture more context about your user's experience on your site or to capture user's actions in other applications to build a more complete understanding of your user's overall experience.
- Identify User V2: Converts Segment Identify calls to FullStory Create User API calls. Use this to upsert a user and their attributes which can be used to search and segment within FullStory.
- Track Custom Event V2: Converts Segment Track calls to FullStory Create Event API calls. Use this to capture more context about your user's experience on your site or to capture user's actions in other applications to build a more complete understanding of your user's overall experience.
- Enrich autocapture data with FullStory's latest data capture APIs
- Ability to send custom events from new sources
- Use Destination Filters to selectively send certain events or user properties to FullStory
- You need a FullStory API Key to use the FullStory cloud mode destination. Refer to this article to learn how to generate a new API Key within FullStory.
- From the Segment web app, click Catalog, then click Destinations.
- Find "FullStory Cloud Mode (Actions)" in the Destinations list and click it.
- Click Configure FullStory Cloud Mode (Actions).
- Select an existing Source to connect to FullStory Cloud Mode (Actions).
- Provide a Destination Name and select Fill in settings manually. Ensure the "Actions" destinations framework is selected and click Save.
- On the Basic Settings page, enter your FullStory API Key from step 1 and click Save Changes.
- On the Mappings tab, you can view default mappings as well as add, modify, or disable mappings. Confirm that the "User ID" FullStory property is mapped to the ID previously used to identify the user. For more information, please refer to the API documentation.
Info
Events that you send through to FullStory through a Cloud-mode connection count towards your FullStory server event quota. To see your company's current quota allotment, view the Subscription information on the Account Settings page in FullStory.
If you are using the original 'Identify User' and 'Track Event' actions and encounter a 404 Not Found error, the user for which the API request is being made can not be found in the identified set of users within your FullStory organization. If you expect that user to already exist, you can search for that User ID in FullStory to confirm. Also, double check that you are using an API key from the same organization.
Data sent server-side for users must match an already existing userId that was sent from a client-side connection.
The new 'Identify User V2' and 'Track Event V2' actions will automatically create users when a user matching the provided UID is not found.
GDPR deletions require an Admin or Architect API key to propagate. You may also contact FullStory directly for deletions.
Fullstory Cloud Mode (Actions) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Track Event | Event type = "track" | Track Event V2 |
| Identify User | Event type = "identify" | Identify User V2 |
Build your own Mappings. Combine supported triggers with the following Fullstory Cloud Mode-supported actions:
Mapping limits per destination
Track events
Track Event is a Cloud action. The default Trigger is type = "track"
The user's id
The name of the event.
Optional
A JSON object containing additional information about the event that will be indexed by FullStory.
Optional
The date and time when the event occurred. If not provided, the current FullStory server time will be used.
Optional
Set to true if the custom event should be attached to the user's most recent session. The most recent session must have had activity within the past 30 minutes.
Optional
If known, the FullStory session playback URL to which the event should be attached, as returned by the FS.getCurrentSessionURL() client API.
Sets user identity variables
Identify User is a Cloud action. The default Trigger is type = "identify"
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
Sets user identity variables. Creates a new FullStory user if no user matching the given uid is found.
Identify User V2 is a Cloud 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 V2.
Track Event V2 is a Cloud action. The default Trigger is type = "track"
Optional
The user's id
The name of the event.
Optional
A JSON object containing additional information about the event that will be indexed by FullStory.
Optional
The date and time when the event occurred. If not provided, the current FullStory server time will be used.
Optional
Set to true if the custom event should be attached to the user's most recent session. The most recent session must have had activity within the past 30 minutes.
Optional
If known, the FullStory session playback URL to which the event should be attached, as returned by the FS.getCurrentSessionURL() client API.