DatriseAI-first ETL

Snapchat Ads to Metabase Integration

AI-first ETL from Snapchat Ads into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Snapchat Ads into Metabase

Datrise syncs Snapchat Ads's campaigns, ad squads, ads, creatives, spend, and conversion metrics into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Snapchat Ads: Paid campaigns across Snapchat placements.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Snapchat Ads entities map to Metabase

Snapchat Ads entityMetabase objectNotes
campaignssnapchat_ads_campaignsid PK · custom fields → flattened columns for the question builder
ad squadssnapchat_ads_ad_squadsid PK · linked to snapchat_ads_campaigns
adssnapchat_ads_adsid PK · linked to snapchat_ads_campaigns
creativessnapchat_ads_creativesid PK · linked to snapchat_ads_campaigns

FAQ

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

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

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

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

Related pipelines

Early access

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