Snapchat Ads to DuckDB Integration

How Datrise loads Snapchat Ads into DuckDB

Datrise syncs Snapchat Ads's campaigns, ad squads, ads, creatives, spend, and conversion metrics into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.

Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.

Ideal for local and notebook analytics without standing up a server.

Endpoints

Snapchat Ads: Paid campaigns across Snapchat placements.

DuckDB: In-process analytics database for fast local OLAP.

How Snapchat Ads entities map to DuckDB

Snapchat Ads entity	DuckDB object	Notes
campaigns	`snapchat_ads_campaigns`	id PK · custom fields → JSON or STRUCT columns
ad squads	`snapchat_ads_ad_squads`	id PK · linked to snapchat_ads_campaigns
ads	`snapchat_ads_ads`	id PK · linked to snapchat_ads_campaigns
creatives	`snapchat_ads_creatives`	id PK · linked to snapchat_ads_campaigns

FAQ

How does Datrise handle Snapchat Ads's custom fields in DuckDB?

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

How does the Snapchat Ads to DuckDB sync stay up to date?

It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.

Related pipelines

Early access

Connect Snapchat Ads to DuckDB 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.