DatriseAI-first ETL

FullStory Azure Synapse

AI-first ETL from FullStory into Azure Synapse. Governed entities, incremental sync, typed landing tables.

How Datrise loads FullStory into Azure Synapse

Datrise syncs FullStory's sessions, events, funnels, frustration signals, and user properties into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

FullStory: Digital experience analytics with session replay context.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How FullStory entities map to Azure Synapse

FullStory entityAzure Synapse objectNotes
sessionsfullstory_sessionsid PK · custom fields → NVARCHAR(MAX) JSON columns
eventsfullstory_eventsdatetime2 events
funnelsfullstory_funnelsid PK · linked to fullstory_sessions
frustration signalsfullstory_frustration_signalsid PK · linked to fullstory_sessions

FAQ

How does Datrise handle FullStory's custom fields in Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the FullStory to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect FullStory to Azure Synapse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.