DatriseAI-first ETL

FullStory ClickHouse

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

How Datrise loads FullStory into ClickHouse

Datrise syncs FullStory's sessions, events, funnels, frustration signals, and user properties into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

FullStory: Digital experience analytics with session replay context.

ClickHouse: Columnar OLAP engine for fast aggregations.

How FullStory entities map to ClickHouse

FullStory entityClickHouse objectNotes
sessionsfullstory_sessionsid PK · custom fields → JSON or Map columns
eventsfullstory_eventsDateTime64 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 ClickHouse?

Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.

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

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

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