media-cloud-setup
Media Cloud setup for advertising sales management, audience segmentation, campaign management, revenue management, and cross-channel ad products. NOT for Salesforce Marketing Cloud (use marketing-cloud-account-setup). NOT for Data Cloud audience activation (use data-cloud-activation-patterns).
Best use case
media-cloud-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Media Cloud setup for advertising sales management, audience segmentation, campaign management, revenue management, and cross-channel ad products. NOT for Salesforce Marketing Cloud (use marketing-cloud-account-setup). NOT for Data Cloud audience activation (use data-cloud-activation-patterns).
Teams using media-cloud-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/media-cloud-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How media-cloud-setup Compares
| Feature / Agent | media-cloud-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Media Cloud setup for advertising sales management, audience segmentation, campaign management, revenue management, and cross-channel ad products. NOT for Salesforce Marketing Cloud (use marketing-cloud-account-setup). NOT for Data Cloud audience activation (use data-cloud-activation-patterns).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Media Cloud Setup Activate when configuring Salesforce Media Cloud for a publisher, broadcaster, streaming service, or ad sales organization. Media Cloud is the industry bundle for advertising sales management — deal-to-cash for media — distinct from Marketing Cloud (marketer outbound) and Data Cloud (CDP / audience store). ## Before Starting - **Distinguish Media Cloud from Marketing Cloud.** Media Cloud is ad-sales revenue-facing (publisher → advertiser). Marketing Cloud is outbound messaging. Practitioners routinely confuse the two; clarify up front. - **Map the ad product catalog.** Digital display, connected TV, streaming audio, linear spot, print, out-of-home, sponsorships each have different inventory, delivery, and pricing rules. Catalog design is the hardest part of Media Cloud setup. - **Identify the ad-server integration.** Most publishers have GAM, FreeWheel, Adswizz, or a proprietary ad server. Media Cloud expects to push order data into that system and pull back delivery metrics. ## Core Concepts ### Deal → Contract → Placement → Delivery Media Cloud extends Revenue Cloud with media-specific objects. `MediaDeal` holds the negotiated scope. `MediaContract` is signed and versioned. `MediaPlacement` is the buy — a line item per ad product, flight, and target audience. `DeliveryActual` records served impressions from the ad server. ### Audience segmentation and targeting Audiences come from Data Cloud or a DMP. Media Cloud references audience segments on each Placement. Audience fill rates and forecast availability are live calculations against the ad-server's inventory, not static lookups. ### Revenue recognition per media type Recognition rules differ by ad product: digital is delivery-based (ASC 606 performance obligation satisfied as impressions serve), linear is broadcast-based, print is issue-date-based. Media Cloud Revenue Management models these with product-specific rules. ## Common Patterns ### Pattern: Digital display order from deal to invoice `MediaDeal` negotiated → `MediaContract` signed → `MediaPlacement` created per flight / audience / creative → order pushed to ad server → daily delivery pulls back via integration → `DeliveryActual` aggregates → invoice generated from delivered impressions at contracted CPM. ### Pattern: Linear spot avail and rate card Rate cards are matrix: daypart × program × week. Forecasting avails uses Programmatic Scheduler or integration with a broadcast traffic system. Deals reserve spots; confirmation locks inventory. ### Pattern: Cross-channel bundled sponsorship One deal spans digital + linear + streaming. A parent Contract; child Placements per channel. Revenue recognition rules differ per child — the Contract aggregates but each Placement runs its own recognition rule. ## Decision Guidance | Situation | Recommended Approach | Reason | |---|---|---| | Ad inventory forecasting | Ad-server integration with cached availability | Live inventory source of truth | | Audience targeting | Data Cloud + Media Cloud Placement reference | Single audience catalog | | Rate card management | Media Cloud rate cards per product | Shipped versioning | | Revenue recognition | Media Cloud Revenue Management | Handles product-specific rules | | Multi-channel bundle | One Contract, multiple Placements | Aggregated deal, per-channel rec | ## Recommended Workflow 1. Confirm Media Cloud license, Revenue Cloud dependency, and ad-server integration path. 2. Define the ad product catalog per media type (digital, linear, print, OOH, streaming). 3. Build rate cards for each product with appropriate versioning and effective-dating. 4. Configure Deal → Contract → Placement records; validate with a sample flight end-to-end. 5. Integrate with ad server: order push, daily delivery pull, reconciliation job. 6. Configure revenue recognition rules per product family; validate with accounting. 7. Build a campaign performance dashboard; sign off with sales, ops, and finance. ## Review Checklist - [ ] Ad product catalog covers every media type actually sold - [ ] Rate cards versioned with effective dates - [ ] Ad server integration round-trips a flight end-to-end - [ ] Revenue recognition rules validated by finance - [ ] Audience segments fed from a single source (Data Cloud or DMP) - [ ] Cross-channel bundles tested (digital + linear + streaming) - [ ] Deal pipeline visible to sales leadership in a dashboard ## Salesforce-Specific Gotchas 1. **Ad server delivery volumes are huge.** Loading raw impression logs into Salesforce kills storage; aggregate upstream and sync daily rollups only. 2. **Audience size forecasts expire fast.** A Placement forecast based on yesterday's audience can mislead pricing; refresh on save. 3. **Rate card versioning is not retroactive.** New rate card versions apply to new Placements only; in-flight contracts keep their original rates. ## Output Artifacts | Artifact | Description | |---|---| | Media Cloud activation plan | License, package, and feature toggle order | | Ad product catalog | Product-level rate/inventory/delivery rules | | Ad-server integration spec | Endpoints, payload, reconciliation schedule | | Revenue recognition rulebook | Per-product recognition rule set | ## Related Skills - `admin/revenue-cloud-cpq-setup` — underlying Revenue Cloud - `integration/platform-events-basics` — delivery-sync backbone - `data/data-cloud-activation-patterns` — audience source
Related Skills
shield-kms-byok-setup
Configure Shield Platform Encryption with customer-supplied (BYOK) or customer-held (Cache-Only Key Service) tenant secrets, rotate them, and recover. NOT for Classic Encryption or field masking.
experience-cloud-security
Use when configuring access controls, sharing, or site security for authenticated or guest Experience Cloud (community) users: external OWD, Sharing Sets, Share Groups, CSP, clickjack protection, guest user record access. NOT for internal sharing model configuration (use sharing-and-visibility).
headless-experience-cloud
Use when building custom frontends (React, Vue, mobile, static sites) that consume Salesforce CMS content via the Connect REST API headless delivery endpoint. Triggers: 'headless Salesforce CMS', 'deliver CMS content to external frontend', 'React app Salesforce content API', 'custom frontend Experience Cloud data', 'CMS delivery channel API'. NOT for standard Experience Builder site development. NOT for CMS Connect (3rd-party CMS federation into Experience Builder). NOT for Experience Cloud LWC components rendered inside a site.
experience-cloud-search-customization
Use this skill when configuring or extending search on an Experience Cloud site — covering Search Manager scope configuration, LWR vs Aura search component selection, federated search setup, guest user search access, and custom search result components. NOT for SOSL/SOQL query development. NOT for internal Salesforce global search or Einstein Search for agents.
experience-cloud-multi-idp-sso
Use this skill when configuring multiple identity providers (OIDC and/or SAML) on a single Experience Cloud site or across tenant-specific portals in the same org — covering auth provider registration, Start SSO URL routing, Federation ID mapping, RegistrationHandler implementation, and simultaneous SP+IdP topology. Trigger keywords: multiple identity providers Experience Cloud, multi-tenant SSO community portal, vendor and citizen portal same site, OIDC SAML both on login page, tenant-specific login routing community. NOT for internal Salesforce employee SSO configuration. NOT for single auth provider setups — see experience-cloud-authentication for basic SSO.
experience-cloud-lwc-components
Use when building custom LWC components for Experience Cloud (Experience Builder sites, LWR portals, Aura-based communities). Covers community context imports, guest user Apex access patterns, navigation API differences between LWR and Aura, and JS-meta.xml target configuration for Experience Builder exposure. NOT for internal LWC components deployed to Lightning App Builder or standard record pages (see lwc/lwc-development). NOT for Aura community components. Trigger keywords: build LWC for Experience Cloud, custom component community portal LWC, guest user LWC component, community context import salesforce, lightningCommunity target, @salesforce/community, guest Apex.
experience-cloud-authentication
Use when building custom login pages, social SSO flows, self-registration flows, or passwordless OTP login for Experience Cloud (community) sites. Trigger keywords: custom login page Experience Cloud, social SSO community portal, passwordless login Experience Cloud, self-registration custom flow, headless authentication community, auth provider OIDC SAML site. NOT for internal SSO configuration (use identity/sso skills). NOT for standard username/password authentication with no customization.
experience-cloud-api-access
Use this skill when configuring or troubleshooting API access for Experience Cloud external users and guest users: guest user Apex data access, Customer Community Plus or Partner Community REST/SOAP API access, external user OAuth scopes, and sharing enforcement on API responses. Trigger keywords: Experience Cloud API access external user, community user REST API, guest user API limits, Customer Community API permissions, external user OAuth. NOT for internal Salesforce API authentication, non-community OAuth flows, or internal user API security.
slack-salesforce-integration-setup
Use this skill when setting up or troubleshooting the Salesforce for Slack managed app — including connecting a Salesforce org to a Slack workspace, configuring the three-party admin handshake, linking Slack channels to Salesforce records, enabling record preview sharing, and managing org-level limits. Triggers on: Salesforce for Slack app not connecting, Slack org connection setup, Salesforce record sharing in Slack, Slack workspace admin approval, connecting Salesforce to Slack. NOT for building custom Slack apps or Slack bots (separate development platform), not for Slack Workflow Builder Salesforce connector (use slack-workflow-builder skill), not for Flow-based Slack messaging (use flow-for-slack skill).
salesforce-maps-setup
Use when configuring Salesforce Maps (formerly MapAnything) — territory planning, route optimization, live tracking, geo-grid visualizations, and check-in/check-out workflows for Sales or Service field reps not on Field Service. Covers package installation order (Maps + Maps Advanced + Maps Routing/Live Tracking add-ons), the MapsTerritoryPlan / MapsAdvancedRoute / MapsLayer object family, base-data syncs (Geocoding and Routing services), and integration with Sales and Service Cloud records. Triggers: 'Salesforce Maps setup', 'MapAnything migration', 'territory planning by polygon', 'route optimization for sales reps', 'live tracking field reps', 'plot accounts on a map', 'check-in to the closest account'. NOT for Field Service Lightning territory and scheduling (use admin/fsl-scheduling-optimization-design and data/fsl-territory-data-setup) — Maps and FSL are different products. NOT for Consumer Goods Cloud retail visit planning (use admin/consumer-goods-cloud-setup) — RoutePlan/Visit objects are CG-specific. NOT for Tableau / CRM Analytics geo charts.
private-connect-setup
Configure Private Connect between Salesforce and AWS/Azure for traffic to stay on private networks. NOT for standard internet callouts.
net-zero-cloud-setup
Use this skill when configuring Salesforce Net Zero Cloud — including Scope 1/2/3 emission source modeling via the StnryAssetCrbnFtprnt / VehicleAssetCrbnFtprnt / Scope3CrbnFtprnt object families, emission factor library setup (EmssnFctr / EmssnFctrSet), DPE-driven carbon calculation jobs, supplier engagement scoring, and CSRD / ESRS / TCFD disclosure pack mapping. Triggers on: Net Zero Cloud setup, Sustainability Cloud carbon accounting, Scope 1 2 3 emissions Salesforce, emission factor library, supplier engagement Net Zero, ESG disclosure pack mapping. NOT for ESG content scoring (use Marketing Cloud), NOT for general financial reporting (use Accounting Subledger), NOT for energy-only utility billing (use Energy & Utilities Cloud).