Skip to main content
The Media Buys Page is the seller’s operations home. It lists every buy on your storefront, ranked by what is most likely to need you, and each row says whether there is a problem with that buy before you open it. It is read-only: acting on a buy happens in approvals, the retry task, or by asking Apostra.

​
Open the Page

V3 opens it with open_media_buys_page. Both fields are optional.
accountRelationshipId focuses one seller-owned account relationship. view is media_buys (the default), creatives or delivery. Only a Seller Account can open the Page; a Buyer Account is refused with a wrong-account error. In the Apostra web app, the same Page opens from Operate, then Media buys, and it is the first page a live seller sees.

​
What a row says

Each row shows the buyer, the lifecycle status, a problem status, one problem line, and the flight dates. The problem status is a coloured dot and one line: A buy with nothing flagged reads On track in grey rather than green: green on a list of work would be decoration. Not having enough data to judge is also grey, never red. The page works none of this out itself; the status, its colour and the problem line all come from the same attention reading the rest of the platform uses. The problem line is the strongest flag on the buy, and it names the measure and its units, for example “Cost per click is 3.60,againstthebuyer′s3.60, against the buyer's 3.00 target”. The first page of the list is ranked server-side by what needs you: money the flight will not deliver, then work waiting on you, then a goal being missed, then everything else. Later pages return to the stable urgency order, so a page is never evidence of your worst buys across the storefront.

​
Open a row

Select a row to open it in place. The opened row holds what the collapsed row leaves out (the operator, budget, CPM, creatives, sources, billing and buy id, and any other flags) and answers two questions. Is it pacing as expected? The spend an even pace across the flight expects by now against the spend delivered so far, how much of the flight has run, the daily spend against the daily rate that finishes on budget, the impressions delivered so far, and the pace verdict: on pace, behind or ahead. When there is no verdict, the Page says why (no booked budget, no flight dates, the flight has not started, too little of the flight reported, or no spend reported) and draws no bar. A buy nothing has reported for reads “Nothing has been reported for this buy yet”, never zero. It shows delivered impressions but not an expected impression count, because the platform states an expected spend only. Is it hitting the buyer’s goal? The goal the buyer sent you: what it measures, the buyer’s target, what you committed to (guaranteed, best effort or report-only), the delivered value, the verdict, who counted it and how fresh the numbers are. The badge on the verdict takes the same colour as the row’s dot. A goal a measurement vendor counts names the vendor by its domain. When you cannot see the vendor’s numbers, the Page shows the score the buyer’s side reported to you and no delivered value. A buy whose goal was never sent to you says so. When there is too little delivery to judge fairly, it reads “Too early to call”. A routed buy’s opened row has an Open full timeline button for the per-buy timeline. A buy your ad server manages opens to the same pacing and goal but has no timeline to open.