Integrating Radian6 with Salesforce

A dashboard still has a panel labelled Radian6. Someone asks for a connector so the panel keeps filling after the studio closed. The panel is a picture of old numbers. The connector would be a call to a listening product that was retired with Social Studio. Do not build that connector. Social Studio was retired on 18 November 2024. A listening call cannot land. Drawing the call anyway is a poster, and running it on a schedule is how a retired product stays in the operating list.

The person who presents the panel has not opened a listening workspace this year. The request treats that gap as an integration backlog. It is not a backlog. It is a product that ended. This page is the refusal to wire the panel back up.

#The app

There is no listening app to call. The notice covers the subscriptions, and this page quotes it once: "Salesforce retired the following Marketing Cloud Social Studio subscriptions (“Marketing Cloud Social Studio Products”) on November 18, 2024." The date, in our calendar, is 18 November 2024.

Radian6 was the listening side of that story. A search for a Salesforce Radian6 app assumes the listening store is still a place a connector can read. This page will not say the store is still there. The fact we have is the retirement of the Marketing Cloud Social Studio subscriptions. Plan the architecture from that fact. A workspace nobody can show, on your tenant, on a dated screen, is not an app. It is a label on a chart.

Do not name a replacement product. The notice does not appoint a listening successor. A connector whose other end is "the new listening tool" has named a replacement by description, even without a logo. Take the description off. If the business later chooses a way to listen, that choice is a new brief. It does not inherit the Radian6 connector, and it does not get designed on this page.

The publishing half of the same retirement is not a back door into listening. Closing one and building the other still builds a connector to a retired product. Read the refusal as one retirement. Two diagrams do not make two living systems.

#The connector

Do not build a connector to a retired listening product. The connector people ask for is a query: topics, mentions, a sentiment figure, pulled on a schedule into a report or a record. The product that answered that query was retired with the subscriptions. A query against it cannot land. Building the query in hope that a host still answers is how you discover the retirement in production, which is a worse place to read a notice.

There is no partial connector that "only reads history". History you have not opened is not a feed. If you already have an export, it is a file with a date. Label it as a file. Do not point a connector at the file and call the file Radian6. The file does not update. A job that pretends it updates is the forbidden connector, aimed at a spreadsheet.

This page does not name an API, a daily cap, a middleware SKU, a query language, or a price. The notice does not give them. A slide that specifies how often to poll a retired listening product has designed the thing you must not build. Delete the poll. Delete the cap you invented to make the poll look governed. There is nothing to govern.

Write the connector line as a stop. No query to Radian6. No query to Social Studio listening. No scheduled pull. No replacement named in the same paragraph. Put that line where the integration specification would have started. Reviewers should see the stop before they see a box.

#The architecture

The architecture names a retired listening product and a call that cannot land. It does not name a pipe. A Salesforce Radian6 architecture diagram that shows mentions flowing into a CRM object is a poster of a store this page will not treat as live. Cross out the flow. Leave the date.

A guide book is not a listening archive. People search for a Salesforce Radian6 integration guide book because they want the query written down. This page will not write the query. Writing it would be the connector. The book, if someone offers one, is the poster with a spine. Decline it.

Do not draw a warehouse, a lake, or a middleware box as the place old mentions now live. Those boxes are replacements this page does not name, or they are guesses about a store the notice does not describe. The notice retires subscriptions. It does not, in the sentence we cite, hand you a new system of record for listening. Do not draw the handoff you were not given.

Charts in the quarterly pack are not systems. If a chart says the figure came from Radian6, either you have the export that shows it, or you take the sentence off the chart. Leaving the sentence up is an architecture decision. It tells the next reader the connector should exist. Correct the chart. That correction is the diagram this page allows.

#When the call does not land

The failure is a listening call that cannot land. You do not retry it. You do not interpret a timeout as a capacity problem. The subscription was retired on 18 November 2024. A timeout, an authentication error, or an empty payload is the same outcome: the call did not land, and it will not start landing because you changed a setting. Write the retirement date as the cause. Stop the schedule that made the call.

If no schedule exists yet, the failure is still the right name for the proposal. The proposed call cannot land. Record the proposal as refused, with the date, so a later quarter does not treat the refusal as unfinished work. Unfinished work grows a connector. A refusal stays a refusal.

Do not reconstruct the missing mentions from memory, from a social network you personally scrolled, or from a model, and then label the reconstruction as the landed call. That label teaches the room the listening product survived. It did not survive on this page. A new observation, if you truly make one, needs its own date and a name that is not Radian6. This page will not choose that name.

Do not invent an error code catalogue so the stop can sit in an incident tool under a vendor's scheme. One line is enough. Listening call not built, or listening call stopped. Cause: subscriptions retired on 18 November 2024. Owner: the person who would have presented the panel. When that line is visible, the incident is done.

#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 listening system. It cannot name a live object such as a topic feed you are allowed to query. It can name the failure: the call cannot land. Because the system and the object are missing, the integration does not exist. Do not "complete" the test by inventing a feed so the diagram looks like other integrations in this set. Those other integrations have apps you can open. This one does not.

The same test rejects a connector that only runs in a proof. A proof against a retired listening product is still a call. It still cannot land, or, if something answers, this page will not treat that answer as a system of record. You were told not to build the connector. A successful-looking proof is not permission. It is a reason to stop and re-read the date.

Keep the three lines in the table on the wall where the panel used to hang. The panel can stay in a folder as a picture of a past quarter, labelled as a picture. It cannot stay in the operating review as a live source. A live source would need the system, the object, and a failure you can watch this week. You have the failure only. That is not enough to integrate. It is enough to stop.

#The other two pages

This page is not the implementation page, and it is not the page about what happened. What you can prove you still hold, and the instruction not to treat the listening store as current, is on the Radian6 implementation page. The retirement as history is on what happened to Radian6. Stay here when the question is the app, the connector, the architecture, and the listening call that cannot land.

Do not let a history of the acquisition become a feed, and do not let an inventory of old slides become a specification for a query. The other pages answer different questions. Link them. Do not merge them into one connector project with a fee. This page will not print a fee, and it will not price a poll against a retired product.

Buddy Media is the same retirement, seen from publishing rather than listening. The connector refusal is the same shape. If one proposal covers both, it is two posters. Read the Buddy Media integration page and then strike both arrows. Same notice. Same date. No replacement named on either page.

A partner who offers a guide book of listening queries has offered the build this page forbids. Ask for the tenant they will query, on a screen, this week. If they cannot show it, the book is fiction. If they show a different product, they have named a replacement. Strike that too. The test is short because the date is already past.

Take the panel out of the operating pack, or label it as a past picture with no feed behind it. Stop any job that still calls the old name. Write the date in the runbook where the connector specification would have been. Then stop. The next request for a listening integration has to arrive as a new brief, without the word Radian6 in the solution, and without a claim that this page chose the tool. This page chose the refusal.

If a later brief arrives with the old panel attached "for context", send the panel back. Context is how a connector re-enters. The reader sees a chart, assumes a feed, and asks for the feed to be repaired. There is no feed to repair. The attachment should be the notice and the date, not the chart. A chart without a source line will be read as a source. Add the line "not a live feed; subscriptions retired on 18 November 2024" or remove the chart. Do not leave it to be interpreted kindly. Kind interpretations build connectors.

When someone asks what the listening number is this week, say it is not available from Radian6. Offer the decision without that number. Do not ask a partner to reconstruct the chart and label the result as migrated history. A reconstruction is a new claim. It needs its own evidence and a name this page will not choose. The gap is allowed. A gap dressed as a connector is not.