Microsoft Advertising → Yellowfin

AI-first ETL from Microsoft Advertising into Yellowfin. Governed entities, incremental sync, typed landing tables.

How Datrise loads Microsoft Advertising into Yellowfin

Datrise syncs Microsoft Advertising's campaigns, ad groups, keywords, spend, and conversion metrics into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

Microsoft Advertising: Paid search and audience ads on Microsoft properties.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How Microsoft Advertising entities map to Yellowfin

Microsoft Advertising entity	Yellowfin object	Notes
campaigns	`bing_ads_campaigns`	id PK · custom fields → flattened columns
ad groups	`bing_ads_ad_groups`	id PK · linked to bing_ads_campaigns
keywords	`bing_ads_keywords`	id PK · linked to bing_ads_campaigns
spend	`bing_ads_spend`	id PK · linked to bing_ads_campaigns

FAQ

How does Datrise handle Microsoft Advertising's custom fields in Yellowfin?

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

How does the Microsoft Advertising to Yellowfin sync stay up to date?

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

Related pipelines

Early access

Connect Microsoft Advertising to Yellowfin 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.