DatriseAI-first ETL

Twitter/X Ads Domo

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

How Datrise loads Twitter/X Ads into Domo

Datrise syncs Twitter/X Ads's campaign metrics, spend, engagement, and ad conversion performance into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

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

Domo: Cloud BI platform combining data integration and executive dashboards.

How Twitter/X Ads entities map to Domo

Twitter/X Ads entityDomo objectNotes
campaign metricstwitter_x_ads_campaign_metricsid PK · custom fields → flattened columns for Magic ETL
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 Domo?

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

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

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

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