Mailshake to Sisense Integration

How Datrise loads Mailshake into Sisense

Datrise syncs Mailshake's campaigns, recipients, sequences, email events, replies, and leads 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

Mailshake: Cold outreach sequences and reply tracking.

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

How Mailshake entities map to Sisense

Mailshake entity	Sisense object	Notes
campaigns	`mailshake_campaigns`	id PK · custom fields → flattened columns for the cube
recipients	`mailshake_recipients`	id PK · linked to mailshake_campaigns
sequences	`mailshake_sequences`	id PK · linked to mailshake_campaigns
email events	`mailshake_email_events`	date/time fields events

FAQ

How does Datrise handle Mailshake'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 Mailshake to Sisense sync stay up to date?

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

Related pipelines

Early access

Connect Mailshake 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.