Localytics to MySQL Integration

How Datrise loads Localytics into MySQL

Datrise syncs Localytics's sessions, events, users, campaigns, push deliveries, and app profiles into MySQL 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/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Localytics: Mobile app analytics and push engagement.

MySQL: Widely used OSS relational engine (InnoDB).

How Localytics entities map to MySQL

Localytics entity	MySQL object	Notes
sessions	`localytics_sessions`	id PK · custom fields → JSON columns
events	`localytics_events`	DATETIME/TIMESTAMP events
users	`localytics_users`	id PK · linked to localytics_sessions
campaigns	`localytics_campaigns`	id PK · linked to localytics_sessions

FAQ

How does Datrise handle Localytics's custom fields in MySQL?

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 MySQL types.

How does the Localytics to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Localytics to MySQL 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.