DatriseAI-first ETL

Outbrain to Redash Integration

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

How Datrise loads Outbrain into Redash

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

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.

Ideal for lightweight, query-driven dashboards.

Endpoints

Outbrain: Native content discovery advertising.

Redash: Open-source SQL client for queries, visualizations, and dashboards.

How Outbrain entities map to Redash

Outbrain entityRedash objectNotes
campaignsoutbrain_campaignsid PK · custom fields → flattened columns for query results
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 Redash?

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

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

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

Related pipelines

Early access

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