Twitter Ads to Neon Integration

How Datrise loads Twitter Ads into Neon

Datrise syncs Twitter Ads's campaigns, line items, promoted tweets, spend, impressions, and conversions 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 Ads: Paid campaign delivery and performance on X.

Neon: Serverless Postgres destination with branching and autoscaling.

How Twitter Ads entities map to Neon

Twitter Ads entity	Neon object	Notes
campaigns	`twitter_ads_campaigns`	id PK · custom fields → jsonb 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 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 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 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.