Localytics to Amazon QuickSight Integration

How Datrise loads Localytics into Amazon QuickSight

Datrise syncs Localytics's sessions, events, users, campaigns, push deliveries, and app profiles into Amazon QuickSight as warehouse tables or a SPICE-loaded dataset. Flexible or custom fields land in flattened columns for analyses, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental refresh of the tables behind SPICE or direct query, so re-runs update only what changed. Date-partitioned facts to bound SPICE refresh. QuickSight SPICE is an in-memory copy, so Datrise keeps the backing tables incremental so refreshes stay cheap.

Ideal for AWS-native dashboards with pay-per-session pricing.

Endpoints

Localytics: Mobile app analytics and push engagement.

Amazon QuickSight: AWS serverless BI with SPICE and embedded analytics.

How Localytics entities map to Amazon QuickSight

Localytics entity	Amazon QuickSight object	Notes
sessions	`localytics_sessions`	id PK · custom fields → flattened columns for analyses
events	`localytics_events`	date/time fields 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 Amazon QuickSight?

Flexible values are stored as flattened columns for analyses, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Amazon QuickSight types.

How does the Localytics to Amazon QuickSight sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the tables behind SPICE or direct query.

Related pipelines

Early access

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