DatriseAI-first ETL

Urban Airship Holistics

AI-first ETL from Urban Airship into Holistics. Governed entities, incremental sync, typed landing tables.

How Datrise loads Urban Airship into Holistics

Datrise syncs Urban Airship's records, events, and configuration objects into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Urban Airship: SaaS or API data source for analytics and warehouse sync.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Urban Airship entities map to Holistics

Urban Airship entityHolistics objectNotes
recordsurban_airship_recordsid PK · custom fields → flattened columns for the modeling layer
eventsurban_airship_eventsdate/time dimensions events
configuration objectsurban_airship_configuration_objectsid PK · linked to urban_airship_records

FAQ

How does Datrise handle Urban Airship's custom fields in Holistics?

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

How does the Urban Airship to Holistics sync stay up to date?

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

Related pipelines

Early access

Connect Urban Airship to Holistics 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.