StackAdapt to Neon Integration

How Datrise loads StackAdapt into Neon

Datrise syncs StackAdapt's campaigns, line items, creatives, 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

StackAdapt: Programmatic advertising across native and display.

Neon: Serverless Postgres destination with branching and autoscaling.

How StackAdapt entities map to Neon

StackAdapt entity	Neon object	Notes
campaigns	`stackadapt_campaigns`	id PK · custom fields → jsonb columns
line items	`stackadapt_line_items`	id PK · linked to stackadapt_campaigns
creatives	`stackadapt_creatives`	id PK · linked to stackadapt_campaigns
spend	`stackadapt_spend`	id PK · linked to stackadapt_campaigns

FAQ

How does Datrise handle StackAdapt'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 StackAdapt 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 StackAdapt 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.