Marketing Cloud Intelligence is the analytics, reporting, and marketing measurement product that originated as Datorama, was acquired by Salesforce in 2018, was integrated into the Marketing Cloud as the cross-channel analytics layer, and now operates under the Marketing Cloud Intelligence name in the broader Marketing Cloud portfolio. The product solves the cross-source marketing data consolidation problem: ingesting paid media data from advertising platforms, owned channel data from Marketing Cloud Engagement and other ESPs, web analytics data from the analytics stack, and conversion data from the CRM and commerce systems into a unified analytics environment. The Intelligence commercial structure is connector- and data-row-driven, with the buyer’s data source breadth and processing volume as the principal cost dimensions. This article walks through Marketing Cloud Intelligence pricing in 2026, the connector economics, the data row tiers, the seat structure, and the negotiation moves that produce sustainable Intelligence economics.
The product positioning and the deployment patterns
Marketing Cloud Intelligence occupies a specific position in the marketing analytics stack: it is purpose-built for the cross-channel marketing data consolidation use case rather than for general-purpose business intelligence. The product’s value proposition centers on the pre-built connectors to marketing data sources, the marketing-domain data model that normalizes cross-source metrics, and the marketing-oriented reporting templates. The deployment that uses Intelligence for these purposes typically realizes the value the platform promises. The deployment that uses Intelligence as a general-purpose BI tool typically discovers that the platform’s strengths do not align with the broader BI use case and that the Intelligence economics are unfavorable compared to dedicated BI alternatives.
The typical Intelligence deployment patterns include the marketing performance dashboards (cross-channel media spend and ROI), the campaign reporting (audience engagement, conversion attribution, journey performance), the executive marketing reporting (CMO-level scorecards), and the marketing operations reporting (budget pacing, brand performance, channel mix). The deployment scope determines the connector requirements, the data volume, the seat count, and ultimately the Intelligence commitment size.
The connector economics
The connector inventory is the foundational dimension of Marketing Cloud Intelligence pricing. Each data source connection is a connector instance, with the connector library covering hundreds of marketing data sources (Google Ads, Meta, LinkedIn, X/Twitter, TikTok, programmatic DSPs, email service providers, web analytics platforms, CRM systems, commerce platforms, attribution tools). The connector pricing structure includes the connector inventory tier (the number of distinct connector instances the deployment can operate), with additional connector instances available at incremental cost.
| Connector tier | Approx. annual list | Typical deployment |
|---|---|---|
| Starter (up to 25 connectors) | $60K–$100K | Single brand, focused channel mix |
| Professional (up to 100 connectors) | $120K–$220K | Multi-brand or multi-region |
| Enterprise (200+ connectors) | $250K–$500K | Large agency or global enterprise |
| Custom enterprise tier | $500K+ | Holding company or media network |
The connector counting deserves attention. A single advertising platform may produce multiple connector instances when the deployment operates multiple advertiser accounts within that platform; a single ESP may produce multiple connector instances when the deployment operates multiple business units within that ESP. The disciplined buyer maps the connector count requirements precisely against the deployment’s actual data source architecture, with the count reflecting the distinct account-level instances rather than the distinct platform types.
The data row consumption
The data row consumption is the second consumption dimension that drives the Intelligence economics. A data row is a record processed by the Intelligence platform from any connector source, with the daily ingestion across all connectors aggregating into the licensed data row tier. The data row counts can grow substantially based on the data granularity (campaign-level daily versus keyword-level hourly versus impression-level real-time), the connector breadth, and the historical depth.
The data row forecasting is difficult for the same reasons as the event volume forecasting for Personalization: the actual production volume often exceeds the pre-commitment estimate, particularly when the deployment expands the data granularity or adds connectors during the contract term. The overage pricing for data row consumption can be meaningful and is one of the regular sources of mid-term cost surprise on Intelligence commitments. The disciplined buyer either runs a baseline period before the commitment or negotiates explicit overage protection.
The seat structure
The seat structure for Marketing Cloud Intelligence is typically tiered by user role: viewer seats for consumption-only access, analyst seats for self-service report building, and administrator seats for the data model and configuration management. The seat pricing scales with the seat count and the seat type mix, with the analyst and administrator seats carrying meaningful per-seat pricing premiums over the viewer tier.
The seat right-sizing discipline often produces meaningful savings on the Intelligence commitment. The typical deployment over-provisions the analyst and administrator seats based on initial implementation needs and continues to license those seats through the contract term even after the seat utilization declines. The renewal-cycle review of the seat utilization typically reveals 30 to 50 percent of the analyst and administrator seats that could be reduced to viewer seats or eliminated entirely without affecting the deployment value.
The Marketing Cloud Intelligence connector counting often diverges from the buyer’s mental model. A single “Meta advertising” data source may produce a dozen connector instances when the deployment operates a dozen advertiser accounts across the brand portfolio. The connector tier sizing should reflect the account-instance count rather than the platform-type count, with the data architecture documented before the commitment.
— SalesforceNegotiations advisory noteThe implementation cost dimension
Marketing Cloud Intelligence implementation cost varies meaningfully with the deployment scope and the data complexity. A focused implementation that delivers cross-channel marketing dashboards for a single brand with standard connectors typically lands in the 150K to 300K range. A complex enterprise implementation that integrates dozens of connectors across multiple brands with custom data models and bespoke reporting can exceed 500K in implementation effort.
The implementation effort allocates across the connector configuration (the technical setup and the data normalization), the data model design (the harmonization rules, the dimension definitions, the metric calculations), the dashboard and report development, the data governance framework, and the training and adoption support. The deployment that under-resources any of these streams typically produces a platform that under-delivers against the analytics business case, which is the worst commercial outcome.
The competitive landscape
Marketing Cloud Intelligence competes against several categories of alternatives: dedicated marketing analytics platforms, general-purpose BI tools (Tableau, Looker, Power BI) augmented with marketing data connectors, custom-built data warehouse and BI stacks, and the analytics capabilities embedded in adjacent marketing platforms. The competitive frame matters in the negotiation because the alternatives establish a credible benchmark that disciplines the Intelligence pricing.
The Tableau alternative deserves specific attention given Tableau’s position in the Salesforce portfolio. Tableau can address many of the cross-channel marketing reporting use cases at a different commercial structure, particularly for deployments where the marketing data is already harmonized in a customer data warehouse. The deployment that has a mature warehouse and analytics stack may find that the Tableau-on-warehouse pattern delivers the marketing reporting at lower cost than the Intelligence-on-Datorama pattern, with the trade-off being the loss of the pre-built marketing connectors and the marketing-specific data model.
The Data Cloud relationship
Marketing Cloud Intelligence operates alongside Data Cloud in the Salesforce data architecture, with potential overlap in the data ingestion and harmonization layers. The Salesforce go-to-market increasingly positions Data Cloud as the foundational data layer that other products activate against, including the analytics products. The deployment that commits to both Data Cloud and Intelligence should evaluate the architectural relationship explicitly and avoid the duplicated data infrastructure cost.
The architectural question turns on whether the marketing data should flow directly into Intelligence through its native connectors (the traditional Datorama pattern) or whether it should flow first into Data Cloud and from there into Intelligence (the emerging Data Cloud-centric pattern). The two patterns produce different commercial structures and different implementation patterns, and the choice should reflect the broader data architecture rather than the product-specific deployment expediency.
The negotiation moves
The Marketing Cloud Intelligence negotiation moves cluster around five levers. The connector tier should be sized for the actual account-instance count after the data architecture mapping rather than for the aspirational connector breadth. The data row commitment should reflect a baseline measurement or include explicit overage protection. The seat structure should match the actual user role mix, with the analyst and administrator seats licensed at the demonstrated need rather than at the aspirational user base.
The commercial structure should preserve the flexibility to add or reduce connectors across the contract term as the deployment’s data architecture evolves. The implementation support, particularly for the complex multi-connector data model work, should be included at the level required for the deployment’s complexity. The renewal protections should include the price hold across the connector tier, the data row tier, and the seat counts.
The renewal-cycle review
The Intelligence renewal-cycle review should measure the active connector count against the licensed tier, the data row consumption against the committed volume, the seat utilization across the viewer, analyst, and administrator tiers, the dashboard and report usage, and the realized analytics outcomes from the deployment investment. The review drives the next-term commitment with the precision the multi-dimensional pricing requires.
The renewal pattern for Intelligence typically reveals both unused connector capacity (connectors licensed but not actively flowing data) and unused seat capacity (seats licensed but not actively logging in). The right-sizing at renewal across both dimensions can produce 25 to 40 percent reduction in the Intelligence cost for deployments that have not actively managed the consumption profile through the contract term. The buyer who applies the review consistently captures the savings; the buyer who renews on the existing commitment typically carries the overcommitment forward.
Final word
Marketing Cloud Intelligence in 2026 remains a strategically valuable capability for organizations with cross-channel marketing data complexity and the need for a unified marketing analytics layer. The platform’s commercial structure rewards disciplined planning at the connector, data row, seat, and integration dimensions. The deployment that commits with rigorous architecture mapping, explicit scope definition, and structural protections operates the platform at sustainable economics. The deployment that commits on aspirational architectures without the supporting discipline carries cost surprises that erode the analytics business case. The 500-plus engagement experience across the broader Salesforce advisory portfolio consistently demonstrates that the Intelligence deployments that succeed commercially paired the capability commitment with the operational and structural discipline to use it well, and the Intelligence cost is well-controlled when both dimensions are addressed deliberately.