Clients
Stay organized with collections
Save and categorize content based on your preferences.
You can create representations of your clients with the
clients
resource.
You can use clients to negotiate proposals, and subscribe to auction
packages on behalf of your clients. You can also use the clients resource
to manage the level of access your clients have to the Authorized Buyers
Authorized Buyers Marketplace UI.
For example, if a client’s
role
is set to CLIENT_DEAL_APPROVER, they can
independently do the following in the Authorized Buyers Marketplace UI:
- Initiate new proposals.
- Negotiate with publishers.
- Approve proposals.
To learn more about client roles and what they can access in the
Authorized Buyers Marketplace UI, see
ClientRole.
Visibility
Your clients aren’t visible to publishers, and don’t receive proposals initiated
by publishers unless sellerVisible is set to True.
A Client that isn't visible to publishers can still access Marketplace
features that are available to their role. For example, a Client that isn't
sellerVisible can view proposals you initiate on their behalf.
Identification
You can provide a unique identifier for each Client with partnerClientId.
For example, you might want to use partnerClientId to map a Client to your
own identifier for the client the Client represents.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-09-18 UTC.
[null,null,["Last updated 2024-09-18 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eclients\u003c/code\u003e resource allows you to create and manage representations of your clients, enabling proposal negotiation and auction package subscriptions on their behalf.\u003c/p\u003e\n"],["\u003cp\u003eClient roles, such as \u003ccode\u003eCLIENT_DEAL_APPROVER\u003c/code\u003e, determine the level of access clients have within the Authorized Buyers Marketplace UI, including initiating, negotiating, and approving proposals.\u003c/p\u003e\n"],["\u003cp\u003eClients' visibility to publishers can be controlled using the \u003ccode\u003esellerVisible\u003c/code\u003e property, impacting their ability to receive proposals directly from publishers.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003epartnerClientId\u003c/code\u003e provides a means to assign unique identifiers to clients, facilitating mapping to your internal systems.\u003c/p\u003e\n"]]],[],null,["# Clients\n\nYou can create representations of your clients with the\n[`clients`](/authorized-buyers/apis/marketplace/reference/rest/v1/buyers.clients)\nresource.\n\nYou can use `clients` to negotiate proposals, and subscribe to auction\npackages on behalf of your clients. You can also use the `clients` resource\nto manage the level of access your clients have to the [Authorized Buyers\nAuthorized Buyers Marketplace UI](//realtimebidding.google.com/#MARKETPLACE/MarketplaceDiscoveryPlace:marketplaceDiscovery).\n\nFor example, if a client's\n[`role`](/authorized-buyers/apis/marketplace/reference/rest/v1/buyers.clients#clientrole)\nis set to `CLIENT_DEAL_APPROVER`, they can\nindependently do the following in the Authorized Buyers Marketplace UI:\n\n- Initiate new proposals.\n- Negotiate with publishers.\n- Approve proposals.\n\nTo learn more about client roles and what they can access in the\nAuthorized Buyers Marketplace UI, see\n[`ClientRole`](/authorized-buyers/apis/marketplace/reference/rest/v1/buyers.clients#ClientRole).\n\nVisibility\n----------\n\nYour clients aren't visible to publishers, and don't receive proposals initiated\nby publishers unless `sellerVisible` is set to `True`.\n\nA `Client` that isn't visible to publishers can still access Marketplace\nfeatures that are available to their `role`. For example, a `Client` that isn't\n`sellerVisible` can view proposals you initiate on their behalf.\n\nIdentification\n--------------\n\nYou can provide a unique identifier for each `Client` with `partnerClientId`.\n\nFor example, you might want to use `partnerClientId` to map a `Client` to your\nown identifier for the client the `Client` represents."]]
