Skip to main content
Buyer Account Mapping is a Seller Page. It shows each buyer account your Seller Account has admitted or is reviewing, which buyer organisation owns it, and whether each of your inventory sources has an account mapped for it. V3 opens it with open_page. V3 has no tool that reads or writes its data, so the review and mapping work happens in the Page itself, by a person.

​
Open the Page

Opening the Page with no focus returns the consolidated view: operator and brand relationships and inventory-source coverage. To open one relationship’s Account setup case instead, add the relationship focus. relationshipId is the opaque id on an advertiser roster row’s accountSetupRelationshipId. blockedReason is optional, and it is the case’s blocked reason when you know it, so the case opens directly on it. It is ignored without relationshipId.
Only a Seller Account can open the Page. A Buyer Account is refused with a wrong-account error. open_page also accepts sourceId, sourceName and esaId for other Pages. This Page ignores them. In the Apostra web app, the same Page is under Storefront, then Buyers, then Buyer Account Mapping. For one buyer, select the buyer and open Account.

​
What the Page shows

The complete-account view below is rolled out storefront by storefront. Until your Seller Account is enrolled, the Page keeps the relationship-based view.
  • Accounts. Each buyer account, the verified buyer organisation that owns it, and your decision for that account.
  • Existing relationship. Relationships that predate complete-account identity, kept visible and read-only for identity.
  • Source coverage. For each account, whether every active inventory source is Mapped, Not required, Not set up, Needs account selection or Stale. Source names and native account ids stay private to you.
  • Sources. The last account-listing attempt for each source and whether the listing completed.
The Account setup case for one relationship shows one of these neutral statuses: Inside the Page, a person can also review pending buyer access, choose or confirm the source account for each source, download mapping CSV files and import a reviewed mapping feed, ask a buyer for information and confirm or withdraw that request, and assert or revoke billing readiness for a direct-billed account.

​
What V3 covers and what it does not

V3’s own contract covers opening the Page, with or without a relationship focus, and the summary read behind the consolidated view. V3 has no tool, noun or filter for the other jobs in the list above. An agent cannot approve a buyer’s access, map a source account, request or confirm buyer information, or assert billing readiness through V3. When a job needs one of these, open the Page, show the person the relationship focus and let them decide there. Two jobs around the Page have a V3 owner today:
  • Admit or decline an external buyer. Read the roster with search({ "kind": "account_relationship" }), read one relationship with get, and decide a seller-controlled pending intake with save_seller and its admission field. See Admit an external buyer and inspect delivery.
  • Inspect an admitted buyer’s delivery. Open the relationship-scoped Media Buys Page with open_media_buys_page and an accountRelationshipId.
Admission decides whether a buyer gets in. Source coverage decides which of your sources can serve that buyer, and billing readiness decides whether a direct-billed buyer can place orders. A buyer can be admitted and still show Not set up coverage or Awaiting billing. Re-read the relationship rather than assuming it is eligible.