01 Facts & context
Microsoft’s proposition for media curation
In a September 10, 2026 article, Microsoft Advertising describes curation as packaging audience data and supply-chain signals with advertising inventory. Its Curate product combines capabilities for creating offers, reaching buyers, reporting and controlling supply paths. The article argues that organizations with proprietary data, content or specialist media expertise can build a media offering through shared infrastructure. This is a platform’s account of a commercial opportunity, not an independent assessment of the profit available to every organization that owns data.
The article also cites an operational case in which line items were reduced from 250 to 14, together with performance comparisons from data-enriched private marketplaces. These are distinct observations with different sources and comparison groups. Fewer line items do not alone establish equivalent savings in labor, and higher engagement does not directly measure incremental sales or profit. The questions for a prospective curator concern what it contributes, what a buyer can verify and who remains responsible after the deal is configured.
Two IAB Tech Lab standards add complementary perspectives. Seller and supply-chain transparency help identify participants, while the Deals API structures information about agreements. Neither validates the commercial value of an audience package by itself. This research combines the platform proposition with those operational boundaries to examine how a media product can become understandable, deliverable and testable.
02 GSP analysis
Differentiated data does not remove supply-path verification
Microsoft argues that proprietary data and premium inventory can form differentiated media products. IAB’s sellers.json and SupplyChain standards answer another question: which sellers and intermediaries handled the impression? A buyer may accept a package’s audience logic while still requiring evidence of inventory origin, authorization and participating entities. The two assessments complement each other. A coherent theme does not demonstrate that all unnecessary intermediaries have been removed.
GSP separates audience value from path value. Audience value concerns how labels are created, refreshed and related to a purchase context. Path value concerns seller identity, resale and traceable delivery. Transparency does not guarantee a low price, and a low price does not guarantee the intended audience. Explaining both lets a buyer understand whether it is paying for insight, inventory quality, operational service or transaction convenience. It also gives the curator a clearer service boundary than an undifferentiated claim about selected traffic, making subsequent performance discussions more accountable.
03 GSP analysis
Static deal terms still need reconciliation with live delivery
Deals API version 1 standardizes high-level deal information, reduces manual entry and identifies parties involved in curation and sales. It does not replace real-time bidding or provide a complete negotiation and revision system. Implementers are told to compare deal conditions with actual requests. This adds an operating boundary to the platform narrative: connecting an interface transmits a promise; it does not prove fulfillment.
The operating record should connect product description, deal configuration, impression delivery and outcome review. If a package promises a content environment or audience condition, acceptance should reference observable fields. If it promises optimization services, record the reasoning and cadence of adjustments rather than delivering only a click-through report. GSP sees durable revenue in explainable differentiation and repeatable service, rather than additional transaction complexity. Buyers should compare packages on consistent net outcomes and account for overlapping reach and attribution. That makes it possible to distinguish a useful service from a package that merely reorganizes existing impressions.
How three perspectives inform the decision
When proprietary data becomes a media package, how can buyers and sellers identify its value?
| Measure | Documented observation | Scope and implication |
|---|---|---|
| about.ads.microsoft.com | Curate packages data and inventory as a media product. | Separate the value of data, inventory and service. |
| IAB Tech Lab | sellers.json and SupplyChain identify selling-chain participants. | Audience differentiation still needs supply-path transparency. |
| IAB Tech Lab | Deals API communicates static terms rather than validating live requests. | Continuously reconcile interface promises with delivery. |
Microsoft Curate describes packaging capabilities, while IAB supply-chain standards and Deals API clarify identities and terms. Commercial evaluation must reconcile the package promise with actual delivery.
- [1] Turn Proprietary Assets Into Revenue | Microsoft Advertising ↗What curators need; smarter approach; performance examples · Accessed
- [2] sellers.json and OpenRTB SupplyChain transparency ↗About sellers.json; SupplyChain object; buyer responsibilities · Accessed
- [3] Deals API Specification v1 ↗Core goals; What it is; What it is not · Accessed
04 GSP analysis
Build, partner or use a platform
An organization can build an end-to-end media operation, use an established curation platform, or retain selected responsibilities while outsourcing transaction infrastructure. These choices distribute control and cost differently. Building internally requires technical maintenance, buyer access, operating support and a way to manage changing requirements. Using a platform may reduce initial integration work while creating dependencies on its pricing, interfaces and commercial relationships. A hybrid arrangement can preserve an important capability without attempting to reproduce every layer.
Start with the asset and the demand it serves. A distinctive content environment or well-defined audience relationship may give a buyer a reason to choose the offering. A broadly available segment with an unfamiliar label may provide little differentiation. Ownership of data does not establish permission for every use, and rarity does not establish willingness to pay. Those questions need separate evidence before the financial model assumes a premium.
Next compare plausible volumes with continuing costs, including support and changes. There is no universal revenue threshold at which building becomes preferable. A small operation may use shared infrastructure to learn, while a specialized one may retain control for reasons beyond immediate margin. The decision should state which capabilities must remain internal, which service is purchased and what would trigger a reassessment. This creates a more useful basis for investment than a general preference for either owning technology or launching quickly.
05 GSP analysis
How curation moves decisions upstream
Curation can move some selection work earlier in the purchasing process. A provider may define audience conditions, content context, inventory criteria and service commitments before the buyer activates a deal. That can reduce repeated evaluation, but it does not mean open-market buyers have no pre-bid controls. The relevant comparison is between specified operating processes, not a simplified contrast in which one route is intelligent and the other is unfiltered.
The package also reallocates responsibility. If the provider claims a particular content environment, it should be able to show how delivery is checked. If it offers an audience signal, it should explain what the signal means, how it is maintained and what it does not reveal. If it promises optimization, the buyer needs to understand which actions are included. A sales outcome requires a different evidence standard from delivery to an agreed environment; the two should not be treated as interchangeable product features.
For example, a publisher could propose a contextual package around a defined subject and support it with a clear inventory list and reporting. This illustrative offer makes a more limited promise than guaranteed purchase intent. Its value would still need testing against an appropriate alternative. Stronger wording should follow stronger evidence, rather than being used to compensate for an offer whose contribution has not yet been measured.
06 GSP analysis
From buying impressions to assessing a package
The buyer’s task shifts partly from adjusting individual campaign settings to evaluating an offer. A useful description explains the audience or context, inventory scope, participating entities, measurement and included service. It also explains what can change after activation. Buyers should be able to distinguish a new source of useful information from a repackaging of inventory they already access elsewhere. Clear descriptions reduce evaluation work while making unsupported claims easier to identify.
A buyer can ask four practical questions. What qualifies an impression for the package? Which records support the claimed quality? How will delivery and outcomes be assessed? What happens if the offer performs differently from its description? The appropriate answers depend on the product. A contextual package, a first-party audience offer and a managed optimization service should not all be sold using the same vague phrase about premium reach.
A sensible journey moves from evaluation to a limited activation and then to a decision about continuation. The trial should establish whether configuration matches delivery and whether the proposed distinction is useful. A polished report is insufficient if the buyer cannot reconcile it with agreed conditions. Conversely, a clearly explained limitation can improve trust by preventing an unsuitable purchase. The curator’s job is to help the buyer make a defensible choice, not merely to remove every objection until a deal is activated.
07 GSP analysis
Assign data, pricing and outcome responsibilities
Curation crosses responsibilities for data, inventory, commercial terms, implementation and buyer support. A platform can expose controls, but people still decide which assets may be offered and which promises can be fulfilled. Without explicit ownership, a seller can describe a capability before the data or operations team has confirmed it. The resulting dispute then appears as a technical problem even though its origin is an undefined commitment.
GSP proposes separating asset eligibility, product design and delivery accountability. The asset owner documents available signals and applicable conditions. The product or monetization owner defines the offer, pricing logic and service boundary. Operations and measurement owners verify implementation, investigate exceptions and explain results to the buyer. These roles may overlap in a small organization, but the decisions should remain distinguishable. Commercial negotiation should not silently expand an approved data use or change a quality definition.
The handoff should include an offer version, inventory scope, permitted settings, reporting definitions and a contact for exceptions. Changes should be visible to the parties affected. For example, adding a new supply source can alter what the buyer believes it purchased even if the deal identifier stays the same. The operating question is therefore not simply who owns the platform account, but who can authorize changes and who verifies that the delivered product still matches the agreement.
08 GSP analysis
Costs and alternative explanations
The economic comparison must include continuing costs as well as launch speed. Shared infrastructure may charge platform or transaction fees, while the curator still pays for integration, product maintenance, support and measurement. Internal infrastructure has its own recurring engineering and operational costs. Neither route guarantees a larger margin. A useful model states the assumptions about volume, buyer retention and servicing effort, then shows which assumptions matter most to the decision.
Performance comparisons also need a credible alternative. Buyers using private marketplaces may differ from open-market buyers in budget, optimization skill or inventory selection. Better engagement could reflect those differences rather than the packaging layer. An observed difference is still informative, but it cannot be assigned automatically to the curator’s contribution. The platform article offers hypotheses to examine; it does not establish a universal effect for every offer sold through the product.
A local comparison should keep buyer, objective, period and other important conditions as similar as feasible. Then identify what changes with the curated offer. If inventory and data both change, the result describes the combined package rather than an isolated data benefit. If costs change too, report the net comparison. This discipline lets the provider explain why a buyer should continue, including situations where a narrower, simpler offer creates more value than a complex package with a larger headline premium.
09 Suggested actions
Begin with a bounded media package
Begin with an inventory of usable assets and a specific buyer problem. Record the data or context available, the conditions attached to it, the supply that can actually be delivered and the people who can support the offer. Then select a limited use case. Attempting to cover every buyer and format before confirming the first product can multiply configuration work without revealing whether demand exists.
The initial offer should state eligibility, inventory scope, participating providers, measurement and the procedure for handling discrepancies. Configure a limited activation and verify that requests and delivery correspond to the agreed conditions. The Deals API can help communicate deal information, but operational reconciliation still matters. A transmitted condition is an instruction or description; evidence that it was fulfilled comes from checking the relevant records and resolving mismatches.
Use the first review to answer three questions: did the buyer understand the product, did delivery match it, and did the distinction improve a relevant result after costs? Record support effort and corrections alongside performance. Only then consider more offers or additional buyer access. This sequence may produce less immediate volume, but it provides evidence about what should be replicated. Expansion without that evidence can spread an unclear promise across more accounts and make later corrections harder to coordinate.
10 Suggested actions
Measure commercial quality with a credible comparison
A balanced review covers commercial performance, buyer value and operating reliability. Commercial measures include repeat purchase, net revenue after defined fees and the cost of support. Buyer-value measures depend on the original question: a delivery-quality objective differs from an incremental-sales objective. Reliability measures include configuration time, discrepancies, resolution speed and the stability of definitions. An increase in one category should not conceal deterioration in another.
Where feasible, compare equivalent eligible groups within the same buying context. Random assignment can strengthen an incremental claim; matched or before-and-after observations require additional assumptions. Historical comparison alone cannot remove seasonal changes, budget shifts or different inventory. A curator does not need to promise a universal experimental design, but should explain what its chosen method can establish and where uncertainty remains. An inconclusive test should remain inconclusive rather than being replaced by an industry-average uplift.
The result may show that context or inventory quality contributes more than the proposed data signal. That is useful information for redesigning the offer and its price. Tools that accelerate reporting can make such investigation easier, but they cannot choose the right counterfactual or validate a causal conclusion automatically. Accountability remains with the people defining the question, checking the data and deciding how the finding should change the product sold to buyers.
From interpretation to a testable action
GSP analysis: define conditions, then advance on observed results
- 01
Define product value
Document data origins, inventory conditions and service scope. Each premium should correspond to explainable work.
- 02
Verify participants
Reconcile authorized sellers with supply-chain nodes. Record unknown or duplicate paths.
- 03
Validate delivery
Connect configured terms to delivery logs and net outcomes. Observe fulfillment of conditions and overlapping reach.
How much differentiation remains if proprietary data is removed?
- [1] Turn Proprietary Assets Into Revenue | Microsoft Advertising ↗What curators need; smarter approach; performance examples · Accessed
- [2] sellers.json and OpenRTB SupplyChain transparency ↗About sellers.json; SupplyChain object; buyer responsibilities · Accessed
- [3] Deals API Specification v1 ↗Core goals; What it is; What it is not · Accessed
11 Suggested actions
Conditions for proceeding or changing direction
Curation is suitable when an organization can identify a useful difference, support the intended asset use and operate the product continuously. A large dataset without a clear buyer question may not form a viable offering. A strong content environment without dependable delivery or support may also struggle. These conditions should be checked separately so that a failed pilot produces a specific lesson rather than a broad verdict that the entire category works or does not work.
Adjustment should follow the observed constraint. If buyers misunderstand the package, simplify the explanation and scope. If the distinction cannot be measured, narrow the promise and improve the comparison. If supply changes disrupt delivery, examine provider selection and reconciliation. If recurring fees or support effort change the economics, reconsider the infrastructure arrangement. Discounting alone will not resolve an offer whose contribution remains unclear, and expansion can worsen a service problem before it improves revenue.
The durable opportunity is to combine assets and service into a product whose contribution can be explained repeatedly. Seller transparency, structured deal information and local outcome evidence each support a different part of that task. None replaces the others. GSP’s conclusion is therefore conditional: curation can create a business when the promise, delivery and evidence remain aligned. It is not an automatic route from owning information to collecting a sustainable premium, and the operating model must be revised as buyer needs and available supply change.
THE EVIDENCE
Grounding the argument in evidence.
What the source reports
Curate packages data and inventory as a media product.
Separate the value of data, inventory and service.
What the source reports
sellers.json and SupplyChain identify selling-chain participants.
Audience differentiation still needs supply-path transparency.
What the source reports
Deals API communicates static terms rather than validating live requests.
Continuously reconcile interface promises with delivery.
DECISION POINTS
From understanding to testable action.
Define product value
Document data origins, inventory conditions and service scope.
Each premium should correspond to explainable work.
Verify participants
Reconcile authorized sellers with supply-chain nodes.
Record unknown or duplicate paths.
Validate delivery
Connect configured terms to delivery logs and net outcomes.
Observe fulfillment of conditions and overlapping reach.
QUESTIONS TO EXPLORE
What still needs to be established?
- How much differentiation remains if proprietary data is removed?
- Can the buyer trace the complete chain from package terms to impressions and outcomes?
Research sources
Synthesized from original reporting, institutional materials and research. Source observations, GSP interpretation and proposed actions are identified separately.
- Turn Proprietary Assets Into Revenue | Microsoft Advertising ↗about.ads.microsoft.com · What curators need; smarter approach; performance examplesAccessed
- sellers.json and OpenRTB SupplyChain transparency ↗IAB Tech Lab · About sellers.json; SupplyChain object; buyer responsibilitiesAccessed
- Deals API Specification v1 ↗IAB Tech Lab · Core goals; What it is; What it is notAccessed
Prepared from the cited public sources with AI-assisted research. Reported facts and editorial interpretation are presented separately.
CONTINUE THE RESEARCH
Explore your question further.
Request the full research report and discuss your market, brand questions and business context with GSP.
Request the full research report ↗