What happened to ExactTarget

A renewal pack still says ExactTarget on the cover, and the room has already agreed what that means. Someone holds the pack up, searches the old name, and the next tab offers a month when the product will be switched off. The agreement is that the name is old, so the product is finished, so a project should start. That agreement is the problem. It fits three different explanations, and only one of them is in the record. Salesforce bought ExactTarget in 2013. The tools were not discarded in that deal. Email, mobile, and journey tools sit in Marketing Cloud Engagement. A month in which those sends stop is not a fact anyone in the room can point at.

The distinction that matters is between a company that was bought and a product that was ended. The cover is a contract habit. The login, if anyone opens it, carries a different name. The purchase year belongs in the conversation. The shutdown month does not. Marketing Cloud Next is a separate product and does not replace Engagement, so an arrow from the old company name to Next has skipped the product the tools were consolidated under. Which sends still run is a later decision, made against the account. It is not settled by the word on the pack.

What follows are the questions that separate a rename from a shutdown. Each has a good answer and a bad answer. The difference is whether the answer names something specific: a year, a product, a person who can open a send, a contract. A general answer at this stage is how a correct purchase becomes a false project.

A DVD, a Reddit thread, a YouTube clip, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown.

#The five, and what a bad answer signals

#1. Was ExactTarget bought, and where did the tools go?

The question is not whether the cover looks old. It is whether Salesforce bought the company, and which product the tools sit in now.

Yes. Salesforce bought ExactTarget in 2013. That is the ownership fact worth standing behind. The rebrand record says where the tools went, and the sentence is quoted once: "Email Studio, Mobile Messaging, Journey Builder, and legacy ExactTarget features were all consolidated under Marketing Cloud Engagement."

Read the verb. Consolidated under is a location. Email Studio, Mobile Messaging, Journey Builder, and legacy ExactTarget features sit in Marketing Cloud Engagement. The sentence does not say they were moved onto a blank org. It does not say they were switched off. You are not moving ExactTarget onto a blank Salesforce org. That sentence is the boundary.

People still type the old name because it is on the pack, on old exports, and on old training titles. The product name for those tools is Marketing Cloud Engagement. Use that name when you mean the place sends run. Use ExactTarget when you mean the company that was bought, or the word still printed on paper.

The acquisition, as the record can tell it, is the 2013 purchase and the consolidation under Engagement. There is no second chapter in which the tools were withdrawn.

A good answer sounds like the renewal owner reading the 2013 year off the record, then naming Email Studio, Mobile Messaging, and Journey Builder as sitting in Marketing Cloud Engagement, and refusing to draw Marketing Cloud Next as the place the purchase ended.

A bad answer sounds like ExactTarget is legacy, so we will rebuild it in Marketing Cloud Next. The first clause may describe the printing on a pack. The second describes a product the 2013 purchase did not produce. Next can be a later conversation. It is not the result of the purchase, and it does not replace Engagement.

#2. Which date can you defend?

1. The completion year is the one the rebrand record uses. The record does not add a day, a month, or an announcement hour. A timeline that needs a day is asking for a precision the record does not have.

Searches for an acquisition date, an announcement, and a timeline all get that answer. The date you can check is the year 2013. The record does not split an announcement date from a completion date. It gives the completion year. Do not promote a month remembered from another article into a fact you will repeat. If you cannot point at the sentence, you do not have the date. If a contract dispute needs a finer date, the contract is the document.

Write the year on the pack if you are correcting it. Do not write a season. Seasons are how a shutdown rumour starts. Someone sees early 2013 and later treats a neighbouring product's end date as if it were this one. Keep the year bare. Do not stack this purchase against a later deal and call the pair one programme. The year is a purchase. It is not an expiry.

A good answer sounds like a person from the renewal meeting writing 2013 on the slide, and striking any month, season, or announcement hour they cannot point at in the rebrand record or in the contract itself.

A bad answer sounds like it was early 2013, and the announcement was a different day we can fill in from memory. That is more precise than the record, which means it is invented. A month typed onto a slide because a timeline looked empty is not news. It is a guess.

#3. Who owns it now?

Salesforce owns it. On the facts in the record, ExactTarget is not an independent company a customer can still buy from. The product the tools sit in is Marketing Cloud Engagement.

Marketing Cloud Next is a separate product. It does not replace Engagement. A diagram with one arrow from ExactTarget to Next, and with Engagement missing, has skipped the product the tools were consolidated under.

Who owns a business unit, a sender, or a folder is an account question. The record does not know your tenants. It knows the product name. If two teams argue about who owns ExactTarget, ask whether they mean the company Salesforce bought, or the team that may still send. Those are different owners. The first is Salesforce. The second is whoever in your organisation still has the journeys.

Ownership is not a login shared with every Salesforce cloud. A Sales Cloud user is not, by that licence alone, an Engagement user. The acquisition did not pour email into the opportunity object. A person on a lead is not a subscriber in a journey. Saying Salesforce owns ExactTarget does not mean every org already contains the sends.

A good answer sounds like a named person who opened the account this week, confirmed the tools from the quoted sentence are in Marketing Cloud Engagement, and can say which colleague in the organisation still owns the journeys, while procurement holds the Engagement contract separately from any Sales Cloud login.

A bad answer sounds like Salesforce owns it, so anyone with a Sales Cloud licence already has the email. That collapses a company purchase into a login. The owner of the product is Salesforce. The owner of a journey is a person in your organisation. A missing Engagement user is not proof the product was switched off.

#4. What was paid?

The record cited here does not publish a purchase price or a licence fee. How much Salesforce paid, how much ExactTarget was sold for, and what a customer pays now are three different questions. The first two are answered by the silence. The silence is not filled with a figure.

A licence you already pay for Engagement is your contract. It cannot be printed from the rebrand record. A search that wants the acquisition price should stop on the absence, rather than on a remembered headline. A headline that is not cited is not a source.

Why Salesforce acquired ExactTarget, and why ExactTarget sold, are not in the sentence quoted above. The sentence says where the features were consolidated. It does not give a strategy, a buyer's motive, or a founder's reason. A motive you add cannot be checked against the record used here.

Impact on customers, as far as the record can say it, is the change of home for the tools. They sit in Marketing Cloud Engagement. Customers are not told to rebuild those tools because of the price, because there is no price here to react to. A business case that needs a deal value has to get that value from a document that actually prints one. The record used here does not have it.

A good answer sounds like procurement stating that the rebrand record is silent on the 2013 price, and then reading the current Engagement fee off the order form the organisation already holds, without copying either number onto the other.

A bad answer sounds like everyone remembers it was a large number, so we will use that number as the licence. A remembered figure is not the cited record. It is also not your contract. The two silences, deal value and customer fee, do not become one number because a slide has an empty cell.

#5. Is Engagement shut down?

The record does not give Engagement an end date. Do not invent one. Shutdown and sunset are the searches that produce the false month. The answer is that the record used here does not end the product.

Other names in this set were retired on a dated notice. Engagement is not one of them. Do not borrow a retirement date from a social tool, a data-management platform, or a sales product and pin it to ExactTarget. The deals are separate. The endings, where they exist, are separate.

A contract that still says ExactTarget can be corrected as a reading of the current product name. That correction is not a shutdown project. It is paper catching up with 2013. If a seller warns that the acquisition means the sends will stop, ask for the notice that names Engagement and names the day. If they cannot show it, the warning comes off the renewal.

The old name on a status page is not an end date either. Brands linger in exports, in folder trees, and in the subject lines of internal mail. Lingering is not a product being switched off. Open the account before you brief a shutdown. If the tools named in the quoted sentence are there, you are in Marketing Cloud Engagement, whatever the shared drive still says. The folder is not a second product. It is an old label on top of a current one.

Do not treat Marketing Cloud Next as the place the old name ended up, unless a separate decision says so, for a reason other than the purchase. The purchase ended in a consolidation under Engagement. Next is newer. It is not the epilogue of ExactTarget. If someone asks whether customers were forced onto a different product, the record does not say that. It says the features were consolidated under Engagement. Forced, declined, and worth-it are judgements that need your own sends in front of you, not a story about 2013.

A good answer sounds like the person who opened the account reporting that Email Studio and Journey Builder are still there, and that no notice in the file names Engagement and names a day.

A bad answer sounds like a social product retired on a dated notice, so ExactTarget retired in the same quarter. Those notices name their own products. Engagement is not given that sentence. A borrowed day is how a correct year becomes a false exit.

#What to do with the answers

Read the five as a set. Specific answers mean the pack can be corrected and the meeting can stop. General answers mean the room has agreed that an old name is an emergency, which is common and predicts nothing.

If the tools named in the quoted sentence are in the account, write three lines and take them to the meeting. The company was bought in 2013. The tools sit in Marketing Cloud Engagement. The record has no end date. Those lines do not choose which journey is still wanted. Keep the old name in a glossary if the contract needs the history. Do not let the glossary grow a shutdown. A board pack can carry the same three lines and nothing else from this history. Extra arrows, a deal value, and a sunset quarter are how a correct year becomes a false project.

Which sends still run in Engagement, and which jobs belong in Marketing Cloud Next, is not settled by the purchase. That work is on the ExactTarget implementation page.