AdTech

Curated Deals in Programmatic: Use Your SSP's Curation Tools, Work With a Curation Platform, or Build Your Own

What curation is, how a curated deal reaches a buyer by deal ID, how the money flows and where curator fees sit, and how to choose between your SSP's curation tools, an independent curation platform and a layer of your own. It also covers what each route leaves you owning, the OpenRTB, Deals API, SupplyChain, sellers.json and ads.txt standards, buyers' doubts about fees, reporting gaps and the questions to ask.

By amBrain12 min read

In this article

Curation in programmatic advertising is the packaging of ad space and data into a deal that buyers target by its identifier, the deal ID. The curator picks the inventory, adds audience or context data and sets a price. It may be a data company, a retailer, an agency trading desk, a publisher or the supply-side platform (SSP) itself. The buyer's demand-side platform (DSP) bids on the deal ID as on any private deal. You can run curation with your SSP's tools, through an independent curation platform, or with a layer of your own. The routes differ in who holds the deal IDs, the data, the reports and the contracts, and in who takes which fee.

The short answer: if your data and buyers sit on one or two SSPs, start with their curation tools and get the order of fees and deal-level reports in writing. A publisher or data owner with no team to sell deals can let an independent platform sell them, for a fee and under the platform's deal IDs. Build your own layer only when curation is your product and you can staff it for years. On every route, settle who owns the deal IDs and whether the buyer can see the fee.

What is a curated deal, and who takes part in one?

IAB Tech Lab, the ad industry's standards body, publishes the Deals API, an application programming interface (API) for passing deal terms between systems. Its specification defines curation as “the selection and organization of inventory using technology and data, with the goal of creating effective packages for advertisers through prepackaged or real-time operations.” It names three roles. The origin is the system where the deal is entered, which “will typically be an SSP”. The curator is the company that packaged the inventory and data. The seller is the company that signed the contract with the buyer. One company can hold several roles. All pages quoted in this article were read on 13 November 2026.

Technically, a curated deal is an ordinary private deal. OpenRTB 2.6 is IAB Tech Lab's protocol for bid requests. Each impression offered in a bid request can carry a private marketplace (PMP) object that lists deals, each with an ID and a floor price, the minimum bid. OpenRTB's implementation guide calls the deal ID a “targeting token” that buyers attach to “orders, line-items or campaigns”. The curator decides, through the SSP, which impressions carry the deal ID.

How does the money flow, and where does the curator's fee sit?

Microsoft and Google both say the curator is paid out of the buyer's bid, before the publisher's auction. Microsoft, which runs a curation product called Microsoft Curate, documents the order. Buyer-side fees are deducted first. Then come the curator's margin, its fee set as a percentage or a fixed CPM (cost per thousand impressions), and Microsoft's tech fee. The rest enters the publisher's auction, “where seller fees are deducted before all bids are ranked in the final auction.” The margin and the tech fee apply “only if the bid for the curated deal wins the impression in the seller's final auction.”

Here is an example with invented round numbers. A buyer bids $10.00 CPM after its DSP's fees, and a 20% curator margin takes $2.00. The tech fee may take more, and the pages read for this article do not give its size. At most $8.00 reaches the publisher's auction, and the SSP takes its own fee from that. In Google Ad Manager, where curation is still in beta, the curator's fee is also taken “out of the bid price before it enters the auction”.

Fees can stack. PubMatic sells curation through a product called Connect. Its chief executive, Rajeev Goel, told AdExchanger in 2025: “We have our core SSP fee. And we also have a data fee in the curation transaction based on the curator's fee. That fee is negotiated partner by partner.” Add the DSP's fee and the curator's margin, and four fees can sit between the advertiser and the publisher.

What do the SSPs' own curation tools offer?

Several SSPs and ad platforms sell curation tools. Five of them describe their tools this way:

  • Index Exchange says partners can create deal packages in Index Marketplaces “all without any added platform fees”, with “Real-time dashboards and audit logs”. At launch, its chief executive said customers could build on Index's supply “without having to make duplicative integrations to the same media owners”.
  • Magnite calls ClearLine a platform “where buyers and curators can discover, package, and activate” supply.
  • OpenX describes OpenXSelect as a “curation and supply-side targeting platform for brands and agencies” with “log-level reporting”, a record of each impression.
  • Equativ, which renamed its curation platform Maestro by Equativ, claimed in January 2025 “direct integration with more than 70 DSPs and over 30 data providers”.
  • Google Ad Manager lets publishers share signals with curators and let those curators package their inventory.

This route gives you the SSP's publishers, DSP connections, billing and reports. It fits a data owner or retailer new to curation, an agency trading desk that buys through a few SSPs, or a publisher packaging its own sites. You depend on one SSP's supply, fees and product plans, which can change. Microsoft, for example, announced in May 2025 that it would “no longer support media buying through our DSP, Microsoft Invest, starting on February 28, 2026”, while it kept Microsoft Curate.

Publishers should check the defaults. Google's help page says “By default, allowing inventory packaging is on for supported partners.” PubMatic's Goel said of publishers in the same 2025 interview: “We opt them in by default.” Both allow opting out, and Microsoft lets sellers block curators.

Microsoft says curated transactions “will not override any seller account configurations”, floor prices included. Google applies a curator's floor only when it is above the publisher's. Google also lets publishers choose, for each curator, whether to share contextual signals and user identifiers such as device IDs. Its contextual signals include the consent string of IAB Europe's Transparency and Consent Framework (TCF).

When does an independent curation platform make sense?

An independent curation platform sells its own curated deals through several SSPs, so publishers and data owners earn without selling deals themselves. Permutive, a data platform for publishers, documents its terms in public:

  • Publishers sign a Curation Order Form that “grants Permutive permission to package the publisher's cohorts into multi-publisher curated audiences”. Cohorts are audience groups, and the deals are “Permutive-branded”.
  • Permutive “handles all demand generation, audience packaging, deal creation, campaign optimization, and buyer reporting.”
  • It lists Monetize, Index Exchange Marketplaces, PubMatic, Google Curate and OpenX as supported SSP marketplaces. It activates cohorts on the web only, not on iOS, Android or connected TV.
  • It says it keeps “transparent fee structures capped at 40%”, and that sentence does not say what the 40% is taken from.

The platform holds the buyer relationship, the deals and the buyer reports. The route fits open-market inventory that the publisher does not sell directly, and data owners who want reach without a contract with each SSP. It also suits buyers who want one deal ID across many publishers.

What does building your own curation layer take?

Build when curation is the business: a retailer selling shopper data across publishers, a data company with many buyers, an SSP offering curation to its clients, or a publisher group pooling its sites. You still sell through SSPs or an exchange you run, and you need these parts:

  • Deals set up in each SSP, with their terms sent to each DSP. The Deals API lets the SSP push the terms and query a deal's status, and it gives the curator its own deal ID field.
  • A path for audience segments into the auction. One way is to put segment IDs in OpenRTB's user data object, with the segtax extension naming the taxonomy they come from. Another is to answer from your server when the SSP calls it. Google's Real-time Curation gives your server 50 milliseconds: “Segment responses received after 50 ms don't contribute to serving the impression.”
  • Controls for publishers: opt-in, blocklists and floor prices.
  • Fee logic with percentage and CPM margins, a cap, and one order of deductions that every report follows.
  • Reports per deal, publisher and buyer, including bid errors. Microsoft's curator reports, for comparison, cover “how money is flowing from demand to supply”, billing and bid errors.
  • Collection from buyers and payment to publishers and data owners. With an SSP's tools, the SSP does this. Outside them, you need each SSP to agree to do it for you, or you invoice buyers yourself and carry the risk of late payment.

Much of this is data pipeline and accounting work, not auction code, because the auction stays with the SSP unless you run your own exchange. The work does not stop at launch. Google's curation documentation, for example, has a section on responding to deprecations, the protocol fields Google plans to remove.

What does each route leave you owning?

On each route, look at who holds the data, the deal IDs, the reports and the contracts.

  • With an SSP's tools, data you match on your own server in real time stays with you, but segments you upload live in its systems. The Deals API defines a deal's ID as unique “in origin's namespace”, so the ID belongs to the SSP, and buyers must switch to new IDs if you leave that SSP.
  • With an independent platform, the deals carry its name and IDs, and it holds the buyers and their reports. Your contract is its order form.
  • With your own layer, you hold the deal library under your own IDs, the segment logic, the reports and the buyer contracts, under each SSP's terms. Buyers still target the deal ID that each SSP issues, unless you run your own exchange. If a firm builds it, the contract decides who owns the code.

Which standards apply to curated deals?

Five documents matter, and only one of them names the curator.

  • OpenRTB 2.6 carries deals in its PMP and Deal objects. With the private auction flag set to 1, bids “are restricted to the deals specified and the terms thereof.”
  • OpenRTB's SupplyChain object lists “all entities who are involved in the direct flow of payment for inventory” and has no curator role.
  • The ads.txt file on a publisher's site lets publishers “publicly and transparently declare who is authorized to sell their inventory”. The sellers.json file on an SSP's site marks each seller as “PUBLISHER, INTERMEDIARY, or BOTH”. Neither has a curator type. In 2025, PubMatic's Goel gave the two files as one reason curation was growing: “it's more difficult for intermediaries to get on publisher websites.”
  • The Deals API names the curator and carries the curator's deal ID and the fee type. It also says whether data from outside the publisher is applied, whether the deal spans several publishers and whether its sites can change. IAB Tech Lab says it adds transparency into curated deals “that is not currently available in the bid stream.” It sits outside OpenRTB, so buyers see these fields only from SSPs that implement it.

The Deals API specification also says what a deal ID does not prove. Terms sent through it “are not guaranteed to be accurately reflected in bid requests”, so buyers must check each request. Without a site ID or app bundle that matches the publisher's ads.txt, nobody can check that the seller is authorized. Deal IDs that get such requests “should be used rarely and closely monitored.”

Why do buyers question curation fees and transparency?

Will Doherty was vice president of inventory development at The Trade Desk, a DSP, when he told Digiday in January 2025: “I think there are some versions of curation that butt heads with our desire to have a fully transparent supply chain”.

The buyer's view has three gaps. First, the bid request does not name the curator. Second, the buyer may not see the fee. Google's Ad Manager page calls the curator's charge “a single fee that is fully transparent to the buyer”. Yet its page for agencies says “The agency may or may not see the fee value depending on the curation partner's visibility settings.” Third, the Deals API fee field gives the type of fee “but not what that fee is.”

Put the fee formula in the contract, and ask for reports per deal that show the gross bid, each deduction and what reached the publisher.

What can you measure on a curated deal, and what stays hidden?

Each party sees a slice. The DSP sees its bids, spend and results, the SSP sees the auction, the curator sees its platform's reports and the publisher sees bids after fees. Microsoft lets sellers break down reports by “is curated” and “curator member ID”. Google gives agencies the report dimensions “Curation partner fees” and “Fee visibility”. None of these joins DSP results to SSP fees for you.

Publishers want detail per deal too. Amanda Gomez, senior vice president of revenue operations at The New York Post, spoke at Permutive's Programmatic Summit in November 2024, which AdExchanger reported on. She listed what she wants: “I would want to know that deal ID, who's buying through there, how many impressions, what's the CPM, and what's the revenue?”

Microsoft's bid error report for curators uses “a randomly selected set of 1% of the errors”. If a deal does not deliver, you may need the SSP's help to find out why. Treat audience accuracy as the curator's claim until you test it. Run a holdout test. Put part of the budget on the curated deal and part on the same publishers without it, and measure both in your own DSP.

What should you ask a curation vendor or a firm that would build it?

  • What fee do you take, from which amount, and in what order with the SSP's fees?
  • Can the buyer see the fee? Will you report the gross bid, each deduction and the net to the publisher, per deal?
  • Who owns the deal IDs, and what happens to live deals if we leave?
  • Which SSPs, DSPs and formats do you cover, including apps and connected TV?
  • Which publishers are in each package, and how did they opt in?
  • Do you send deal terms through the Deals API, with the curator and fee type fields filled in?
  • Do we get log-level data and every bid error rather than a sample, and for how long?
  • Who invoices the buyer, and who pays the publishers and the data owners?
  • Will you agree to a holdout test measured in our own DSP?
  • If you build it for us: who owns the code, the segment logic and the data pipeline, and which parts are your reusable components?

Where does amBrain fit?

amBrain publishes this blog. It describes its AdTech work as “DSP development, real-time bidding platforms, and ad exchange engineering.” Three more lines describe parts of that work: “amBrain builds supply-side platforms (SSP) for publishers.” “amBrain builds ad servers: targeting, frequency capping and reporting.” “amBrain builds event analytics pipelines for ad tech: collection, processing and reporting of impression and click events.” It names one AdTech product: “RTBBidder, a demand-side platform we built for a client.” None of these lines names a curation product or describes curation work.

In its own words, “amBrain has been building software since 2019.” On how it works with clients, it says: “Three formats: full delivery, a dedicated team, or engineers embedded in your team.” Its line on ownership is “The client keeps full ownership of the product and the code, except our reusable components.” Ask for the list of those components by name before you sign.

This article is not a case study. The lines above name no client, and nothing here says that amBrain has built a curation tool or run curated deals for any company. The quotations come from IAB Tech Lab specifications, from documentation, help pages, product pages, press releases and a blog post of Google, Microsoft, Index Exchange, Magnite, OpenX, Equativ and Permutive, and from articles in AdExchanger and Digiday, read on 13 November 2026. The article claims no relationship between amBrain and any of them, recommends none of their products and gives no amBrain prices or timelines.

It is not legal advice either. Sharing user identifiers, consent strings or customer data with a curator can bring data protection duties in each market. Have a lawyer read the curation terms and your data processing agreements before you sign. If amBrain is on your shortlist, ask it the same questions as any other firm.

Topics

  • Curation
  • Deal IDs
  • Build or Buy
  • Programmatic

Building a DSP, a bidder or an ad exchange?

Send the design or the problem you are solving, and the numbers you already have.

Tell us about your project

We'll respond within 24 hours with a clear action plan.

Have a design like this on the table?

We'll respond within 24 hours with a clear action plan.

Free project intro call · 30 minutes