You do not create a single Marketing Cloud Intelligence record. You stand up the platform by connecting sources, harmonizing the data, and publishing dashboards. This is the high-level path an admin or analyst follows; the exact screens depend on your edition and which successor product you are on.
- Connect your data sources
Use an API Connector for sources with a native integration, TotalConnect for file-based feeds that need mapping, or LiteConnect for lighter uploads. Each connection becomes one or more typed data streams.
- Harmonize the incoming fields
In the Harmonization Center, set naming conventions and classification rules so each source's spend, clicks, conversions, and revenue map to the same dimensions and measurements.
- Choose an attribution model
Decide between first-touch, last-touch, linear, time-decay, or position-based before building ROI views, since the model shapes every budget conversation downstream.
- Build a curated set of dashboards
Assemble widgets into dashboard pages and collections, starting from the template library. Keep one focused view per audience rather than a sprawling gallery.
Pulls data directly from a source platform on a schedule; best for sources with a native integration.
The marketer-built method for file-based feeds; automates ingestion, cleansing, and mapping for CSVs and reports with no native connector.
The no-code area where naming conventions, classification, and field mapping align every feed to the shared data model.
The rule that distributes conversion credit across touchpoints; pick first-touch, last-touch, linear, time-decay, or position-based.
- Harmonization, not dashboard authoring, is the slow part of a rollout. Budget time for the data plumbing.
- Datorama and Marketing Cloud Intelligence name the same product; older docs and labels may still say Datorama.
- The platform is licensed separately from other Marketing Cloud products, and cost scales with connectors, data volume, and users.
- Salesforce now offers Marketing Intelligence in Marketing Cloud Next; confirm which product your org is provisioning before you design.