DatriseAI-first ETL

Microsoft Advertising Sisense

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

How Datrise loads Microsoft Advertising into Sisense

Datrise syncs Microsoft Advertising's campaigns, ad groups, keywords, spend, and conversion metrics into Sisense as modeled tables for a Sisense ElastiCube (or live connection). Flexible or custom fields land in flattened columns for the cube, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental ElastiCube builds on changed rows, so re-runs update only what changed. Date-partitioned facts to speed cube builds. ElastiCube is an in-memory model, so Datrise lands incremental, build-friendly tables rather than forcing full rebuilds.

Ideal for embedded analytics on an in-memory engine.

Endpoints

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

Sisense: Analytics platform with elastic data models and embedded analytics.

How Microsoft Advertising entities map to Sisense

Microsoft Advertising entitySisense objectNotes
campaignsbing_ads_campaignsid PK · custom fields → flattened columns for the cube
ad groupsbing_ads_ad_groupsid PK · linked to bing_ads_campaigns
keywordsbing_ads_keywordsid PK · linked to bing_ads_campaigns
spendbing_ads_spendid PK · linked to bing_ads_campaigns

FAQ

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

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

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

It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.

Related pipelines

Early access

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