# FullStory (v1)
Information note **FullStory is supported by the Singer community**
This integration is powered by [Singer's](https://www.singer.io/) FullStory tap. For support, [visit the GitHub repo](https://github.com/singer-io/tap-fullstory) or [join the Singer Slack](https://singer-slackin.herokuapp.com/).
## FullStory integration summary
Stitch’s FullStory integration relies on the Data Export pack add-on to replicate data through the [FullStory Data Export REST API](https://help.fullstory.com/develop-rest/data-export-api). Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/fullstory#schema) section for a list of objects available for replication.
## FullStory feature snapshot
A high-level look at Stitch's FullStory (v1) integration, including release status, useful links, and the features supported in Stitch.
| **STITCH** | | | |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on June 27, 2018 | **Supported by**
the Info icon
Indicates if the integration is supported by Stitch or the Singer community. | [Singer Community](https://www.singer.io/) |
| **Stitch plan**
the Info icon
The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**
the Info icon
Indicates if the integration is available as a source in Stitch Connect. | the Success icon
This version of the integration is available via the API.
Available |
| **Singer GitHub repository** | [singer-io/tap-fullstory](https://github.com/singer-io/tap-fullstory) | | |
| **REPLICATION SETTINGS** | | | |
| **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**
the Info icon
A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon
This feature is supported for this version of the integration.
Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**
the Info icon
A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Success icon
This feature is supported for this version of the integration.
Supported |
| **Table-level reset**
the Info icon
Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Remove icon
Table-level resets are not supported for this integration. Resets are only supported at the integration level.
Unsupported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**
the Info icon
Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon
Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.
Unsupported |
| **DATA SELECTION** | | | |
| **Table selection**
the Info icon
The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Remove icon
Table selection is not supported for this integration. All available table and fields will be automatically selected for replication.
Unsupported | **Column selection**
the Info icon
The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Remove icon
Column selection is not supported for this integration. All available columns in tables set to replicate will be selected.
Unsupported |
| **Select all**
the Info icon
Indicates if the integration supports selecting all available tables and columns. | the Remove icon
As this integration doesn't support table or column selection, all available tables and columns are automatically replicated.
Unsupported | | |
| **TRANSPARENCY** | | | |
| **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**
the Info icon
Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Success icon
This feature is supported for this version of the integration.
Supported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**
the Info icon
Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon
This feature is supported for this version of the integration.
Supported |
## 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](https://help.fullstory.com/technical-questions/data-export) 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 FullStoryRetrieve 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](https://app.stitchdata.com/).
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 replication start date
The Sync Historical Data setting defines 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](https://help.qlik.com/en-US/stitch/replication/syncing-historical-saas-data-resetting-replication-keys) guide.
### Step 4: Create a replication schedule
Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.
In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
FullStory integrations support the following replication scheduling methods:
* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)
* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)
* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) 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.**
Information note
**Initial replication jobs with Anchor Scheduling**
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.
#### 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.
Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.
## 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.
### Loading data using Append-Only loading
When Stitch loads the extracted data for FullStory events into your destination, it will do so using Append-Only loading. This is a type of loading behavior where existing rows aren’t updated, but appended to the end of the table. **Note**: Loading will be append-only even if the destination you’re using supports Upsert loading.
Refer to the [Understanding loading behavior guide](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-behavior) for more info and examples.
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 `https://example.com/my-account`.
2. Next, the user clicks in the `Street address` text field on the page at `https://example.com/update-address`.
3. The user changes (`EventType: change`) the text in the `Street address` field to `1339 Chestnut Street` on the page at `https://example.com/update-address`.
4. Lastly, the user clicks the `Save Changes` button on the page at `https://example.com/update-address`.
## FullStory table reference
Information note
**Schemas and versioning**
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for **version 1** of this integration.
This is the latest version of the FullStory integration.
Information note
**Table and column names in your destination**
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (`CusTomERs` > `customers`), while case is maintained in PostgreSQL destinations (`CusTomERs` > `CusTomERs`). Refer to the [Loading Guide](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info.
### events
The `events` table contains raw data about the events that occurred on your site, which are recorded using the FullStory JavaScript library.
**Note**: Records for this table are loaded using [Append-Only loading](https://help.qlik.com/en-US/stitch/integrations/saas/fullstory#data-loading-append-only). Loading will be append-only even if the destination you’re using supports Upsert loading.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | \_\_sdc\_primary\_key |
| **Replication Key ** | EventStart |
| **Useful links** | [FullStory documentation](https://help.fullstory.com/technical-questions/data-export#data-export-contents "Opens in new tab: FullStory documentation")
[events schema on GitHub](https://github.com/singer-io/tap-fullstory/blob/master/tap_fullstory/schemas/events.json "Opens in new tab: events schema on GitHub") |
events table schema
| **EventStart**
DATE-TIME |
| --- |
| **EventTargetSelectorTok**
STRING |
| **EventTargetText**
STRING |
| **EventType**
STRING |
| **IndvId**
INTEGER |
| **PageActiveDuration**
INTEGER |
| **PageAgent**
STRING |
| **PageBrowser**
STRING |
| **PageDevice**
STRING |
| **PageDuration**
INTEGER |
| **PageId**
INTEGER |
| **PageIp**
STRING |
| **PageLatLong**
STRING |
| **PageNumErrors**
INTEGER |
| **PageNumInfos**
INTEGER |
| **PageNumWarnings**
INTEGER |
| **PageOperatingSystem**
STRING |
| **PageRefererUrl**
STRING |
| **PageUrl**
STRING |
| **SessionId**
INTEGER |
| **UserAppKey**
STRING |
| **UserDisplayName**
STRING |
| **UserEmail**
STRING |
| **UserId**
INTEGER |