管理帳戶關係
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
您可以使用 Accounts API 管理 Merchant Center 帳戶與其他服務供應商之間的關係。關係是指正式連結，可讓供應商為貴商家提供特定服務。服務會定義授予供應商的權限和功能，例如產品管理或廣告活動管理。舉例來說，將 Merchant Center 帳戶連結至 Google Ads 帳戶後，Google Ads 帳戶就能使用你的產品資料放送廣告活動。
關係由下列屬性組成：
- 接收服務的 Merchant Center 帳戶
- 服務供應商
- 提供給 Merchant Center 帳戶的服務或一組服務
服務供應商可以將別名與他們服務的帳戶建立關聯 (這相當於 Content API for Shopping 中「帳戶」資源的 seller_id 欄位)。別名可使用 AccountRelationship 資源中的選用 account_id_alias 欄位指派，並做為自訂 ID。
如要使用別名存取帳戶，網址結構為
GET /accounts/v1/accounts/{provider}~{account_id_alias}。
服務
在帳戶 API 中，帳戶可接收下列服務：
帳戶匯總：此模型會建立進階帳戶與其提供服務的帳戶之間的關係。服務供應商 (進階帳戶) 可完全存取連結的子帳戶，不受任何限制。在本例中，externalAccountId是 Merchant Center 帳戶的 ID。建立子帳戶時，必須省略 externalAccountId，因為系統會在建立帳戶時指派帳戶 ID。
廣告活動管理：這項服務會模擬 Merchant Center 帳戶與 Google Ads 帳戶之間的連結，讓 Google Ads 帳戶存取放送廣告活動所需的產品和帳戶資料。在本例中，服務供應商為 GOOGLE_ADS，而 externalAccountId 是 Google Ads 帳戶的 ID。
購物比較：代表與經營 Merchant Center 帳戶的購物比較服務 (CSS) 之間的關係。
店面資訊管理：這代表與商店經理的關係，可使用 Google 商家檔案管理店面商品目錄和資訊。
帳戶管理：這項服務可讓供應商對 Merchant Center 帳戶執行管理動作，例如設定帳戶設定、管理使用者或更新商家資訊。商家也可以限制授予的存取權。
產品管理：供應商可透過這項服務管理產品和相關功能，例如資料來源和規則。
畫面中有兩個人在握手
如要建立服務，提供服務的帳戶和接收服務的帳戶都必須授權連線。這項授權程序稱為「交握」。
交握程序分為兩個步驟：
- 其中一方提議服務連結。
- 對方核准或拒絕提案。
提案獲得接受後，服務即獲准，並視為完全建立。授予服務供應商的任何存取權，現在都授予給符合資格的使用者 (請參閱下方的存取權)。
請注意，建立、拒絕或核准提案的使用者，必須對啟動程序的帳戶擁有 ADMIN 存取權。因此，如果服務供應商提議提供服務，提出提議的使用者必須是服務供應商帳戶的 ADMIN，而接受或拒絕提議的使用者必須是接收帳戶的 ADMIN。
服務專屬交握行為
以下說明各項服務的具體握手需求：
帳戶匯總：這項服務只能在建立帳戶時一併設定。服務供應商應為進階帳戶，且由於進階帳戶使用者擁有建立帳戶的完整 ADMIN 存取權，因此服務會自動獲得核准。
廣告活動管理：這項作業會遵循正常的交握程序，但提案是在一個系統 (例如 Google Ads) 中進行，核准則是在另一個系統 (例如 Merchant Center 或透過 Merchant API) 中完成。
店面資訊管理：這項服務會在專用方法中提議握手，並在其他系統 (例如 Google 商家檔案) 中完成核准。如需詳細步驟，請參閱連結 Google 商家檔案指南。
帳戶管理：這項服務適用一般握手程序 (由服務供應商或商家提議，然後由另一方接受)。
產品管理：這項服務適用一般交握程序 (由一方提議，另一方接受)。
存取權
每種服務類型都會為服務供應商的使用者提供特定層級的存取權，方便他們管理帳戶：
帳戶匯總：這項服務提供完整的 ADMIN 權限。
廣告活動管理：這項服務提供受限的存取權，允許相關聯的 Google Ads 帳戶存取產品和基本帳戶資訊。
購物比較：這項服務預設提供完整的 ADMIN 權利。不過，商家可以限制在 Merchant Center 中授予的存取權。
店面資訊管理：這項服務不提供直接存取權。而是讓產品資訊與 Merchant Center 帳戶同步。
重要事項：以下服務類型所述的存取權僅適用於核准的服務供應商。如果您是服務供應商，並想使用這項功能，請與支援團隊聯絡。如果先前已獲准在 Content API for Shopping 中使用 accounts.link 方法管理產品，即可在 Merchant API 中使用這項服務，不必再次取得核准。
如果您是第三方平台，負責管理其他商家的帳戶，下表將說明不同概念如何對應至您的帳戶結構：
- 服務供應商：您的進階帳戶。
- 接收服務的帳戶：代表你管理業務的 Merchant Center 帳戶。
- 服務：
accountAggregation，或是將這些帳戶設為進階帳戶的子帳戶。不過，我們不建議這麼做，最好使用 accountManagement 服務。accountManagement，如果您是在建立帳戶後，為不屬於進階帳戶子帳戶的帳戶建立這項服務。
如要進一步瞭解如何設定進階帳戶並連結至新的 Merchant Center 帳戶，請參閱「建立及管理子帳戶」。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-08 (世界標準時間)。
[null,null,["上次更新時間：2025-08-08 (世界標準時間)。"],[[["\u003cp\u003eMerchant accounts can be linked through various relationships, defining the services one account provides to another.\u003c/p\u003e\n"],["\u003cp\u003eEach relationship includes a service provider, an external account ID, a service recipient, and the service(s) offered.\u003c/p\u003e\n"],["\u003cp\u003eA primary relationship type is "account aggregation," where an aggregator (like an advanced account) provides services to sub-accounts.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eservice\u003c/code\u003e type specifies the access level granted to the service provider, such as admin access in account aggregation.\u003c/p\u003e\n"],["\u003cp\u003eAdvanced accounts can manage sub-accounts, enabling third-party platforms to manage merchants under their hierarchy.\u003c/p\u003e\n"]]],[],null,["# Manage account relationships\n\nYou can use the Accounts API to manage the relationships between your\nMerchant Center account and other service providers. A relationship is a formal\nconnection that enables a provider to offer specific services to your business.\nA service defines the permissions and capabilities granted to the provider, such\nas product management or campaign management. For example, linking your Merchant\nCenter account to a Google Ads account allows the Ads account to use your\nproduct data for running ad campaigns.\n\nA relationship is composed of the following attributes:\n\n- The Merchant Center account receiving the service\n- The service provider\n- The service or set of services being provided to the Merchant Center account\n\nService providers can associate an alias with accounts they service (this is the\nequivalent of the `seller_id` field that was present in the\n[account](/shopping-content/reference/rest/v2.1/accounts#resource:-account)\nresource in Content API for Shopping). The alias can be assigned using the\noptional `account_id_alias` field within the `AccountRelationship` resource and\nserves as a custom identifier.\n\nThe URL structure for accessing an account using its alias is\n`GET /accounts/v1/accounts/{provider}~{account_id_alias}`.\n\nServices\n--------\n\nIn the Accounts API, accounts can receive the following services:\n\n- **Account aggregation** : This models the relationship between an [advanced\n account](//support.google.com/merchants/answer/188487) and the accounts it\n is providing services to. The service provider (the advanced account) gets\n full, unrestricted access to the linked sub-accounts. The\n `externalAccountId` is, in this case, the identifier of the Merchant Center\n account. When you [create a sub-account](/merchant/api/guides/accounts/sub-accounts),\n the `externalAccountId` must be omitted, as it will be assigned to the\n account's ID upon creation.\n\n- **Campaign management** : This service models the link between a Merchant\n Center account and a Google Ads account, giving the Ads account access to\n product and account data needed to run ad campaigns. The service provider in\n this case is `GOOGLE_ADS` and the `externalAccountId` is the ID of the\n Google Ads account.\n\n- **Comparison shopping**: This represents the relationship with a Comparison\n Shopping Service (CSS) that operates the Merchant Center account.\n\n- **Local listing management**: This represents the relationship with a store\n manager for managing local inventory and listings using a Google business\n profile.\n\n- **Account management**: This service enables the provider to perform\n administrative actions on the Merchant Center account, such as configuring\n account settings, managing users, or updating business information. The\n business can also restrict the access granted.\n\n- **Products management**: This service allows providers to manage products\n and related features like data sources and rules.\n\nHandshake\n---------\n\nTo establish a service, both the account providing the service and the account\nreceiving the service must authorize the connection. This authorization process\nis called a handshake.\n\nThe handshake is a two-step process:\n\n1. One party proposes a service link.\n2. The other party approves or rejects the proposal.\n\nOnce a proposal has been accepted, the service is approved and considered fully\nestablished. Any access right conferred to the service provider\nis now granted to qualified users (See [access rights](#access-rights) below).\n\nNote that the user creating a proposal, rejecting, or approving it must have\n`ADMIN` [access\nrights](/merchant/api/reference/rest/accounts_v1/accounts.users#accessright)\non the account initiating the process. So if the service provider\nproposes a service, the user making the proposal must be an `ADMIN` on the\nservice provider's account and the user accepting or rejecting the proposal\nmust be an `ADMIN` on the receiving account.\n\nService-specific handshake behavior\n-----------------------------------\n\nThe following is a description of the specific handshake requirements for each\nindividual service:\n\n- **Account aggregation** : This service can only be established as part of\n account creation. The service provider is expected to be an advanced\n account, and the service is automatically approved since users of the\n advanced account have full `ADMIN` access to the account being created.\n\n- **Campaign management**: While this follows the normal handshake process,\n proposals are made in one system (for example Google Ads) and approvals are\n done in the other system (for example in Merchant Center or through the\n Merchant API).\n\n- **Local listing management** : For this service, handshake is proposed in a\n dedicated method and approvals are done in the other system (for example\n Google business profile). Detailed steps are in the\n [Guide to link a Google business profile](/merchant/api/guides/accounts/link-business-profile).\n\n- **Account management**: For this service, the regular handshake process\n applies (proposed by the service provider or business, followed by\n acceptance from the other party).\n\n- **Products management**: For this service, the regular handshake process\n applies (proposed by one party, followed by acceptance from the other).\n\nAccess rights\n-------------\n\nEach service type provides a certain level of access for users of the service\nprovider over the account being serviced:\n\n- **Account aggregation** : This service provides full `ADMIN` rights.\n\n- **Campaign management**: This service provides a restricted access right,\n allowing the associated Ads account to access products and basic account\n information.\n\n- **Comparison shopping** : This service provides, by default, full `ADMIN`\n rights. However, the business can restrict the access granted in Merchant\n Center.\n\n- **Local listing management**: This service provides no direct access right.\n Instead, it enables the listing to synchronize its products with the\n Merchant Center account.\n\n**Important** : The access rights described for the following service types apply\nonly to approved service providers. Reach out to our [support\nteam](/merchant/api/support/get-help) if you are a\nservice provider and want to make use of this capability. If you were already\npreviously approved for the `accounts.link` method for products management in\nContent API for Shopping, you can use this service in Merchant API without\nfurther approvals.\n\n- **Account management** : This service provides, by default, full `ADMIN`\n rights.\n\n- **Products management** : This service provides full `ADMIN` rights. Note\n that in the future, this will be limited to only product-related access\n rights.\n\nHow relationships apply for third-party platforms\n-------------------------------------------------\n\nIf you are a third-party platform that manages accounts on behalf of other\nbusinesses, the following shows how the different concepts map to your account\nstructure:\n\n1. **Service provider** : Your [advanced\n account](//support.google.com/merchants/answer/188487).\n2. **Account receiving the service**: A Merchant Center account that represents the business you manage.\n3. **Service** :\n - `accountAggregation`, if you are creating these accounts as sub-accounts of your advanced account. However, this is discouraged and the preferred service is `accountManagement`.\n - `accountManagement`, if you are establishing this service after account creation to accounts that are not sub-accounts of your advanced account.\n\nFor details about how to set up an [advanced\naccount](//support.google.com/merchants/answer/188487) and link to new Merchant\nCenter accounts, see [Create and manage\nsub-accounts](/merchant/api/guides/accounts/sub-accounts)."]]
