DatriseAI-first ETL

FullStory Holistics

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

How Datrise loads FullStory into Holistics

Datrise syncs FullStory's sessions, events, funnels, frustration signals, and user properties into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

FullStory: Digital experience analytics with session replay context.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How FullStory entities map to Holistics

FullStory entityHolistics objectNotes
sessionsfullstory_sessionsid PK · custom fields → flattened columns for the modeling layer
eventsfullstory_eventsdate/time dimensions 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 Holistics?

Flexible values are stored as flattened columns for the modeling layer, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Holistics types.

How does the FullStory to Holistics sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the modeled tables.

Related pipelines

Early access

Connect FullStory to Holistics 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.