Branch to PlanetScale Integration
AI-first ETL from Branch into PlanetScale. Governed entities, incremental sync, typed landing tables.
How Datrise loads Branch into PlanetScale
Datrise syncs Branch's links, clicks, installs, events, attribution touchpoints, and campaigns into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.
Ideal for horizontally scalable MySQL apps on Vitess.
Endpoints
Branch: Deep linking and mobile attribution.
PlanetScale: Serverless MySQL platform with safe schema workflows.
How Branch entities map to PlanetScale
| Branch entity | PlanetScale object | Notes |
|---|---|---|
| links | branch_links | id PK · custom fields → JSON columns |
| clicks | branch_clicks | id PK · linked to branch_links |
| installs | branch_installs | id PK · linked to branch_links |
| events | branch_events | DATETIME events |
FAQ
How does Datrise handle Branch's custom fields in PlanetScale?
Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native PlanetScale types.
How does the Branch to PlanetScale sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.
Related pipelines
More destinations for Branch
More sources for PlanetScale
Early access
Connect Branch to PlanetScale 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.