本文へ移動
cccskills
無料GitHub で公開

media-cloud-setup

Media Cloud setup for advertising sales management, audience segmentation, campaign management, revenue management, and cross-channel ad products. NOT for Marketing Cloud setup — use admin/marketing-cloud-engagement-setup. NOT for Data Cloud segments — use admin/data-cloud-segmentation.

PranavNagrecha/AwesomeSalesforceSkills
インストール方法を見る

含まれるファイル（7）

  • SKILL.md8.1 KB
  • references/examples.md6.9 KB
  • references/gotchas.md5.9 KB
  • references/llm-anti-patterns.md3.2 KB
  • references/well-architected.md5.5 KB
  • scripts/check_media_cloud_setup.py3.1 KB
  • templates/media-cloud-setup-template.md621 B

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

Opportunity → Quote → Order line

Media Cloud Advertising Sales Management (ASM) ships standard objects, all prefixed Ad. AdOpportunity "Represents ad sales specific details of an advertisement campaign opportunity," with AdOpportunityLineItem as "a line item in an advertisement opportunity." AdQuote "Represents the details of a quote for an advertisement campaign" and AdQuoteLine "the details of a line item in an advertisement campaign quote." On the order side, AdOrderItem "Represents the advertisement campaign specific details of an ad order item."

The buy's detail hangs off the line as a family of junctions and child records rather than fields — for orders: AdOrderItemAdSpaceSpec, AdOrderItemCreativeSizeType, AdOrderItemDeliveryFrequency ("the frequency at which an ad order item must be served"), AdOrderItemDeliverySchedule ("the time period and days for serving an ad order item"), AdOrderItemPrintIssue, AdOrderItemUnitsSplit, AdOrderLineAdTarget, AdOrderLineHiatus, AdOrderLineTargetExpression, AdOrderLineTargetValue. Each has an AdQuoteLine… mirror on the quote side.

Audience segmentation and targeting

Audiences come from Data Cloud or a DMP. Targeting is expressed on the line itself: AdOrderLineAdTarget "Represents selections made by users against a specific Ad Order Line item for a particular category," AdOrderLineTargetExpression "the expression that decides the targeting criteria for an ad order line," and AdOrderLineTargetValue the values within it. 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

AdOpportunity negotiated → AdQuote and AdQuoteLine priced → AdOrderItem per flight, with AdOrderItemDeliverySchedule and AdOrderItemDeliveryFrequency setting when it serves and AdOrderItemCreativeSizeType fixing the creative → order pushed to the ad server through the AdTech Integration API → daily delivery pulled back → 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 single AdQuote carries an AdQuoteLine per channel, each with its own AdQuoteMediaTypeProperty ("information associated with the media type for an ad quote"). Revenue recognition rules differ per line — the quote aggregates the deal, but each line runs its own recognition rule.

Decision Guidance

SituationRecommended ApproachReason
Ad inventory forecastingAd-server integration with cached availabilityLive inventory source of truth
Audience targetingData Cloud + AdOrderLineAdTarget / target expressionSingle audience catalog
Rate card managementMedia Cloud rate cards per productShipped versioning
Revenue recognitionMedia Cloud Revenue ManagementHandles product-specific rules
Multi-channel bundleOne AdQuote, one AdQuoteLine per channelAggregated 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 AdOpportunity → AdQuote/AdQuoteLine → AdOrderItem 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. An AdQuoteLine 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 AdQuoteLine records only; in-flight orders keep their original rates.

Output Artifacts

ArtifactDescription
Media Cloud activation planLicense, package, and feature toggle order
Ad product catalogProduct-level rate/inventory/delivery rules
Ad-server integration specEndpoints, payload, reconciliation schedule
Revenue recognition rulebookPer-product recognition rule set

Related Skills

  • architect/revenue-cloud-architecture — underlying Revenue Cloud
  • integration/platform-events-integration — delivery-sync backbone
  • admin/data-cloud-segmentation — audience source

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

acceptance-criteria-given-when-then

無料

Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords: given when then, gherkin, behavior driven AC, test first acceptance criteria, scenario outline, BDD acceptance criteria. NOT for the user-story format itself (use admin/user-story-writing-for-salesforce). NOT for UAT script writing (use admin/uat-test-case-design). NOT for Apex test method generation (use agents/test-class-generator). NOT for high-level UAT planning (use admin/uat-and-acceptance-criteria). More triggers: acceptance criteria record, ac_id, req_id on a criterion, artefact under test, negative case for a rule-type requirement, no-match fall-through criterion, oracle for a Then clause, test type apex flow manual, criteria linter, check_ac_format.py, --manifest-dir.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

activity-and-task-patterns

無料

Task and Event objects: polymorphic WhatId/WhoId, Activity object model, ActivityHistory vs OpenActivity, activity timeline customization, bulk task creation, Einstein Activity Capture boundaries. NOT for turning on EAC or calendar sync — use admin/einstein-activity-capture-setup. NOT for Email-to-Case — use admin/case-management-setup. Covers ActivitiesSettings metadata, enableActivities, shared Task/Event custom fields and FLS, TaskStatus value sets, Shared Activities and TaskRelation/EventRelation, recurring and child activities, and partial-success bulk DML on Task.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

agent-action-error-handling

無料

Design Invocable Apex actions that return deterministic, agent-friendly errors instead of surfacing raw exceptions to the LLM. NOT for authoring the action itself — @InvocableMethod schema, labels, security context — use agentforce/custom-agent-actions-apex. NOT for the Apex tests that force each error branch — use agentforce/agent-action-unit-tests.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

agent-action-input-slot-extraction

無料

Use when designing how an Agentforce agent extracts structured input parameters (slots) from a user's natural-language utterance to invoke an action. Triggers: 'agent extract date from user', 'agent action argument extraction', 'agentforce slot filling', 'agent invocable input mapping', 'agent fails to fill required parameter'. NOT for action authoring (use agentforce/agent-actions) or for prompt-template variable binding (use agentforce/prompt-builder-templates).

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

agent-action-unit-tests

無料

Apex test patterns for @InvocableMethod agent actions: per-reason-code branch coverage, bulk safety, callout mocking, deterministic assertions. NOT for testing whether the agent routes to the right topic or answers well — use agentforce/agent-testing-and-evaluation. NOT for designing the error envelope the tests assert on — use agentforce/agent-action-error-handling.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

agent-actions

無料

Designing or reviewing Agentforce actions: Flow actions, Apex invocable actions, prompt-template actions, action naming, input and output contracts, confirmation requirements, and safe error behavior. Triggers: 'agent actions', 'build an agent that can look up an order', 'make the agent able to check order status', 'give the agent a capability', 'agent that can retrieve a record', 'flow action for agent', 'agent invocable action', 'action schema design'. NOT for writing the Apex class itself — use agentforce/custom-agent-actions-apex. NOT for the reason_code error envelope that stops an agent retry loop — use agentforce/agent-action-error-handling.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

PranavNagrecha のスキルをすべて見る

このスキルの問題を報告する