DatriseAI-first ETL

Twitter/X Ads Neon

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

How Datrise loads Twitter/X Ads into Neon

Datrise syncs Twitter/X Ads's campaign metrics, spend, engagement, and ad conversion performance into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

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

Neon: Serverless Postgres destination with branching and autoscaling.

How Twitter/X Ads entities map to Neon

Twitter/X Ads entityNeon objectNotes
campaign metricstwitter_x_ads_campaign_metricsid PK · custom fields → jsonb 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 Neon?

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

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

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

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