# Integrating ExactTarget with Salesforce

Email, mobile, and journeys sit in Marketing Cloud Engagement. The connector is a named send and a subscriber key. A journey that does not fire is the failure.

**Published:** 2025-10-21
**Canonical:** https://synconai.com/integrating-exacttarget-with-salesforce
**Author:** SynconAI Architecture Team

## In short

Email, mobile, and journeys sit in Marketing Cloud Engagement. Marketing Cloud Next does not replace Engagement. A Salesforce sandbox does not clone Marketing Cloud. The connector is a named send and a subscriber key. The failure is a journey that does not fire. This page does not choose which send to change, and it does not retell the purchase. Those questions sit on the other two pages.

## Sources

- **The ultimate guide to Salesforce product rebrands** (retrieved 2026-10-10)
  https://gearset.com/blog/salesforce-product-rebrands/
  > Email Studio, Mobile Messaging, Journey Builder, and legacy ExactTarget features were all consolidated under Marketing Cloud Engagement.

## What to take away

- Email, mobile, and journeys sit in Marketing Cloud Engagement. Marketing Cloud Next does not replace Engagement.
- A Salesforce sandbox does not clone Marketing Cloud.
- The connector is a named send and a subscriber key. The failure is a journey that does not fire.
- A diagram that omits the system, the object, and the failure is a poster.

## The guide

A journey was supposed to leave at nine. The marketer refreshed the send and the count stayed at zero. On the wall, a diagram has two boxes and an arrow. One box says ExactTarget. The other says Salesforce. The arrow has no send name and no subscriber key. Someone says the sandbox already contains Marketing Cloud, so the miss is only a mapping. A Salesforce sandbox does not clone Marketing Cloud. The send, if it exists, sits in Marketing Cloud Engagement. The diagram has not named the system, the object, or what happens when the call fails. It is a poster. This page puts those three names on the arrow, and then it stops.

The person who owns the journey is still waiting. A poster does not tell them which send was meant to fire, or which subscriber key was meant to enter it. Until those words are on the page, there is nothing to integrate and nothing to repair. The rest of this page is how to write the three names without inventing a product the record does not contain.

## The app

The app you open for this work is Marketing Cloud Engagement. Email, mobile, and journeys sit there. The rebrand record says where they were consolidated, and this page quotes that sentence once: "Email Studio, Mobile Messaging, Journey Builder, and legacy ExactTarget features were all consolidated under Marketing Cloud Engagement."

Read the names in the sentence. Email Studio, Mobile Messaging, Journey Builder, and legacy ExactTarget features are the place the work lives. Consolidated under is a location. It is the app. A search for a Salesforce ExactTarget app is a search for that location, under the name people still type. The login may still show an old word on a bookmark. The product that holds the send is Marketing Cloud Engagement.

Marketing Cloud Next does not replace Engagement. A diagram that draws one arrow from ExactTarget to Next, and leaves Engagement off the page, has skipped the app the tools were consolidated under. Next can be a later conversation, on its own page, for a reason that is not this connector. It is not the system this integration calls.

Write the app name on the diagram before you draw anything else. If the box still says ExactTarget and nobody can open Engagement and find the send, you do not have an app. You have a word from an old contract. The contract word can stay in a glossary. It cannot be the system the arrow points at.

## The connector

The connector is a named send and a subscriber key. That is the whole of what this page will call a connector. The send is the thing that was supposed to leave. The subscriber key is the identity the journey uses for the person who should have entered it. If either name is missing, you do not have a connector. You have a wish that mail and the CRM should meet.

A named send is a send someone can point at in Engagement. It has a name the marketer recognises, a business unit it lives in, and a result from this morning: it fired, or it did not. A subscriber key is the value the journey expects. This page will not invent the field on the CRM side, the length of the key, or a daily cap. Those live in your account, if they live anywhere. Write the key you actually pass. If you cannot write it, the connector is not designed yet.

Do not invent an API name. Do not invent a middleware SKU. Do not invent a price. The record this page cites does not name a connector product, a call limit, or a fee. A slide that adds one has left the record. Take the invented name off before you review the arrow. The arrow may only say the send and the key.

A person on a lead is not, by that fact, a subscriber. The integration is the moment a specific subscriber key is handed to a specific send, and the journey either fires or it does not. Copying a contact into a spreadsheet and calling the paste a connector has skipped both names. Put the send name and the key name in the first sentence of the design. If the sentence cannot be written, stop the design.

## The architecture

An architecture for this integration has three labels and a direction. The system is Marketing Cloud Engagement. The object is the named send, addressed by the subscriber key. The failure is that the journey does not fire. Draw those three. Anything else on the picture is optional, and it has to earn its place by naming a real send you have opened.

| What the picture must say | What you write |
| --- | --- |
| System | Marketing Cloud Engagement |
| Object | The named send, and the subscriber key it expects |
| Failure | The journey does not fire |

A Salesforce sandbox does not clone Marketing Cloud. Refreshing a core sandbox does not copy Email Studio, Mobile Messaging, or Journey Builder, and it does not replay this morning's send. Anyone who says the sandbox already contains the app should open it and show the journey. The absence is the finding. The architecture that starts from a sandbox refresh has started from the wrong system.

Marketing Cloud Next does not sit on this diagram as the replacement box. If a later decision uses Next for a different job, that decision gets its own picture, with its own system, its own object, and its own failure. This picture is Engagement, the send, and the journey that did not fire.

A guide book is not an architecture. People search for a Salesforce ExactTarget integration guide book because they want a finished picture. This page is not that book, and it will not invent one. The picture is finished when the three labels are true of your account. A printed book cannot know your send name.

## When the call does not land

The failure this page will stand behind is simple. The journey does not fire. You named a send. You passed a subscriber key, or you meant to. The person did not enter the journey, or the message did not leave. That is the call not landing. Write it as an observable fact, with the time you looked, not as a theory about platforms in general.

Check the three labels in order. Is the system Engagement, and can the marketer open the business unit? Is the send the one you named, and is it the one that was supposed to run at nine? Is the subscriber key the value that journey expects, and was that value the one you passed? If any answer is no, the integration did not run. Do not add a fourth label called platform health. You do not have a measurement for it on this page.

When the journey does not fire, the work is to say which of the three failed. The system was wrong, because someone pointed at a sandbox or at Marketing Cloud Next. The object was wrong, because the send name or the key did not match. Or the call was made and the journey still did not fire, which you record as the failure itself, with the send name beside it. A ticket that says "ExactTarget integration down" has not said which. Send it back until it has.

Do not invent a retry cap, a queue name, or an error code the record does not give. If Engagement shows a status, quote the status you saw, on that send, at that time. If it shows nothing, write that it showed nothing. Silence is a result. It is not permission to invent a fault code so the ticket looks complete.

## 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.

For this page the system is Marketing Cloud Engagement. The object is the named send, together with the subscriber key. The failure is that the journey does not fire. If a proposal cannot say those three sentences, it is not an ExactTarget integration. It is a drawing. Decline the drawing in the meeting where it appears. You do not need a workshop to notice a missing send name.

The same test rejects a connector that is only a logo. ExactTarget on one side and Salesforce on the other, with a line between them, fails the test. So does a line that names a middleware product this page has not sourced. So does a line that ends in Marketing Cloud Next because someone wanted a newer word. The test is the three names, said in the open, against a send the marketer can open.

Write the three sentences at the top of the design and keep them there when the picture grows. Extra boxes are allowed only after the three are true. A box you cannot explain in one sentence does not go on the picture. The sentence has to say what the box holds, which is a send or a key, or it has to come off.

## The other two pages

This page is not the implementation page, and it is not the page about what happened. Implementation is which sends still run, and which jobs, if any, belong somewhere else. That work is on [the ExactTarget implementation page](/exacttarget-marketing-cloud-engagement). The purchase, the owner, and the missing end date are on [what happened to ExactTarget](/what-happened-to-exacttarget). Stay here when the question is the app, the connector, the architecture, and the journey that did not fire.

Do not let one meeting answer all three questions with one arrow. The purchase does not name your send. The implementation choice does not, by itself, tell you what failure looks like this morning. This page tells you the failure. The other pages tell you the history and the change, if there is a change. Link them. Do not merge them into a single project called integration, with a single price this page will not print.

A partner who arrives with a guide book, a poster, and a shutdown date has brought three things this page refuses. The book is not your send. The poster is not an architecture. The shutdown date belongs to neither page until a notice this set has cited actually gives one. Engagement has no end date on the page that tells the purchase. It has no end date here either. The journey that did not fire is a fault in a live app, not a sign that the app has been replaced.

::: warn
A Salesforce sandbox does not clone Marketing Cloud. Marketing Cloud Next does not replace Engagement. The connector is a named send and a subscriber key. If the journey does not fire, that is the failure. A diagram without those three names is a poster.
:::

Put the send name, the subscriber key, and the time you looked on one line, and take that line to the meeting. If the line cannot be filled, you are earlier than an integration. Go and open Engagement. Find the business unit. Find the send. Then come back. The arrow can wait. The poster cannot be allowed to stand in for the line.

When the line is filled and the journey still does not fire, you have a real fault, on a named send, in Marketing Cloud Engagement. That is the point at which someone who can see the journey should look. It is not the point at which someone redraws the estate, adds a product, or prices a move. The call did not land. Say so, with the names. Then stop.

## Questions

### What is the Salesforce ExactTarget app?

Marketing Cloud Engagement. Email, mobile, and journeys sit there. Marketing Cloud Next does not replace Engagement. A Salesforce sandbox does not clone Marketing Cloud.

### What must a Salesforce ExactTarget architecture diagram name?

The system, the object, and the failure. The system is Marketing Cloud Engagement. The object is a named send and a subscriber key. The failure is a journey that does not fire. A diagram without those three is a poster.

### What is an ExactTarget Salesforce integration?

A named send in Marketing Cloud Engagement, addressed by a subscriber key, with a stated failure when the journey does not fire. A line between two logos is not that integration.

### What is the ExactTarget Salesforce integration connector?

A named send and a subscriber key. This page does not name an API, a daily cap, a middleware SKU, or a price. If the send or the key is missing, there is no connector.

### Is there a Salesforce ExactTarget integration guide book?

This page is not a book, and it will not invent one. The integration is your send name, your subscriber key, and the journey that does not fire. The implementation page and the purchase page are separate.

---

SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Marketing Cloud Next (https://synconai.com/salesforce-marketing-cloud-next).