DatriseAI-first ETL

Outbrain to Mode Integration

AI-first ETL from Outbrain into Mode. Governed entities, incremental sync, typed landing tables.

How Datrise loads Outbrain into Mode

Datrise syncs Outbrain's campaigns, promoted links, publishers, spend, clicks, and conversions into Mode as warehouse tables Mode queries with SQL. Flexible or custom fields land in flattened columns for SQL and notebooks, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned facts for report queries. Mode runs analyst-written SQL, so Datrise lands stable, documented tables that won't break saved reports.

Ideal for SQL-first analysis with Python and R notebooks.

Endpoints

Outbrain: Native content discovery advertising.

Mode: Collaborative analytics workspace for SQL, Python, and shared reports.

How Outbrain entities map to Mode

Outbrain entityMode objectNotes
campaignsoutbrain_campaignsid PK · custom fields → flattened columns for SQL and notebooks
promoted linksoutbrain_promoted_linksid PK · linked to outbrain_campaigns
publishersoutbrain_publishersid PK · linked to outbrain_campaigns
spendoutbrain_spendid PK · linked to outbrain_campaigns

FAQ

How does Datrise handle Outbrain's custom fields in Mode?

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

How does the Outbrain to Mode sync stay up to date?

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

Related pipelines

Early access

Connect Outbrain to Mode 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.