Localytics → PlanetScale
AI-first ETL from Localytics into PlanetScale. Governed entities, incremental sync, typed landing tables.
How Datrise loads Localytics into PlanetScale
Datrise syncs Localytics's records, events, and configuration objects 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
Localytics: SaaS or API data source for analytics and warehouse sync.
PlanetScale: Serverless MySQL platform with safe schema workflows.
How Localytics entities map to PlanetScale
| Localytics entity | PlanetScale object | Notes |
|---|---|---|
| records | localytics_records | id PK · custom fields → JSON columns |
| events | localytics_events | DATETIME events |
| configuration objects | localytics_configuration_objects | id PK · linked to localytics_records |
FAQ
How does Datrise handle Localytics'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 Localytics 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 Localytics
Early access
Connect Localytics 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.