Twitter Ads to Mode Integration

How Datrise loads Twitter Ads into Mode

Datrise syncs Twitter Ads's campaigns, line items, promoted tweets, spend, impressions, and conversions into Mode as warehouse tables Mode queries with SQL. Flexible or custom fields land in flattened columns for SQL and notebooks, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned facts for report queries. Mode runs analyst-written SQL, so Datrise lands stable, documented tables that won't break saved reports.

Ideal for SQL-first analysis with Python and R notebooks.

Endpoints

Twitter Ads: Paid campaign delivery and performance on X.

Mode: Collaborative analytics workspace for SQL, Python, and shared reports.

How Twitter Ads entities map to Mode

Twitter Ads entity	Mode object	Notes
campaigns	`twitter_ads_campaigns`	id PK · custom fields → flattened columns for SQL and notebooks
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 Mode?

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

How does the Twitter Ads to Mode sync stay up to date?

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

Related pipelines

Early access

Connect Twitter Ads to Mode 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.