Branch to Sisense Integration
AI-first ETL from Branch into Sisense. Governed entities, incremental sync, typed landing tables.
How Datrise loads Branch into Sisense
Datrise syncs Branch's links, clicks, installs, events, attribution touchpoints, and campaigns 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
Branch: Deep linking and mobile attribution.
Sisense: Analytics platform with elastic data models and embedded analytics.
How Branch entities map to Sisense
| Branch entity | Sisense object | Notes |
|---|---|---|
| links | branch_links | id PK · custom fields → flattened columns for the cube |
| clicks | branch_clicks | id PK · linked to branch_links |
| installs | branch_installs | id PK · linked to branch_links |
| events | branch_events | date/time fields events |
FAQ
How does Datrise handle Branch'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 Branch to Sisense sync stay up to date?
It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.
Related pipelines
More destinations for Branch
Early access
Connect Branch 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.