發布商簡介
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
您可以使用 publisherProfiles
資源,查看已協商的發布商相關資訊。
舉例來說,在「交易」敲定並放送時,domains
和 mobileApps
會說明發布商在出價要求中收到的廣告空間來源。
使用 deals
、finalizedDeals
和 proposals
資源時,發布商會以 name
中的完整 PublisherProfile
資源路徑來識別發布者。
並非所有發布商都共用完整的簡介,在這些情況下,您會收到下列欄位:
name
displayName
isParent
發布商的同一個主要簡介下可以有多個發布商簡介。
每個子發布商簡介都代表發布商的廣告空間的一部分。所有發布商的廣告空間都會顯示在上層發布商簡介中。如果發布商簡介為上層簡介,isParent
欄位會設為 True
。
所有發布商都有專屬的 publisherCode
。您可以在呼叫 publisherProfiles.list
時依 publisherCode
篩選,找出與特定發布商相關聯的所有設定檔。
視設定檔是父項或子項而定,某些欄位不會填入資料。舉例來說,父項設定檔不會填入 domains
和 mobileApps
。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-25 (世界標準時間)。
[null,null,["上次更新時間:2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eThe \u003ccode\u003epublisherProfiles\u003c/code\u003e resource provides access to information about publishers, including inventory details like domains and mobile apps for finalized deals.\u003c/p\u003e\n"],["\u003cp\u003ePublisher profiles are identified by a unique \u003ccode\u003ename\u003c/code\u003e within resources like \u003ccode\u003edeals\u003c/code\u003e, \u003ccode\u003efinalizedDeals\u003c/code\u003e, and \u003ccode\u003eproposals\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003ePublishers may have multiple profiles (parent and child) to represent different inventory segments, with the parent profile encompassing all inventory.\u003c/p\u003e\n"],["\u003cp\u003eAll publishers possess a unique \u003ccode\u003epublisherCode\u003c/code\u003e for filtering and identification purposes.\u003c/p\u003e\n"],["\u003cp\u003eSome profile fields, such as \u003ccode\u003edomains\u003c/code\u003e and \u003ccode\u003emobileApps\u003c/code\u003e, are specific to child profiles and not populated for parent profiles.\u003c/p\u003e\n"]]],["The `publisherProfiles` resource provides information about publishers, including `domains` and `mobileApps` for inventory origin. Publishers are identified by their `PublisherProfile` path (`name`) in deals, finalized deals, and proposals. Some publishers only share limited fields like `name`, `displayName`, and `isParent`. A parent profile encompasses all of a publisher's inventory, while child profiles represent portions of it. A unique `publisherCode` can be used to locate all associated profiles. `domains` and `mobileApps` are not available for parent profiles.\n"],null,["# Publisher profiles\n\nYou can use the\n[`publisherProfiles`](/authorized-buyers/apis/marketplace/reference/rest/v1/buyers.publisherProfiles#resource:-publisherprofile)\nresource to view information about publishers you're negotiating with.\n\nFor example, when a [deal](/authorized-buyers/apis/guides/marketplace/deals) is\nfinalized and serving, `domains` and `mobileApps` describe the origin of\ninventory you receive in bid requests from the publisher.\n\nWhen you use the `deals`, `finalizedDeals`, and `proposals` resources, the\npublisher is identified by the full `PublisherProfile` resource path found in\n`name`.\n\nNot all publishers share full profiles. In these cases, you receive the\nfollowing fields:\n\n- `name`\n- `displayName`\n- `isParent`\n\nA publisher can have multiple publisher profiles under a single parent profile.\nEach child profile represents a portion of the publisher's inventory. All of the\npublisher's inventory is represented in the parent profile. If a publisher\nprofile is a parent, the `isParent` field is set to `True`.\n\nAll publishers have a unique `publisherCode`. You can filter by `publisherCode`\nwhen calling `publisherProfiles.list` to find all of the profiles that are\nassociated with a given publisher.\n\nSome fields aren't populated depending on whether the profile is a parent\nor child. For example, `domains` and `mobileApps` aren't populated for parent\nprofiles."]]