FullStory is an app that captures all customer experience data in one powerful, easy-to-use platform. This datasource slice retrieves Data Export extracts and writes it to S3 and Redshift.
events: This is the only load unit in the slice that has data of all events. This load unit has the following columns -
|exportid||This is the bundle id of Data Export pack|
|eventstart||The time when the event first occurred, in UTC.|
|eventtype||The type of event that was recorded. Typical types are: |
|eventtargettext||Where applicable, this contains the text of the event target and its child elements.|
|eventtargetselectortok||Where applicable, this contains the CSS selector for the event target.|
|eventmoddead||Your customer clicked something, but nothing happened. Will be 1 for dead clicks, zero for non-dead clicks.|
|eventmoderror||Your customer clicked something and a console error was generated, either by an actual error occurring, or by logging an error to the console. Will be 1 for error clicks, zero for non-error clicks.|
|eventmodsuspicious||Your customer entered text or navigated to a URL that was suspicious. When set to zero, nothing was suspicious. When 1, it indicates a possible SQL injection attack. When 2, it indicates a possible cross site scripting attack.|
|indvid||A unique identifier for the Individual that combines all Users with the same User App Key. The IndvdId value is not visible within the FullStory UI, but it is part of the session URL.|
|pageurl||The full URL of the page on which the given event occurred.|
|pageduration||The total time this User spent on this page during this session (milliseconds).|
|pageactiveduration||The active time (mouse movement, text entry, clicks, etc.) this User spent on this page during this session (milliseconds).|
|pagerefererurl||The page from which the user reached this page.|
|pagelatlong||The latitude/longitude corresponding to this session.|
|pageagent||The full user agent string for the system on which this session was recorded.|
|pageip||The IP address captured at the start of the session.|
|pagebrowser||The browser that was used for this session, as derived from the User Agent. Current possible values: Chrome, Firefox, Internet Explorer, Microsoft Edge, Safari, Opera, Mobile App, Yandex, Robot, Unknown.|
|pagedevice||The device type that was used for this session, as derived from the User Agent. Current possible values: Desktop, Mobile, Tablet, Robot, Unknown.|
|pageoperatingsystem||The operating system type that was used for this session, as derived from the User Agent. Current possible values: Chrome OS, OS X, iOS, Windows, Windows Phone, Linux, Robot, Unknown.|
|pagenumwarnings||The number of times console.warn() was called on the page.|
|sessionid||The identifier for a particular session, within the context of a single user.|
|pageid||The identifier for a particular page, within the context of a single session.|
|userappkey||The user identifier that was passed to FullStory from your system using FS.identify.|
|useremail||The email address that was set via FS.identify or FS.setUserVars.|
|userdisplayname||The display name that was set via FS.identify or FS.setUserVars.|
|userid||A unique identifier for a user cookie on a given device/browser.|
|loaddomcontenttime||DOMContentLoaded fires when the initial HTML document has been loaded and parsed.|
|loadfirstpainttime||The First Meaningful Paint event relates to the moment when the biggest "above-the-fold" layout change has happened and when web fonts have loaded.|
|loadeventtime||The onload event or "Page Load" fires when the whole page and all of its dependent resources have finished loading.|
|customvars||Custom user variable fields amalgamated into a single JSON document|
Obtain API Token from Fullstory as below -
Sign into your FullStory account.
Click the user menu (three dots, upper right corner) > Settings.
Click Integrations & API Keys in the menu on the left side of the page.
Click API Key
Your API token will display on the page. Copy the API token.
To get the input params required to deploy Fullstory slice, run the describe command below and save the output of the command to a file.
datacoral collect describe --slice-type fullstory \ --input-parameters > <params-file>
Add the token in the above params file and add the slice using the following command
datacoral collect add --slice-type fullstory --slice-name <slice-name> \ [--parameters-file <params-file>]
Schema - <sliceName>
Table - <Load Unit Name>
The Data Export Pack provides a periodic, raw data extract of events that have been recorded for your organization and an API endpoint to retrieve the data extracts.
How often are the data export files updated?
The data is provided in the form of bundles. By default, a bundle contains data about events that occurred during a period of 24 hours. This period can be changed to anywhere between 30 minutes to 24 hours. This bundle will be available to download 24 hours after the last event in this bundle occurred. For example, if your bundle period was set to 6 hours, a data export bundle corresponding to events that happened on Jul 11 between 12:00 PM - 6:00 PM will be available to download on Jul 12 at 6:00 PM.
Preferred option would be to set this to hourly so that data does not become too large.
How far back in time can I export data?
Data export availability matches the session retention length that you currently subscribe to. This means that if your account is configured for 2 months of session retention, you will be able to export data for sessions that are up to two months old. It is important to note that once sessions expire and are deleted, they are truly not recoverable.
Note: the timestamps in the slice are in UTC. However, directly searching through the FullStory app uses your local time. Please keep this in mind if you see differing results.