Source connector

FullStory connector

FullStory integration for databases, warehouses and BI tools

Digital experience analytics with session replay context. Datrise captures FullStory entities such as sessions, events, funnels, frustration signals, and user properties, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The FullStory Server API v1 (Segment Export API) authenticates with API key, incremental runs key on time_range / segment_time_range window end, and FullStory caps calls at Segment Export API: burst limit of 50 calls that replenishes at 2 requests per minute; the deprecated Event Export endpoint is separately capped at 2 downloads/minute.

Of the 5 objects, 3 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `fullstory_sessions`) with a schema derived from the FullStory API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the FullStory pipeline page, and join the waitlist to get the FullStory connector (Product analytics) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What FullStory data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
sessions	fullstory_sessions	Append-only, incremental by timestamp
events	fullstory_events	Append-only, incremental by timestamp
funnels	fullstory_funnels	Upsert by primary key, incremental on updated-at
frustration signals	fullstory_frustration_signals	Upsert by primary key, incremental on updated-at
user properties	fullstory_user_properties	Upsert by primary key, incremental on updated-at

FullStory API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	FullStory Server API v1 (Segment Export API)
Authentication	API key — Requests send an API key as `Authorization: Basic {API_KEY}`; Segment Export specifically requires an Admin- or Architect-scoped key, a Normal key is rejected.
Pagination	token — Exports are asynchronous: you create a segment export job, poll its operation ID via the Operations API until it finishes, then download the resulting file.
Rate limit	Segment Export API: burst limit of 50 calls that replenishes at 2 requests per minute; the deprecated Event Export endpoint is separately capped at 2 downloads/minute
Incremental cursor	time_range / segment_time_range window end — There is no per-record last-modified field; incremental pulls are done by advancing the `time_range` (or `segment_time_range` for bulk 'everyone' segment exports) window on each run.
Webhooks	Yes — Webhook Endpoints (Anywhere Streams, paid add-on)
Bulk export	Yes — Segment Export API run over the built-in 'everyone' segment
Deletes detectable	No — no tombstone or delete flag appears in any export; GDPR erasure via `DELETE /v2/users?uid=` removes the user's sessions and events outright

Official API reference

What bites when replicating FullStory

Segment Export API allows a burst of 50 calls that then only replenish at 2 requests per minute, so aggressive operation-status polling exhausts the budget on a single job.
Segment Export requires an Admin or Architect API key; the same 'Normal' key that works for `FS.identify()` event ingestion returns a permission error here.
The older `GET /v1/exports` Event Export endpoint is deprecated in favor of Segment Export and is separately rate limited to 2 downloads/minute.
GDPR erasure via `DELETE /v2/users?uid={uid}` deletes a user's sessions, events, and raw page files outright with no tombstone, so a connector that only re-runs segment exports never observes the removal.

Compare this against every other documented API

Popular destinations for FullStory

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

FullStory connector FAQ

What FullStory data does the connector extract?: 5 objects: sessions, events, funnels, frustration signals and user properties. Each lands in its own table with types preserved; history-style objects (2: sessions and events) load as append-only streams.
Is the FullStory integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load FullStory data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each FullStory → destination pair has its own page with the object-to-table mapping.

Related Product analytics sources

Other sources in the same category, each with its own connector page.

Early access

Launch your FullStory pipeline with guided onboarding

Join the waitlist to get priority access for FullStory integrations with guided setup, schema-aware mapping, and production-grade incremental sync.