Urban Airship to Azure Synapse Integration

How Datrise loads Urban Airship into Azure Synapse

Datrise syncs Urban Airship's push notifications, channels, audiences, message events, segments, and named users into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

Urban Airship: Mobile push and cross-channel message orchestration.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Urban Airship entities map to Azure Synapse

Urban Airship entity	Azure Synapse object	Notes
push notifications	`urban_airship_push_notifications`	id PK · custom fields → NVARCHAR(MAX) JSON columns
channels	`urban_airship_channels`	id PK · linked to urban_airship_push_notifications
audiences	`urban_airship_audiences`	id PK · linked to urban_airship_push_notifications
message events	`urban_airship_message_events`	datetime2 events

FAQ

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

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the Urban Airship to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

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