FullStory Collect Slice


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.

Steps to add this slice to your installation

The steps to launch your slice are:

  1. Generate FullStory API key
  2. Specify the slice config
  3. Add the FullStory slice

1. Generate FullStory API key

Setup requirements

Before getting started please make sure to have the following information:

  • Access to an active FullStory account

Setup instructions

  1. Sign into your FullStory account.
  2. Click the user menu (three dots, upper right corner) > Settings.
  3. Click Integrations & API Keys in the menu on the left side of the page.
  4. Click API Key
  5. Your API token will display on the page. Copy the API token.

2. Specify the slice config

To get a template for the FullStory slice configuration save the output of the describe --input-parameters command as follows:

datacoral collect describe --slice-type fullstory \
--input-parameters > fullstory_parameters_file.json

Necessary input parameters:

  • api_key - your FullStory API token

    Example templates:

"api_key": "test",

3. Add the Slice

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>]
  • slice-name Name of your slice. A schema with your slice-name is automatically created in your warehouse
  • params-file File path to your input parameters file. Ex. fullstory_parameters_file.json

Supported load units

  • events
  • lists


events: This is the only load unit in the slice that has data of all events.

Slice output

Output of this slice is stored in S3 and Redshift.

AWS S3 Data stored in AWS S3 is partitioned by date and time in the following bucket s3://datacoral-data-bucket/<sliceName>

AWS Redshift: Schema - schema name will be same as a slice-name. Tables produced by the slice are:

- schema.events
- schema.lists


What is Data Export pack?

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.

Questions? Interested?

If you have questions or feedback, feel free to reach out at hello@datacoral.co or Request a demo