Radian6 licence cost: listening tools priced today

Radian6 is the cleanest example of a licence that has to be rebuilt from scratch. The product itself is gone, but the job it did, watching what people say about a brand and routing the important parts to a person, is still wanted by plenty of organisations. The trade press put the origin plainly: "Salesforce acquired Radian6, a social listening platform designed to help brands monitor what was being said about them on social media channels." That sentence describes a function, and functions are what you can still buy. This page is about how that function is licensed today, using published figures read on 13 October 2026, and it keeps implementation work on the Radian6 retirement guide.

#What ended, and the date that matters

Salesforce's retirement notice carries the key fact: "Salesforce retired the following Marketing Cloud Social Studio subscriptions (“Marketing Cloud Social Studio Products”) on November 18, 2024." The same trade article, written as the retirement approached, describes Social Studio as formerly Radian6, which is why a Radian6 contract you signed years ago may today appear under a different name or not at all.

We could not find a Salesforce page that lists every legacy product code against the retired subscriptions, so we cannot tell you which of your lines the notice covers. What I can say is how to resolve it. Ask your account executive for a written list of active subscriptions, with product, edition, quantity and dates, and ask what happened to any listening line that ended before the retirement. If a Radian6 charge is still on an invoice, it either belongs to something else under an old label or it is an error, and both are worth correcting.

#Listening is metered, and that is the point

A seat price tells you who can log in. A listening licence usually has a second meter that tells you how much the tool will watch. Vendors choose from a handful, and you will see different ones in different quotes.

The right meter for you depends on the question you are asking. A business that monitors three brand names across a few markets is a topics story. A consumer brand that expects a viral moment is a volume story. A regulated business that must keep a record for years is a retention story. Write down which of those you are before you open a vendor's quote, because the same words, such as monitoring or listening, can describe very different allowances.

#What published prices show

Most vendors do not publish a full listening price list, so published figures are a starting point, not a budget. Sprout Social, as one example, lists keyword and location monitoring in its Standard plan at 199 US dollars per seat per month, with Professional at 299 and Advanced at 399, and an Advanced plan that adds sentiment in its inbox and message spike alerts. Its top tier is shown as custom pricing, described as "Designed for organizations with large-scale social media operations". Those figures were read on its pricing page on 13 October 2026.

Read that as a pattern. At entry level, listening arrives bundled with a seat and a modest allowance. As you need depth, such as sentiment, alerts and larger volumes, you climb tiers or move to a quote. A dedicated enterprise listening product is a different category again, and its pricing is nearly always negotiated, so we will not guess a figure for it.

A worked example, as list arithmetic and not a quote: four analysts on Standard at 199 dollars cost 796 dollars a month, or 9,552 dollars a year. The same four on Advanced at 399 cost 19,152 dollars a year. The difference is 9,600 dollars, and what it buys is a set of features such as sentiment, spike alerts and reporting. If you do not use them, you are paying for the tier gate.

#The Salesforce side of the licence

Listening matters to a business mainly when it produces action. Someone complains publicly, and a case should open. A prospect asks a question, and a lead should be created. Those records live in Salesforce, and the people who work them need seats. Sales Cloud is priced per user per month, with Starter Suite listed at 25 US dollars and Pro Suite at 100 US dollars, according to the Sales Cloud pricing page, and Service Cloud has its own ladder.

The Salesforce Ben article that reported the retirement also noted a partnership between Salesforce and Sprout Social, announced to help Salesforce customers manage their social presence through Sprout. That is a fact about the market, not an endorsement and not a price, and I mention it only because many former Social Studio customers will be offered it. If you are, ask for the integration to be priced as a line, and ask which Salesforce objects it writes to and whether any of them consume additional seats or credits.

#Historical data is a licence question too

Radian6 customers often hold years of collected posts, tags and reports. Whether you can keep them is a contract question, and it is one you should settle before the product is gone, not after. If the data is already inaccessible, you are choosing between rebuilding from a new start date and sourcing historical data from the platforms again at their own prices. If any of it is still available, export it now, in a structured form, and store it where your own team can open it.

Do not assume a new vendor will import old Radian6 data. Ask whether it can, in what format, up to what volume and at what cost. An import service priced separately from the licence is common, and it should be on its own row in the quote.

#How to right-size a listening licence

The mistake I see most is buying listening on ambition rather than evidence. A team imagines it will watch every competitor in every market and asks for a quote to match, then uses a fraction of it. Right-sizing works in four steps, and none needs a vendor's help.

First, write down the questions the business actually asks of social data in a normal month. Examples are how people are reacting to a launch, whether a service fault is trending and which complaints are about to reach a regulator. Each question becomes a query or a topic, and the list is usually shorter than expected.

Second, measure a baseline. Run those queries for a month on a free trial or an entry plan and record how many mentions each returns and how many a human reads. The ratio between collected and read mentions is a quiet indicator of waste. If your analysts read a small slice of what is collected, you can safely choose a smaller allowance or tighter queries.

Third, plan for the bad month. Listening volume is not smooth. A product fault, a viral post or a media story can multiply mentions within hours. Ask the vendor in writing what happens to the allowance in that case, whether collection pauses, whether you are billed for overage and whether there is a ceiling. A vendor that can answer in one clear sentence is easier to trust than one that refers you to a general terms page.

Fourth, decide who acts. A listening tool that nobody is assigned to respond to is an expensive dashboard. Count the people who will triage, the people who will respond, and the people who need to see a weekly summary. The first two groups need full seats. The third often needs only an exported report, which costs nothing.

#Three scenarios, three meters

It helps to see how the same product category prices differently by situation. These are illustrations of method, not forecasts, and none uses a figure that a vendor has not published.

A regional retailer with two brands. The need is steady: watch two brand names and a handful of product terms, and route complaints to customer care. This is a topics and seats problem. An entry plan with bundled keyword monitoring, a few seats and a Salesforce integration for cases will cover it, and the main risk is under-counting the social profiles that must be connected if the team also publishes.

A consumer brand with campaigns. The need is bursty. Volume spikes with each campaign, and the business wants alerts and sentiment. This is a volume and feature problem. A higher tier with spike alerts is justified, and the contract question is overage. Ask for a campaign calendar to be attached to the quote so the vendor knows when to expect the peaks.

A regulated business with a retention duty. The need is a record. Mentions about the business must be kept for a defined period and be retrievable. This is a retention problem, and the allowance that matters is how long collected data is stored and in what form it can be exported. A quote that prices volume well but retention badly is the wrong quote.

If you find yourself in two of these at once, price the dominant meter first and treat the other as an add-on to be negotiated, not an assumption.

#Data you collect and rules you inherit

Social listening collects public posts, and the platforms those posts come from set conditions on how the data may be stored and reused. Vendors differ in how they handle those conditions, and the differences show up in contract terms such as retention limits and deletion requirements. We have not read every platform's current terms for this page, so I make no claim about them here. What I can say is that the licence you sign should state plainly what data you may keep, for how long, and what you must delete when the term ends. If you plan to push mentions into Salesforce as records, check that the same conditions are acceptable once the data sits in your CRM, because your own retention and privacy obligations then apply to it.

For Australian organisations, that includes thinking about where the data is stored and who can access it. Ask where the vendor hosts collected data, and whether a copy leaves your region, before you write the answer into a procurement checklist.

#What to do this quarter

If you are still carrying a Radian6 or Social Studio line, do three things in order. Get the written subscription list from Salesforce. Decide, in one meeting, which listening questions the business really needs answered. Then request quotes from two or three vendors on the same stated meter, with the same volume assumptions, so the numbers can be set side by side. That sequence turns a retirement into a short procurement exercise instead of a scramble, and it keeps the licence cost visible as its own line rather than buried inside a larger marketing budget.

#Contract mechanics

Listening tools are usually sold on annual terms. Three clauses decide whether the contract is fair.

1. Allowance overage. Ask what happens when you exceed a volume or topic allowance, whether you are billed in arrears, and whether there is a cap.
2. Renewal uplift. Ask for the renewal price now. A low first-year price followed by a steep step is the usual structure.
3. Exit. Ask what you can export, in what format and for how long after the end of term.

#Comparing offers

#Where the other questions sit

How Radian6 came to Salesforce is on what happened to Radian6. Connecting listening to the CRM is on integrating Radian6 with Salesforce. Whether to move off whatever is left is on should I migrate from Radian6. Sprout's figures come from its pricing page, read on 13 October 2026, and every price here will change.