Skip to main content
Buyer Account Mapping gives a seller one consolidated record for each exact operator-and-brand relationship, such as a brand buying through its agency. An authorized buyer sees one account for that relationship, rather than one per inventory source. The seller can privately see whether each source has a current mapping. Open the portable Page with the storefront MCP tool:

​
What is canonical

The relationship is identified by the storefront, operator domain, and brand domain. A CRM record, GAM advertiser, FreeWheel reference, or another native ID can support that relationship, but none replaces it. This keeps two native accounts with the same literal ID separate. For example, 1234 under gam-primary and 1234 under freewheel-ctv are different source mappings even when both support the same buyer relationship.

​
Page views

  • Accounts shows each consolidated relationship and linked buyer access.
  • Source coverage expands the relationship across active inventory sources. Coverage is Mapped, Not required, Not set up, Needs account selection, or Stale. Source names and native IDs remain seller-private.
The Page is paginated and searchable. It does not expose private source topology or source-native account IDs to buyers.

​
Review pending buyer access

When a buyer requests access to a relationship that requires seller approval, the request stays pending until a storefront administrator decides it. List the pending requests with list_seller_account_grant_reviews in storefront MCP or GET /api/v2/storefront/account-mappings/reviews in the storefront REST API. Each row includes the current version needed to prevent a decision against stale review state. Use decide_seller_account_grant_review or POST /api/v2/storefront/account-mappings/reviews/{grantId}/decision to approve Interchange-cleared billing. Rejections require a reason. A decision changes the buyer access grant only: it does not create a native ad-server account, map an inventory source, or enable spend by itself. Existing grants and mappings keep their current state unless an administrator explicitly decides a pending request.

​
CSV exports and imports

The Page can download:
  • an empty source_account_bindings.csv v1 template;
  • current healthy source mappings; and
  • active native accounts with their source namespace, generation, status, and listing version.
The normalized mapping columns are:
Spreadsheet-formula leads are neutralized in every exported field. Select Import feed from the Page to open the portable import Task. The Task:
  1. lets an administrator choose the inventory sources covered by the file;
  2. uploads the bytes directly to private, short-lived storage;
  3. validates the exact schema, hashes, row count, relationships, source accounts, and current mapping authority;
  4. shows creates, updates, archives, unchanged rows, and quarantined rows; and
  5. applies the reviewed set in one atomic, version-checked commit.
Sandbox relationships use the same reviewed mapping flow as live relationships. If a storefront has both a sandbox and live relationship with the same operator and brand domains, the Task quarantines that row instead of guessing which one to map. Each successful commit records the administrator, revision, and impact in the seller’s activity audit. Audit delivery is durable and does not make the mapping transaction depend on a second service being available at commit time. Snapshot imports treat the selected sources as complete. A missing row can archive only a mapping that an earlier revision of the same feed created; manual mappings and mappings owned by another feed are never removed. Any quarantined snapshot row blocks the commit. Delta imports require the last committed revision ID and may apply only accepted rows after the administrator reviews the quarantine impact.
This release imports only source_account_bindings.csv. It does not create CRM records, canonical operator-and-brand relationships, grants, or native accounts. Exported native-account choices must already come from an authenticated inventory source. Files are limited to 10 MB and 10,000 data rows.
The MCP Task launcher is:
The upload, preview, and commit capabilities are app-only; they do not appear in the model’s tool catalog.

​
CRM and commercial policy

A CRM is optional evidence and workflow acceleration. Runtime product discovery, execution, and reporting use the inventory-source mapping for the relevant leg. Credit limits, billing approvals, and permissions remain in their owning typed commercial contracts; the account-mapping export does not copy or interpret arbitrary CRM fields. Native mapping support is runtime-specific. Agent-backed sources and managed Google Ad Manager or FreeWheel sources consume explicit native-account mappings. Sellers can refresh either managed source’s authenticated advertiser choices before exporting or importing mappings. A partial or truncated refresh keeps the previous choices active and never archives an omitted advertiser. Modular sources can also consume mappings when their active modules declare one shared account namespace across products, media buys, delivery, and account resources. CitrusAd is the first supported composition and maps a supplier team. The Page labels an incomplete composition as unsupported; it may participate only through an explicit, contract-valid Not required decision where account scope is not needed.