Media CloudStrategyPublishers & media

Why Media Cloud "on Core" changes the game for traditional media

Clément Richard · Founder, Amplee • • 9 min read

Traditional media has a tooling problem more than a demand problem: ad sales in one specialized system, subscribers in another, the sales CRM on the side, billing somewhere else again - and spreadsheets to stitch the pieces back together at every month-end. Salesforce itself lists the pains it targets with Media Cloud: silos between departments, error-prone manual processes, coordination of multiple third-party vendors, lost orders, poorly controlled discounts. What changes with Media Cloud (Agentforce Media) comes down to one phrase: "on Core". The product does not live next to the CRM, it is the CRM. Here is why that is a game changer - and for which industries.

01"On Core": what it means in practice

  • Standard objects, not a separate package. The media quote is linked to the Salesforce quote, the media line to the quote line, the media order line to the order line - without a custom field. One data model, from opportunity to order; the invoice, for its part, belongs to Revenue Cloud, on the same platform.
  • Sales Cloud or Service Cloud included in the license. Your ad sales reps and your subscriber service work in the same tool as the rest of the company, with the same reports, the same security, the same Flow automations.
  • A unified data foundation. The media model (opportunity, quote, ad space, targeting category…) is recognized by Data 360, which grounds the agents without copying the data. Data 360 remains a separately licensed product - but it is the same foundation as for the rest of Salesforce.
  • Audience-first rather than inventory-first. This is one of the five shifts Salesforce describes for the industry: you no longer sell a space, you sell an audience - and that assumes customer data and advertising data live in the same place.
  • Industrial-grade tooling around it: Industries order management (decomposition, orchestration to the ad servers), native contracts (insertion orders from templates), OmniStudio now available in a native version with a migration assistant from the managed package.
  • Agentforce for Media, for what it is: one standard subagent delivered today - ad proposal management (proposal, pitch, opportunity summary) - as an add-on. Useful; not yet autonomous.
The real gain is not one more feature. It is the end of reconciliation.

02Press and publishers: ad sales, subscribers, a single customer

The historical problem, in our reading: print ad sales, digital ad sales and subscriber management in three tools; an advertiser who is also a subscriber is never recognized as such; insertion orders still in PDF. What native changes: print and digital on a single media plan; subscribers handled by the SLM side within the same CRM; a shared customer master. To scope: the inventory model (direct or programmatic), the articulation with Revenue Cloud for invoicing, and the actual scope of the subscription side.

03TV and radio: linear joins digital

The historical problem: proprietary linear traffic systems, separate from the digital tools; two sales forces, two plans, two reconciliations. What native changes: media planning for linear products is native since Summer '26, with spot price calculation; linear ad servers (WideOrbit, Operative IBMS, Mediaocean) can be integrated. To scope: no linear connector ships out of the box - only Google Ad Manager does, on the digital side - so the integration has to be costed; multi-ad-server inventory checks are validated in a demo, not on a brochure.

04Media agencies: getting out of multi-publisher spreadsheets

The historical problem: plans in spreadsheets, manual reconciliation across publishers, client visibility rebuilt by hand. What native changes: the agency is a native ASM persona, with its account-advertiser-brand relationships; the media plan becomes a shared, versioned object linked to the quote. To scope, honestly: ASM is designed for the sell side (the publisher who sells). Purely buy-side use is an adaptation, not the core of the product - we say so before the project, not after.

05B2C apps and subscriptions: churn inside the CRM

The historical problem: churn managed outside the CRM, in the payment tool or a dashboard; limited self-care; customer service discovering the subscriber without their history. What native changes: three interfaces delivered (self-care portal, 360° agent console, storefront), subscriber lifetime value as the pivotal metric, gifts and win-back, promotions with a cart and fixed-term subscriptions (Summer '26). To scope: Salesforce describes SLM for media; extending it to a non-media B2C app is our reading, relevant but to be validated; and the native billing scope has to be checked against Revenue Cloud Billing.

06Retail media: monetizing the retailer without reinventing ad sales

The historical problem: valuable retailer data, but no structured ad sales tooling; sponsorship deals negotiated by email, share of voice tracked by hand. What native changes: Salesforce explicitly cites retail media networks among its targets; direct inventory (sponsorship, share of voice) and programmatic coexist; category targeting is a standard object; everything is tied into quote-to-cash. To scope: the actual availability of the inventory calendar in your org, the lack of a native "retail banner / category" dimension on the ad space specification, and the integration of your ad server if it is not Google Ad Manager.

07Adtech: partner, not customer

Ad servers, measurement solutions, data providers: Salesforce classifies them as third-party vendors in the ecosystem, not as the product's target. For them, "on Core" means a standardized integration point - OmniStudio integration procedures or MuleSoft, named credentials - and a question to settle early: does the ad server expose a synchronous availability API? If not, the "real-time check" promised in the demo becomes a project of its own.

0custom fields between the media plan and the Salesforce order
1CRM (Sales or Service) included in the license
1standard AI subagent delivered to date: ad proposals

08What we take away

The game changer is not the feature list: it is that a media group can finally fit ad sales, subscribers, sales and billing into a single platform, with standard objects that a Salesforce administrator understands. We did it for an international media group, across more than twenty countries: ad sales, quotes and orders in a single platform. The price to pay is serious scoping: inventory model, articulation with Revenue Cloud, costed ad server integrations - and an AI presented for what it is today. To lay the groundwork: Media Cloud: what is it?. To scope your case: our Media Cloud expertise or 30 minutes with us.

Go further

Our Media Cloud expertise

Scope, method, references: the expertise page details how we put this subject into practice for our clients.