DatriseAI-first ETL

Localytics to ThoughtSpot Integration

AI-first ETL from Localytics into ThoughtSpot. Governed entities, incremental sync, typed landing tables.

How Datrise loads Localytics into ThoughtSpot

Datrise syncs Localytics's sessions, events, users, campaigns, push deliveries, and app profiles into ThoughtSpot as warehouse tables ThoughtSpot indexes for search. Flexible or custom fields land in flattened columns for searchable fields, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the indexed tables, so re-runs update only what changed. Date-partitioned facts for live-query performance. ThoughtSpot search relies on clear names and relationships, so Datrise lands well-named, joinable tables.

Ideal for natural-language search analytics over a warehouse.

Endpoints

Localytics: Mobile app analytics and push engagement.

ThoughtSpot: Search-driven analytics with AI-assisted insights on warehouse data.

How Localytics entities map to ThoughtSpot

Localytics entityThoughtSpot objectNotes
sessionslocalytics_sessionsid PK · custom fields → flattened columns for searchable fields
eventslocalytics_eventsdate/time columns events
userslocalytics_usersid PK · linked to localytics_sessions
campaignslocalytics_campaignsid PK · linked to localytics_sessions

FAQ

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

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

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

It runs incrementally — Datrise uses incremental refresh of the indexed tables.

Related pipelines

Early access

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