# Integrating Buddy Media with Salesforce Social Studio was retired on 18 November 2024. Do not build a new connector. This page does not name a replacement product. **Published:** 2026-01-06 **Canonical:** https://synconai.com/integrating-buddy-media-with-salesforce **Author:** SynconAI Architecture Team ## In short Social Studio was retired on 18 November 2024. There is no Buddy Media app left to call. Do not build a new connector. Do not name a replacement product. A call cannot land, because the subscription is gone. A diagram of a connector is a poster. What you still hold, and the purchase story, sit on the other two pages. ## Sources - **Marketing Cloud Social Studio Retirement** (retrieved 2024-11-18) https://help.salesforce.com/s/articleView?id=sf.mc_cc_faq_resolve_missing_data_in_social_care_display.htm&type=5 > Salesforce retired the following Marketing Cloud Social Studio subscriptions (“Marketing Cloud Social Studio Products”) on November 18, 2024. ## What to take away - Social Studio was retired on 18 November 2024. There is no Buddy Media app to integrate. - Do not build a new connector. Do not name a replacement product. - The call cannot land. That is the failure, and it is not a prompt to design a pipe. - A diagram that still draws a connector is a poster. ## The guide A brief asks for a Buddy Media connector. The diagram has a social network on one side and Salesforce on the other, and a box in the middle with no product name, because the author is waiting for this page to supply one. This page will not supply one. Social Studio was retired on 18 November 2024. Buddy Media does not have a current app to call. Do not build a new connector. Do not name a replacement product. The arrow cannot land, because there is nowhere for it to land. The diagram is a poster of a product that has already ended. The person who used to publish from that studio cannot open it and show a tenant. Until they can, which they cannot on the facts this page has, there is no integration to design. There is a retired subscription and a drawing. The drawing has to come down. ## The app There is no app. The notice this page cites says so in the verb it uses, and this page quotes it once: "Salesforce retired the following Marketing Cloud Social Studio subscriptions (“Marketing Cloud Social Studio Products”) on November 18, 2024." In our calendar that date is 18 November 2024. The notice's own wording stays inside the quotation. A search for a Salesforce Buddy Media app still returns the old name, because contracts and slides keep it. The name is not a login. Marketing Cloud Social Studio was the product those subscriptions belonged to. The notice retires the subscriptions. After that verb, there is no studio to open, no tenant to point a connector at, and no Buddy Media app hiding under a newer label this page is allowed to reveal. This page does not name a replacement product. A replacement you have not sourced is a guess. Guesses do not become the system on an architecture. Read the notice for the subscriptions it lists. This page will not invent the list from memory. A connector aimed at a subscription you cannot read on the notice, or at a subscription the notice retired, is a connector aimed at a gap. Delete the aim. If a bookmark still resolves, a redirect or a marketing page is not an app. An app is a tenant a named person can open. If they cannot, write that they cannot. That sentence replaces the box on the diagram. ExactTarget's tools still have a home this set can name. Social Studio does not, on this page. Do not borrow a living product's pattern and paste Buddy Media into it. The verb here is retired. Design for that verb. ## The connector Do not build a new connector. A connector needs a system that can receive a call. This one cannot. Building the connector anyway, against a retired subscription, produces a project that fails on the first attempt and then asks for a phase two. Phase two is where an unsourced replacement usually appears. Refuse phase two in the same breath as phase one. There is no first call worth making. Do not name a replacement product. The notice does not name one. A partner who writes a destination in the middle box has left the notice. Take the destination off, even if you like the product, even if another team uses it for a different job. Another team's tool is not appointed by this retirement. If you later choose a tool for publishing, that choice gets its own brief, and the brief does not say Buddy Media in the solution. This page stops before that choice. This page does not name an API, a daily cap, a middleware SKU, or a price. There is no call limit to tune, because there is no call to make. A SKU in the middle of the picture would be an invention on top of a retirement. A price for the connector would be a fee for a pipe to nowhere. This page will not print one. The honest connector statement is a refusal. We will not connect to Buddy Media. We will not connect to Marketing Cloud Social Studio. We will not connect to a product this page does not name. Write that on the brief where the arrow used to be. A blank box is how the arrow returns in the next draft. Fill the blank with the refusal, not with a logo. ## The architecture The architecture is the absence of a connector. You can draw the date. You can draw the retired name, crossed out, with the notice beside it. You cannot draw a live arrow. A diagram that shows a social account flowing into Salesforce through a connector, dated after 18 November 2024, is a poster. It describes a call the subscription cannot accept. | What the picture must say | What you write | | --- | --- | | System | None. Social Studio subscriptions were retired on 18 November 2024 | | Object | None you can call. Do not invent one | | Failure | The call cannot land | People search for a Salesforce Buddy Media architecture diagram and expect boxes. Give them the three lines in the table instead. The lines are the diagram. Extra boxes are how a retired product starts looking buildable. A guide book is not an exception. This page is not a Salesforce Buddy Media integration guide book, and it will not invent the chapters a book would use to specify endpoints. There are no endpoints on this page. If someone still holds an export from before the retirement, the export is a file. Draw it as a file, with a date and a person, not as a system the connector reads. A file does not refresh. A connector that "keeps the file in sync" is the new connector this page forbids, wearing a gentler verb. Sync with a retired studio is still a call that cannot land. ## When the call does not land The failure is that the call cannot land. You do not get a partial success, a queued retry, or a degraded mode. The subscription was retired. A call aimed at it has nowhere to arrive. Write the time you confirmed there is no tenant, and the notice's date. A ticket that says the Buddy Media connector is down asks for a repair. There is nothing to repair. Close the ticket as "do not build", with the date on it. Do not watch a queue for a response that cannot come. Do not add retries. Do not page an on-call for a studio nobody can open. Those habits belong to a living integration. Applying them here spends a night on a poster. The failure is already known. It is the retirement. Record it once, in the place your team looks for runbooks, so the next brief dies in the first paragraph. If a call was built before you read the notice, stop it. A job that posts, pulls, or listens on a schedule against that name is the connector you are now forbidden to keep. Switching it off is not a migration. It is the end of a call that cannot land. Say what the job was trying to touch, in plain words, and say it has been stopped. Do not point the job at a new product in the same change. That pointing is the replacement this page will not name. Do not invent an error code to make the stop look like an incident platform. "Retired on 18 November 2024" is the status. If a screen shows something else, write what you saw, and do not promote it into a product name. A login error is not a destination. ## 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. This page cannot name a live system. It cannot name a live object. It can name the failure: the call cannot land, because Social Studio was retired on 18 November 2024. A page that cannot name the system and the object does not have an integration. Say that in the meeting. The three-part test is how you refuse the diagram without a long argument. They have a poster. You have a date. The same test rejects every softer version. A read-only connector is still a connector. A historical sync is still a connector. A connector "until we pick a replacement" is still a connector, and it smuggles the replacement in the same sentence. Do not build any of them. Do not name the replacement while you refuse them. Keep the refusal at the top of the picture. You may list files you already hold, as files. You may not draw an arrow from those files into a living system and call the arrow Buddy Media. The files are evidence of what someone saved. They are not a tenant. The implementation page is where an inventory of files belongs, if you need one. This page's job is to stop the connector being drawn. ## The other two pages This page is not the implementation page, and it is not the page about what happened. What you still hold, and the fact there is nothing to implement, is on [the Buddy Media implementation page](/buddy-media-social-studio-retirement). The retirement as history, and the ownership question, are on [what happened to Buddy Media](/what-happened-to-buddy-media). Stay here when the question is the app, the connector, the architecture, and the call that cannot land. Do not let the other pages talk you into a pipe. The implementation page does not ask you to build a connector. The history page does not name a successor for you to connect. If a meeting uses those pages as permission to draw an arrow, the meeting has misread them. Link them for the inventory and the date. Do not merge them into a build. This page will not print a price for a build that must not exist. The listening half of the same retirement is a different trap, and it gets its own refusal. A connector that promises posts and listening in one pipe is two forbidden calls. Read [the Radian6 integration page](/integrating-radian6-with-salesforce) before you let one diagram cover both. Same date. Same instruction. Do not build. A partner who brings a guide book with a connector chapter has brought the poster bound. Ask them to put the retirement date on the first page of their proposal and to strike the connector. If they replace the strike with a product name, they have failed the only test this page has. You do not need a second vendor to confirm a retired subscription. ::: warn Social Studio was retired on 18 November 2024. Do not build a new connector. Do not name a replacement product. The call cannot land. A diagram that still shows a connector is a poster. ::: Write the date on the diagram and remove the arrow. Tell the next person who searches for a Buddy Media app that the app is not there to call. Keep the notice with that sentence. If a job is still scheduled, stop the job and do not retarget it. The integration work is the refusal. When the refusal is in the runbook, stop. There is no phase two on this page. ## Questions ### What is the Salesforce Buddy Media app? There is no current app. Marketing Cloud Social Studio subscriptions were retired on 18 November 2024. This page does not name a replacement. ### What must a Salesforce Buddy Media architecture diagram name? It must say there is no live system, no live object, and that the call cannot land. Social Studio was retired on 18 November 2024. A connector on the diagram is a poster. ### What is a Buddy Media Salesforce integration? Nothing you should build. The subscriptions were retired. An integration would need a system, an object, and a failure you can watch. This page cannot name a live system or a live object. ### What is the Buddy Media Salesforce integration connector? Do not build one. Do not name a replacement product, an API, a middleware SKU, or a price. A connector to a retired subscription cannot land. ### Is there a Salesforce Buddy Media integration guide book? This page is not a book, and it will not specify a connector. The implementation page covers what you still hold. The other page covers the retirement. Neither is a build manual. --- 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).