Platform & Architecture

Acquisitions

Integrating Datorama with Salesforce

Datorama became Marketing Cloud Intelligence. It does not replace Tableau. Integrate the report that still lives there.

A marketing team working in a modern office.Platform & Architecture

A Monday meeting uses a number. The number was redrawn in Tableau over the weekend, from a screenshot of an older report. The report that produced the original number still lives in Marketing Cloud Intelligence. Nobody opened it. The redraw is now called the Datorama connector. It does not replace the report, and it does not replace Tableau. Tableau remains Tableau. The connector, if there is one, is the report that still lives where the record says it lives. A picture with Datorama on one side and Tableau on the other, and no report name on the line, is a poster.

The person who used to trust the old report can still open it, or they cannot. That is the first fact. A redraw skips the fact and publishes a cousin of the number. The meeting then argues about a cousin.

The app

The app is Marketing Cloud Intelligence. The record says what Datorama became, and this page quotes that sentence once: "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."

Read the two renames in the sentence. Datorama became Marketing Cloud Intelligence. Datorama Reports for Marketing Cloud became Intelligence Reports for Engagement. The report you integrate is the one that still lives there, under the name the sentence gives it. A search for a Salesforce Datorama app is a search for that intelligence app, not for a workbook someone rebuilt because the old name felt clearer.

It does not replace Tableau. The sentence does not say Tableau moved inside Intelligence, and it does not say Intelligence moved inside Tableau. They are different tools. A diagram that erases Tableau because Datorama was bought has invented a merger. A diagram that erases Intelligence because Tableau feels more familiar has invented a retirement this page does not have. This page does not give Marketing Cloud Intelligence an end date. Do not borrow one from a different product.

Open the report before you draw the app. If you cannot find Intelligence Reports for Engagement, say you cannot find it. Do not fill the gap with a chart you made in Tableau and label the chart as the app. The app is the place the report still lives. The chart is a picture of a picture.

The connector

Integrate the report that still lives there. The connector is that report, named, with the number the meeting is supposed to use. Do not redraw it in Tableau and call that a connector. A redraw is a new chart. It can be useful later, on a Tableau page, for a decision you name. It is not a pipe from Datorama. Nothing was called. Nothing can fail, because nothing was sent. The meeting only has two drawings and a belief that they match.

Name the report. Name the figure on it that the meeting quotes. Name where that figure is read, which is Marketing Cloud Intelligence, in Intelligence Reports for Engagement, if that is where it still lives. If the figure has moved, and you have seen the move, say where you saw it. If you have not seen it, it has not moved on this page. The redraw does not count as seeing it.

This page does not name an API, a daily cap, a middleware SKU, a connector product, or a price. The record does not name them. A slide that puts a sync product between Intelligence and Tableau has added a box the sentence does not contain. Take the box off. The sentence contains a reporting tool that changed its name. Integrate that report. Stop.

Write one line the room can check. This report, this figure, opened in Intelligence, at this time. If the line says "Tableau now" and never names the Intelligence report, it is the redraw. Send it back. The old name Datorama can sit in a footnote so people can find the page. It cannot sit as the system the figure comes from, unless you are explaining the search, not the login.

The architecture

The architecture names Marketing Cloud Intelligence, the report that still lives there, and the failure when that report does not update. Tableau may appear on a different picture, as Tableau, for a workbook you actually maintain. It does not appear here as the destination of a connector. An arrow from Intelligence into a redraw, labelled integration, fails the test before anyone discusses colours.

What the picture must sayWhat you write
SystemMarketing Cloud Intelligence
ObjectThe report that still lives there, Intelligence Reports for Engagement
FailureThe report does not update

Do not draw CRM Analytics as a third home unless you are only repeating the history inside the quoted sentence. The sentence places Datorama in the suite of tools that formed CRM Analytics, and then says it became Marketing Cloud Intelligence. The place you open is Intelligence. A box that stops at the older suite name, and never reaches the report, is a history lesson drawn as an architecture. History belongs on the other page.

A guide book is not the report. People search for a Salesforce Datorama integration guide book because they want the number explained in general. This page will not invent that book. The number is whatever your report showed when you opened it. A book cannot open your report.

If both Tableau and Intelligence are in the programme, write two sentences. One says which decision the Tableau workbook is for. One says which figure still lives in Intelligence. If the sentences describe the same figure, you have one report wearing two pictures. Keep the report. Drop the claim that the redraw is a connector.

When the call does not land

The failure is a report that does not update. You opened Intelligence Reports for Engagement. The figure the meeting uses was not the figure on the report, or the report did not show a new figure at the time you looked. That is the call not landing. Write the report name, the figure, and the time. A ticket that says the Datorama feed into Tableau is broken has assumed a connector this page does not name. Ask which report, and whether anyone called anything.

If the only copy of the number is the redraw, there was no call to fail. Say that. The redraw cannot be late, because it is not connected. It can be wrong, because it was copied by hand from a screenshot. Wrong by hand is a copying problem. It is not an integration incident. Do not open an integration incident for a chart nobody linked.

When the report itself does not update, stay on that report. Who last saw it change. What the figure was then. What it is now. You do not need a Tableau workbook to answer those three. Opening Tableau first teaches the room that the redraw is the source. It is not. Intelligence is the source for the report that still lives there.

Do not invent an error code, a refresh cap, or a connector status. If the report shows a time, write the time you saw. If it shows nothing new, write that. Nothing new is the failure. It does not require a product name you found in a different catalogue.

An integration names three things

An integration exists only when the page can name the system, the object, and what happens when the call fails. A diagram that does not name those three is a poster.

The system is Marketing Cloud Intelligence. The object is the report that still lives there. The failure is that the report does not update. A diagram of Datorama, Tableau, and a lightning bolt has named two products and a decoration. It has not named the report or the failure. Take it down. Put the report name up, or admit you have not found the report.

The same test rejects the redraw. Do not redraw the report in Tableau and call that a connector. The test rejects a claim that Intelligence replaces Tableau, and a claim that Tableau replaces Intelligence. Neither sentence is in the record. The record says what Datorama became. It does not retire Tableau, and this page will not retire it either.

Keep the three sentences at the top of the design. Extra charts are allowed after the report is named and someone has opened it. A chart you cannot tie to that report in one sentence does not belong on this picture. It can live with the team that draws it, under Tableau's own name, without borrowing the integration.

The other two pages

This page is not the implementation page, and it is not the page about what happened. Which report moves, and which stays until a replacement matches, is implementation. That work is on the Datorama implementation page. The purchase and the rename as history are on what happened to Datorama. Stay here when the question is the app, the report, the architecture, and the report that does not update.

Do not let a stale figure become a Tableau migration. The stale figure is either a report that did not update, or a redraw that was never a call. Both are smaller than a programme. Link the other pages when someone asks what was bought, or what a real change to the report includes. Do not merge those questions into a connector fee. This page will not print a fee.

A partner who arrives with a guide book and a redraw has brought the poster. Ask them to open Intelligence Reports for Engagement and read the figure the meeting quoted. If they open Tableau instead, they are on the wrong system. If they cannot open the report, the integration has not started. The book will not start it.

Write the report name, the figure, and the time you opened it. If the figure matches what the meeting used, you do not have a fault to widen. If it does not match, say the report did not update, or say the meeting used a redraw. Those are different sentences. Pick the true one. Then stop. Do not draw a pipe you have not watched fail.

On the next Monday, open the same report before the meeting starts. Read the figure aloud from Intelligence, not from the slide. If the slide differs, correct the slide in the room. That correction is the integration being used. Leaving the slide in place, because it is already in the pack, teaches the next week to trust the redraw again. The report that still lives there only stays the source if someone opens it when the number is about to be said.

If the report cannot be opened, write that down and take the number out of the pack. A missing report is not a reason to reconstruct the figure in Tableau for one week "so the meeting has something". Something, in that sentence, is a new claim with the old name on it. The meeting can proceed without the figure. It cannot proceed on a figure you rebuilt and called a connector. Wait until the report opens, or decide in the open that this meeting does not use it.

Sources

  1. The ultimate guide to Salesforce product rebrands

Common questions

Answered, directly.

The questions this piece settles about Platform & Architecture, answered in full on this page.

Marketing Cloud Intelligence. Datorama Reports for Marketing Cloud became Intelligence Reports for Engagement. It does not replace Tableau.

The system, the object, and the failure. The system is Marketing Cloud Intelligence. The object is the report that still lives there. The failure is a report that does not update. Without those, the diagram is a poster.

The report that still lives in Marketing Cloud Intelligence, named, with a stated failure when it does not update. A redraw in Tableau is not that integration.

The report itself, under Intelligence Reports for Engagement if that is where it still lives. This page does not name an API, a middleware SKU, a daily cap, or a price. A Tableau chart is not the connector.

This page is not a book. The integration is your report, opened in Marketing Cloud Intelligence. The implementation page and the purchase page are separate.

Free architect conversation

Talk to an architect, not a sales rep.

Architecture review, before it gets expensive. 60 seconds to brief us, and a certified architect replies within one business day.

What decision is actually in front of you?

Pick the closest fit. The review is free, and we will tell you to keep your current design if keeping it is right.

What does this decision touch?

Optional. Choose any that apply, or skip ahead.

Where does your org stand today?

Optional. A few sentences is plenty: what is working, what is stuck, and what you want to be true. Or skip ahead and tell us on the call.

Who should the architect reach?

A certified architect will reply to these details.

Takes about 30–60 seconds · No obligation · Architect replies within one business day

Protected by reCAPTCHA. Google's Privacy Policy and Terms apply.

More from Insights

Read by desk

Ten desks, one delivery team. Every piece is written by the people who do the work.