Koleksiyonlar ile düzeninizi koruyun
İçeriği tercihlerinize göre kaydedin ve kategorilere ayırın.
Pazarlık yaptığınız yayıncılar hakkındaki bilgileri görüntülemek için publisherProfiles kaynağını kullanabilirsiniz.
Örneğin, bir anlaşma kesinleşip yayınlanırken domains ve mobileApps yayıncıdan gelen teklif isteklerinde aldığınız envanterin kaynağını açıklar.
deals, finalizedDeals ve proposals kaynaklarını kullandığınızda, yayıncı name içinde bulunan tam PublisherProfile kaynak yolu ile tanımlanır.
Tüm yayıncılar tam profilleri paylaşmaz. Bu durumlarda aşağıdaki alanları alırsınız:
name
displayName
isParent
Bir yayıncının, tek bir ana profil altında birden fazla yayıncı profili olabilir.
Her alt profil, yayıncı envanterinin bir kısmını temsil eder. Yayıncının tüm envanteri ana profilde gösterilir. Ana profil, yayıncı profiliyse isParent alanı True olarak ayarlanır.
Tüm yayıncıların benzersiz bir publisherCode vardır. Belirli bir yayıncıyla ilişkili tüm profilleri bulmak için publisherProfiles.list çağırırken publisherCode etiketine göre filtreleme yapabilirsiniz.
Profilin bir üst veya alt öğe olmasına bağlı olarak bazı alanlar doldurulmaz. Örneğin, domains ve mobileApps üst profiller için doldurulmaz.
[[["Anlaması kolay","easyToUnderstand","thumb-up"],["Sorunumu çözdü","solvedMyProblem","thumb-up"],["Diğer","otherUp","thumb-up"]],[["İhtiyacım olan bilgiler yok","missingTheInformationINeed","thumb-down"],["Çok karmaşık / çok fazla adım var","tooComplicatedTooManySteps","thumb-down"],["Güncel değil","outOfDate","thumb-down"],["Çeviri sorunu","translationIssue","thumb-down"],["Örnek veya kod sorunu","samplesCodeIssue","thumb-down"],["Diğer","otherDown","thumb-down"]],["Son güncelleme tarihi: 2025-07-25 UTC."],[[["\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."]]
