DatriseAI-first ETL

Twitter/X Ads Birst

AI-first ETL from Twitter/X Ads into Birst. Governed entities, incremental sync, typed landing tables.

How Datrise loads Twitter/X Ads into Birst

Datrise syncs Twitter/X Ads's campaign metrics, spend, engagement, and ad conversion performance into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.

Ideal for networked, governed enterprise BI.

Endpoints

Twitter/X Ads: Ad performance source for X campaign analytics.

Birst: Cloud BI with networked analytics and enterprise semantic layers.

How Twitter/X Ads entities map to Birst

Twitter/X Ads entityBirst objectNotes
campaign metricstwitter_x_ads_campaign_metricsid PK · custom fields → flattened columns
spendtwitter_x_ads_spendid PK · linked to twitter_x_ads_campaign_metrics
engagementtwitter_x_ads_engagementid PK · linked to twitter_x_ads_campaign_metrics
ad conversion performancetwitter_x_ads_ad_conversion_performanceid PK · linked to twitter_x_ads_campaign_metrics

FAQ

How does Datrise handle Twitter/X Ads's custom fields in Birst?

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

How does the Twitter/X Ads to Birst sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.

Related pipelines

Early access

Connect Twitter/X Ads to Birst 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.