DatriseAI-first ETL

Salesforce Marketing Cloud Yellowfin

AI-first ETL from Salesforce Marketing Cloud into Yellowfin. Governed entities, incremental sync, typed landing tables.

How Datrise loads Salesforce Marketing Cloud into Yellowfin

Datrise syncs Salesforce Marketing Cloud's records, events, and configuration objects 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

Salesforce Marketing Cloud: SaaS or API data source for analytics and warehouse sync.

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

How Salesforce Marketing Cloud entities map to Yellowfin

Salesforce Marketing Cloud entityYellowfin objectNotes
recordssalesforce_marketing_cloud_recordsid PK · custom fields → flattened columns
eventssalesforce_marketing_cloud_eventsdate/time dimensions events
configuration objectssalesforce_marketing_cloud_configuration_objectsid PK · linked to salesforce_marketing_cloud_records

FAQ

How does Datrise handle Salesforce Marketing Cloud'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 Salesforce Marketing Cloud to Yellowfin sync stay up to date?

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

Related pipelines

Early access

Connect Salesforce Marketing Cloud 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.