Skip to main content
Two reads help the agent that answers your buyers’ proposal requests, and you, judge a product before offering it: what its source forecasts it can deliver, and what buyers have paid for it. Both are reads of your own catalog; buyers do not see them.
Both reads are in beta for Seller Accounts on the beta profile. Elsewhere a product carries no forecast, and include: ["price_paid"] is refused with FEATURE_NOT_ENABLED.

Forecast

Every wholesale_product you read with get or search carries forecast: the product’s delivery forecast exactly as its source reports it, in AdCP’s own shape (DeliveryForecast: points, method, currency and the rest). Apostra does not forecast again for a brief’s flight or targeting. When the source reports no forecast, forecast is null.

Pricing across buyers

Add include: ["price_paid"] to get(kind: "wholesale_product") or search(kind: "wholesale_product") to read what buyers paid for each product. It is summed across buyers and never shows what any one buyer paid.
Or, when the figure is withheld:
How the figure is worked out: pricePaid is null when the product has no CPM or vCPM list price, because a per-thousand average cannot be compared with any other kind of price. A buyer counts as having bought a product when its package booked that product through the product’s own inventory source, under the product’s own id or the storefront’s id for it. Two sources can use the same product id, so a buy through one source never counts toward another source’s product. Each day’s delivery counts toward the product the package booked on that day, so a buy that later moves a package to another product keeps its earlier delivery on the product it was booked under then. A day on which no version of the buy was live has no booking to count under and is left out.