Merge to Sisense Integration

How Datrise loads Merge into Sisense

Datrise syncs Merge's linked accounts, employees, candidates, contacts, invoices, and sync statuses into Sisense as modeled tables for a Sisense ElastiCube (or live connection). Flexible or custom fields land in flattened columns for the cube, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental ElastiCube builds on changed rows, so re-runs update only what changed. Date-partitioned facts to speed cube builds. ElastiCube is an in-memory model, so Datrise lands incremental, build-friendly tables rather than forcing full rebuilds.

Ideal for embedded analytics on an in-memory engine.

Endpoints

Merge: Unified API across HR, CRM, and accounting tools.

Sisense: Analytics platform with elastic data models and embedded analytics.

How Merge entities map to Sisense

Merge entity	Sisense object	Notes
linked accounts	`merge_linked_accounts`	id PK · custom fields → flattened columns for the cube
employees	`merge_employees`	id PK · linked to merge_linked_accounts
candidates	`merge_candidates`	id PK · linked to merge_linked_accounts
contacts	`merge_contacts`	id PK · linked to merge_linked_accounts

FAQ

How does Datrise handle Merge's custom fields in Sisense?

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

How does the Merge to Sisense sync stay up to date?

It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.

Related pipelines

Early access

Connect Merge to Sisense 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.