Release Status Released Supported By Singer community
Availability Free Status Page FullStory Status Page
Default Historical Sync 1 year Default Replication Frequency 30 minutes
Whitelisting Unsupported Destination Incompatibilities None

Connecting FullStory

FullStory Setup requirements

To set up FullStory in Stitch, you need:

  • A FullStory account with the Data Export Pack add-on. The Data Export Pack is a paid add-on for FullStory accounts that enables you to export raw event data.

    This add-on is required to replicate data using FullStory’s Data Export REST API.

Step 1: Retrieve your FullStory API key

  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:

    Retrieve your API key in FullStory

  5. Your API key will display on the page. Copy the API key before closing the page.

Step 2: Add FullStory as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the FullStory icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch FullStory” would create a schema called stitch_fullstory in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the API Key field, paste your FullStory API key.

Step 3: Define the Historical Sync

The Sync Historical Data setting will define the starting date for your FullStory integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond FullStory’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Stitch offers two methods of creating a replication schedule:

  • Replication Frequency: This method requires selecting the interval you want replication to run for the integration. Start times of replication jobs are based on the start time and duration of the previous job. Refer to the Replication Frequency documentation for more information and examples.
  • Anchor scheduling: Based on the Replication Frequency, or interval, you select, this method “anchors” the start times of this integration’s replication jobs to a time you select to create a predictable schedule. Anchor scheduling is a combination of the Anchor Time and Replication Frequency settings, which must both be defined to use this method. Additionally, note that:

    • A Replication Frequency of at least one hour is required to use anchor scheduling.
    • An initial replication job may not begin immediately after saving the integration, depending on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.

To help prevent overages, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up FullStory, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

FullStory Replication

Data updates and FullStory data export bundles

FullStory data bundles event data together based on a time period setting you define. By default, a FullStory data bundle contains data about events that occurred during a 24 hour period.

Note: FullStory makes event bundles available 24 hours the last event in the bundle occurs.

For example: If your bundle period is set to 6 hours, a data export bundle for events that occur on June 1 between 12:00PM - 6:00PM will be available the following day, June 2, at 6:00PM.

Impact on Stitch replication

Because FullStory only makes event data available a full day after events have occurred, records for the current date will only ever be available the next day. Event data that is one day old is considered “up to date” for this integration.

Data loading and Append-Only Replication

When Stitch loads the extracted data for FullStory events into your destination, it will do so using Append-Only Replication. This is a type of Incremental Replication where existing rows aren’t updated, but appended to the end of the table.

For FullStory, this means that every captured event is equal to a single row in the events table. Using this data, you can view a given user’s event history and construct a timeline of their actions.

Example: Create a user session timeline

The table below contains what sample data might look like for a user who changes their address during a session:

Using this data, we can put together the order of events for this user’s session:

  1. The user clicks (EventType: click) the Update Address button on the page at
  2. Next, the user clicks in the Street address text field on the page at
  3. The user changes (EventType: change) the text in the Street address field to 1339 Chestnut Street on the page at
  4. Lastly, the user clicks the Save Changes button on the page at

FullStory table schemas

Replication Method: Append-Only Incremental Replication Key : EventStart
Primary Key : _sdc_primary_key Documentation: Official Docs

The events table contains raw data about the events that occurred on your site, which are recorded using the FullStory JavaScript library.


Applicable only if Stitch doesn’t detect a Primary Key in the source table. Stitch will use this column to de-dupe data.


The time when the event first occurred, in UTC.


The ID for a particular page within the context of a single session.


A unique ID for a specific user session.


A unique ID for the an individual user that combines all users (UserId) with the same user app key (UserAppKey).

For example: If you’ve identified user 327 whenever they visit your site, event records for the user across devices, browsers, etc. will include this ID.


A unique ID for a user cookie given on a device/browser. This ID may be reset if the user clears their cookies, switches devices, changes browsers, etc.


The CSS selector for the target event, if applicable. This will be a fully-qualified descendant selector, starting from the HTML element and including all CSS selectors of elements that appear in the DOM when walking from the HTML element, through its children, to the event target.

Note: FullStory will encode most non-alphanumeric characters within a selector. For example: .my%2Dclass rather than .my-class


The text of the event target and its child elements, if applicable.

For example: If the user clicked a button that said Pay now, the value of this field would be Pay now.

FullStory may truncate long text.


The type of event that was recorded. Possible values are:

  • abandon - A form was abandoned.
  • change - The text in a text entry field was changed. EventTargetText will contain the new text value.
  • click - An element on the page has been clicked. EventTargetText will contain text of the clicked element, if applicable.
  • navigate - A URL change, either to a completely new page or a new hash fragment.
  • thrash - The user moved the mouse cursor erratically or in circles.

The active time (mouse movement, text entry, clicks, etc.) a user spent on the page (pageId) during the session, in milliseconds. This is not a running total; even event for a given page will show the same duration.


The full user agent string for the system on which the session was recorded.


The browser used for the session. Current possible values are:

  • Chrome
  • Firefox
  • Internet Explorer
  • Microsoft Edge
  • Safari
  • Opera
  • Mobile App
  • Yandex
  • Robot
  • Unknown

The device type used for the session, as derived from the user agent (PageAgent). Current possible values:

  • Desktop
  • Mobile
  • Tablet
  • Robot
  • Unknown

The total time the user spent on the page (pageId) during the session, in milliseconds. This is not a running total; even event for a given page will show the same duration.


The IP address captured at the start of the session.


The latitutde/longitude corresponding to the session.


The number of times the JavaScript function console.log() was called, plus the number of times was called on the page during the session.

This is a running total for the page, and will steadily increase until the user navigates to a new page.


The number of times the JavaScript function console.warn() was called on the page during the session.

This is a running total for the page.


The number of times the JavaScript function console.error() was called on the page, plus the number of JavaScript errors that occurred on the page during the session.

This is a running total for the page.


The operating system used for the session, as derived from the user agent (PageAgent). Current possible values:

  • Chrome OS
  • OS X
  • iOS
  • Windows
  • Windows Phone
  • Linux
  • Robot
  • Unknown

The full URL of the page on which the given event occurred.


The URL of the page from which the user reached this page. This field may be empty if the user manually entered the page URL, the referrer has been scrubbed, etc.


The user ID passed to FullStory from your system using FS.identify.


The display name for the user, set via FS.identify or FS.setUserVars.


The email address for the user, set via FS.identify or FS.setUserVars.

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.