管理账号关系
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
您可以使用 Accounts API 管理 Merchant Center 账号与其他服务提供商之间的关系。关系是指一种正式的关联,可让提供商向您的商家提供特定服务。服务定义了授予提供方的权限和功能,例如产品管理或广告系列管理。例如,将 Merchant Center 账号与 Google Ads 账号相关联后,Google Ads 账号就可以使用您的商品数据来投放广告系列。
关系由以下属性组成:
- 接收服务的 Merchant Center 账号
- 服务提供商
- 向 Merchant Center 账号提供的服务或一组服务
服务提供商可以将别名与他们所服务的账号相关联(这相当于 Content API for Shopping 中账号资源中存在的 seller_id
字段)。可以使用 AccountRelationship
资源中的可选 account_id_alias
字段分配别名,该别名用作自定义标识符。
使用别名访问账号的网址结构为 GET /accounts/v1/accounts/{provider}~{account_id_alias}
。
服务
在 Accounts API 中,账号可以接收以下服务:
账号汇总:此模型用于表示高级账号与其提供服务的账号之间的关系。服务提供商(高级账号)可以不受限制地完全访问关联的子账号。在这种情况下,externalAccountId
是 Merchant Center 账号的标识符。创建子账号时,必须省略 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 账号,请参阅创建和管理子账号。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-08。
[null,null,["最后更新时间 (UTC):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)."]]