Twitter Ads to Azure Synapse Integration

How Datrise loads Twitter Ads into Azure Synapse

Datrise syncs Twitter Ads's campaigns, line items, promoted tweets, spend, impressions, and conversions 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

Twitter Ads: Paid campaign delivery and performance on X.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Twitter Ads entities map to Azure Synapse

Twitter Ads entity	Azure Synapse object	Notes
campaigns	`twitter_ads_campaigns`	id PK · custom fields → NVARCHAR(MAX) JSON columns
line items	`twitter_ads_line_items`	id PK · linked to twitter_ads_campaigns
promoted tweets	`twitter_ads_promoted_tweets`	id PK · linked to twitter_ads_campaigns
spend	`twitter_ads_spend`	id PK · linked to twitter_ads_campaigns

FAQ

How does Datrise handle Twitter Ads'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 Twitter Ads 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 Twitter Ads 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.