Datorama implementation cost: Marketing Cloud Intelligence licences and services

Datorama was bought to solve a stubborn problem: marketing performance data scattered across ad platforms, analytics tools, email systems and spreadsheets, each with its own naming and its own idea of what a campaign is. The problem has not gone away, and neither has the product. The rebrand record explains where it went: "Datorama, part of the suite of tools that formed CRM Analytics, became Marketing Cloud Intelligence and its reporting tool, Datorama Reports for Marketing Cloud, became Intelligence Reports for Engagement." So when a buyer asks what a Datorama implementation costs in 2026, the answer is the cost of Marketing Cloud Intelligence, plus the work of feeding it clean data.

#How Marketing Cloud Intelligence is sold

Marketing Cloud Intelligence is licensed per org per month, not per user. Salesforce publishes the price on its Marketing Cloud Intelligence pricing page, which leads with a one-line pitch, "Improve performance with agentic marketing analytics." The figures below were read on 11 October 2026. Both editions are billed annually, and the page shows each in several currencies.

At list, that is US$120,000 a year for Marketing Intelligence and US$132,000 for Intelligence+. These are the entry points Salesforce publishes; your contract may differ, and multi-year terms and bundles with other Marketing Cloud products change the numbers. The same products also appear on the wider Marketing Cloud pricing page alongside Engagement and the personalisation products, which matters if you are negotiating several products together.

A licence at that level needs a business case. The question to ask is not what the tool costs but what reporting work it replaces. If analysts currently spend days each month exporting platform reports, reconciling naming and rebuilding the same spreadsheets, the case is easy to make. If a single team runs two ad platforms and a monthly report, a lighter approach, such as Tableau over a warehouse, may be enough, and the honest answer is to say so.

#Do not confuse it with Intelligence Reports for Engagement

The rebrand record also names a second, smaller product: the reporting tool that was Datorama Reports for Marketing Cloud, now Intelligence Reports for Engagement. That tool sits inside Marketing Cloud Engagement and reports on Engagement sends. It is not the same as a full Marketing Cloud Intelligence org pulling in paid media, web analytics and CRM data. Buyers sometimes receive a proposal for one while thinking of the other. Check which product your quote is for before you compare it with anything.

#What drives the implementation cost

Marketing Cloud Intelligence implementations are data projects first and dashboard projects second. The licence buys you the platform; the work is in getting data in, making it consistent, and deciding what to measure. These are the factors that make the job larger or smaller.

Number and type of data sources. Each source, whether a search platform, a social ad platform, a programmatic buying tool, web analytics, Marketing Cloud Engagement, CRM or offline spend files, needs a data stream configured, tested and owned. Sources with standard API connectors are quicker. Sources that arrive as files from agencies or spreadsheets take longer and break more often.

Campaign naming and harmonisation. This is the single biggest driver, and it is the one most buyers underestimate. Intelligence can only join a search campaign, a social campaign and an email send into one view if something links them: a shared campaign key, a naming convention, or mapping rules that extract the key from each platform's names. If your naming has been inconsistent for years, someone has to write and maintain those rules, or fix the naming upstream. Neither is quick.

The data model. Mapping each source's fields to Intelligence dimensions and measurements, agreeing what a conversion is, and setting currency and time zone rules. Disagreement between teams about definitions shows up here and has to be settled by people, not software.

Calculated measurements and KPIs. Return on ad spend, cost per acquisition, blended metrics across channels and anything with custom attribution logic. Each one needs a definition, a formula and a test against a known result.

History. How many months of past data you want to load. A year of history across ten sources is a real migration, and some platforms limit how far back their APIs will go.

Dashboards and audiences. Executives, channel managers, agencies and analysts each want different pages. Count the audiences, not the dashboards, and ask who will maintain each view after launch.

Permissions. Agencies and regional teams may need to see only their own data. Workspace and access design adds effort, and it matters for privacy.

#The work packages in a comparable quote

A Marketing Cloud Intelligence quote that you can compare against another names these packages and the assumptions behind each.

Discovery lists every data source, its owner, its access method and its history, and records the KPIs each audience actually uses. It should also produce a sample of real campaign names from each platform, because that sample tells you how hard harmonisation will be.

Design sets the data model, the harmonisation approach, the KPI definitions, the workspace and permission structure, and a list of dashboards by audience.

Build configures data streams and connectors, mapping and harmonisation rules, calculated measurements, alerts and dashboards.

Data loading brings in history for each source, with checks that totals match the source platforms for a sample period. This reconciliation step is the one that builds trust, and it is the one most often cut to save time.

Testing compares Intelligence numbers with each platform's own reporting, and explains every difference that matters. Training is for analysts who will maintain the model and for business users who will read it. Hypercare covers the first month or two of live reporting, when the first unexplained gap appears and someone has to track it down.

#Hidden costs and the questions to ask

Connector upkeep. Ad platforms change their APIs and fields regularly. Ask who updates the data streams when that happens, and whether that is in a support agreement or billed as new work.

Naming cleanup. If harmonisation depends on fixing naming conventions upstream, that work happens in the ad platforms and agencies, not in Intelligence. It may sit outside the quote entirely.

Agency cooperation. Agencies often own the ad accounts. Getting access and consistent naming from them can take longer than the build, and it may need to be written into their contracts.

Admin after launch. Someone has to own the data streams, the mapping rules and the dashboards. If that person does not exist in your team, the cost has not gone away; it has become a managed service line or a hire.

Related products. If the plan includes Data 360 for unified profiles, Tableau for wider business reporting, or Marketing Cloud Engagement data, each brings its own licence and its own integration scope. Data 360 in particular consumes credits.

Support. The pricing page lists Premier and Signature Success Plans. Premier is priced as a share of net licence fees, so it adds a meaningful amount on top of a licence of this size.

When you ask for proposals, send every bidder the same brief: the list of sources with access method and history required, a sample of campaign names from each platform, the KPIs that matter, the audiences who need dashboards, and whether agencies will feed data. Ask each to state how many sources and calculated measurements are included, how many months of history they will load, how they will handle naming that does not follow a convention, and what ongoing connector maintenance they assume. Those four answers explain most of the difference between two quotes.

#How scope grows, and how to keep it in check

It helps to picture how a typical Intelligence project changes shape between the first meeting and go-live, because that is where budgets break.

The first meeting usually starts with a dashboard. A marketing leader wants one view of spend and results across channels, refreshed daily, that the board can trust. That sounds like a dashboard project, and the first quote often reads like one: a handful of sources, a few pages, a short timeline.

Discovery then finds the sources are not a handful. Search and social are obvious, but there is also programmatic display bought through an agency, affiliate spend in a spreadsheet, offline media in a monthly invoice, web analytics with its own conversion definitions, and email results from Marketing Cloud Engagement. Each one is reasonable on its own. Together they double the connector work.

Then the naming sample arrives, and it turns out each agency has its own convention, the convention changed twice last year, and some campaigns were named by hand. Harmonisation, which looked like a configuration task, becomes the main workstream. Finally, the finance team asks why Intelligence spend does not match the invoices, and a reconciliation step nobody priced becomes essential.

None of this is unusual, and none of it means the project was badly sold. It means the first quote priced the visible part. You can keep scope honest in three ways. Run discovery as its own small, fixed-price piece of work before committing to the build, so that the build quote is based on what discovery found. Phase the sources, starting with the channels that carry most of the spend and adding the long tail later. And agree a naming convention with agencies before the build starts, so harmonisation rules are written once against a standard instead of many times against history.

A phased plan also gives you an early, honest test of value. If the first phase, covering the main paid channels, does not change how the team spends money, adding ten more sources will not fix that. If it does, the business case for the remaining phases writes itself, and the next quote is easier to approve because it rests on results rather than promises.

#Moving, replacing or keeping it

Some long-standing Datorama customers are asking whether to keep Marketing Cloud Intelligence at all. The options usually on the table are to keep it and invest in cleaner data, to move reporting into Tableau over a data warehouse, or to bring marketing data into Data 360 and report from there. Each has a different licence shape and a different services profile, and none is free to reach. Price the exit as carefully as the stay, including the cost of rebuilding harmonisation rules and dashboards elsewhere and the months when both tools run while reports are checked against each other. If the current org is working and the data is clean, the cheapest project may be no project at all, beyond a renewal.

#Where to go next

Renewal and licence questions are on the Datorama licence cost page. The acquisition history is on what happened to Datorama, and the product as it stands is described on the Marketing Cloud Intelligence page. To choose a firm, read who to hire for Datorama. For connector and API work, see integrating Datorama with Salesforce, and for the keep or replace decision, should I migrate from Datorama. If Intelligence will sit alongside the newer Marketing Cloud products, our Marketing Cloud Next page explains how we approach that.