DatriseAI-first ETL

Taboola to Redash Integration

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

How Datrise loads Taboola into Redash

Datrise syncs Taboola's campaigns, campaign items, sites, 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

Taboola: Content recommendation and native advertising.

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

How Taboola entities map to Redash

Taboola entityRedash objectNotes
campaignstaboola_campaignsid PK · custom fields → flattened columns for query results
campaign itemstaboola_campaign_itemsid PK · linked to taboola_campaigns
sitestaboola_sitesid PK · linked to taboola_campaigns
spendtaboola_spendid PK · linked to taboola_campaigns

FAQ

How does Datrise handle Taboola'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 Taboola to Redash sync stay up to date?

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

Related pipelines

Early access

Connect Taboola 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.