DatriseAI-first ETL

Outbrain to MongoDB Integration

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

How Datrise loads Outbrain into MongoDB

Datrise syncs Outbrain's campaigns, promoted links, publishers, spend, clicks, and conversions into MongoDB as a collection per source entity. Flexible or custom fields land in native nested documents, and timestamps such as created, updated, and status changes are typed as BSON Date.

Sync is incremental: Datrise uses upserts by stable id with updateOne(upsert) on the source primary key, so re-runs update only what changed. Optional sharding on the entity id for large collections. Mongo has no fixed schema, so Datrise keeps field types consistent across documents to avoid mixed-type query surprises.

Ideal for document-oriented apps that want CRM data in their existing Mongo store.

Endpoints

Outbrain: Native content discovery advertising.

MongoDB: Document database for flexible schemas.

How Outbrain entities map to MongoDB

Outbrain entityMongoDB objectNotes
campaignsoutbrain_campaignsid PK · custom fields → native nested documents
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 MongoDB?

Flexible values are stored as native nested documents, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MongoDB types.

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

It runs incrementally — Datrise uses upserts by stable id with updateOne(upsert) on the source primary key.

Related pipelines

Early access

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