DatriseAI-first ETL

Totango to ClickHouse Integration

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

How Datrise loads Totango into ClickHouse

Datrise syncs Totango's accounts, users, success plays, health scores, journey stages, and tasks 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

Totango: Customer journey orchestration for retention teams.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Totango entities map to ClickHouse

Totango entityClickHouse objectNotes
accountstotango_accountsid PK · custom fields → JSON or Map columns
userstotango_usersid PK · linked to totango_accounts
success playstotango_success_playsid PK · linked to totango_accounts
health scorestotango_health_scoresid PK · linked to totango_accounts

FAQ

How does Datrise handle Totango'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 Totango 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 Totango 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.