Connectors / Service / Fullstory

A user session replay tool. (updated: 1633093467428)

Fullstory

FullStory is a web-based digital intelligence system that helps optimize the client experience.

Overview

API INFO: The Base URL used for the Fullstory connector is https://api.fullstory.com/. More information can be found on their main API documentation (v1) site.

FullStory enables users to track and monitor each customer activity. From clicks to page transitions, everything is indexed automatically.

Authentication

Within the builder, click on the Fullstory connector to display the connector properties panel. Select the 'Authentication' tab and click on the 'New authentication' button.

add-new-auth

In the Tray.io authentication pop-up modal, name the authentication in a way that will easily identify it within a potentially large list. For example, whether it is a Sandbox or Production auth, etc.

Consider who/ how many people will need access to this authentication when choosing where to create this authentication ('Personal' or 'Organisational').

The second page asks you for your 'API Key'.

auth-api-key

In order to get these fields, head to the Fullstory dashboard. Click on the vertical hamburger icon on the top right corner and select 'Settings'.

Navigate to 'Integrations' > 'API Keys'.

Here you can create an API Key using the 'Create key' button.

PLEASE NOTE: Make sure to copy the API token as it will only be displayed once.

auth-create-api-key

Once you have added these fields to your Tray.io authentication pop-up window, click the 'Create authentication' button.

Your connector authentication setup should now be complete.

Available Operations

The examples below show one or two of the available connector operations in use.

Please see the Full Operations Reference at the end of this page for details on all available operations for this connector.

Notes on using Fullstory

Get user

PLEASE NOTE: The 'UserId' received in the output of the 'List Sessions from Email' operation cannot be used as an input to the 'User ID' field of the 'Get user' operation.

The Get user operation provides the data about users who have been identified in the browser. It uses 'User ID' to fetch the user details from Fullstory.

get-user-operation

User ID is a six-digit number found in the User's profile on your Fullstory dashboard.

user-profile

Example Usage

TRAY POTENTIAL: Tray.io is extremely flexible. By design there is no fixed way of working with it - you can pull whatever data you need from other services and work with it using our core and helper connectors. This demo which follows shows only one possible way of working with Tray.io and the Fullstory connector. Once you've finished working through this example please see our Introduction to working with data and jsonpaths page and Data Guide for more details.

Below is an example of a way in which you could potentially use the Fullstory connector to list session details for a given email address.

These sessions are then counted and a daily notification of the total session count is sent to Slack, to keep track of daily browser activities.

Note that you could also send this information to a Google Sheet or a SQL database.

The overall logic of the workflow is:

  1. The workflow is triggered by a scheduled trigger that runs daily.

  2. It gets the List of all the sessions based on the specified email address.

  3. Loops through the Session Dates and compares each with the Last Run Date to see if there are any new sessions.

  4. Is new Session? is a boolean step which checks if each session occurred after the last run date. If so, the Session count is incremented.

  5. Then the Total Session Count is fetched and sent as a Slack notification.

  6. Finally, the Last Run Date is set, which will be used in the next run of the workflow

The efficiency of this workflow may slightly reduce over time if after say, a year, a user has thousands of sessions to be looped through. In which case you may find it will take a minuteor so to run

Your completed workflow should look similar to this:

fullstory-complete-wf-1

Step-by-step Explanation

BEST PRACTICES: Whenever you do decide to create your own workflow, please make sure you take a look at our managing data best practices guide.

All Operations

Latest version:

1.2

List Sessions from Email

Returns a list of session URLs for a given user’s email address. These requests are scoped to user in the context of a single Fullstory account.

Delete user

Delete all user data related to a user identified in the browser. This includes sessions, events and custom user variables, as well as all of the raw page files and any corresponding session data on the Fullstory servers.

Get user

Get data about users who have been identified in the browser.