Google Business Performance API 的新 API 方法可通过单个 API 请求提取多个 `DailyMetrics`。 请查看弃用时间表和相关说明，并从 v4 reportInsights API 方法迁移至 Google Business Profile Performance API。
[null,null,["最后更新时间 (UTC)：2025-08-29。"],[[["\u003cp\u003eTo use the OAuth 2.0 implementation, configure the merchant consent dialog with application details and set your application's name and logo.\u003c/p\u003e\n"],["\u003cp\u003ePlatforms can leverage OAuth 2.0 to act on behalf of business owners for tasks like creating locations, replying to reviews, and managing admins, thereby minimizing merchant actions.\u003c/p\u003e\n"],["\u003cp\u003eMerchants need to perform certain actions directly, such as initial sign-in, acknowledging the consent dialog, and handling ownership claims.\u003c/p\u003e\n"],["\u003cp\u003eMerchants can revoke a partner's OAuth access to their Google Account if their business relationship ends.\u003c/p\u003e\n"]]],[],null,["# OAuth setup\n\nComplete the following steps to configure your platform for the OAuth 2.0 implementation:\n\n1. Configure the merchant consent dialog.\n\n When a merchant first attempts to access their Business Profile account through the\n partner platform with use of the APIs, they're presented with the merchant consent dialog.\n\n Once you grant third-party access to your account, Google sends a mandatory email\n notification to you. The notification alerts you, the location owner, that a change to who\n may access your account data has been made.\n\n Your Google Account now displays\n [apps with access to your account](https://myaccount.google.com/permissions),\n with additional details on what data in particular is accessible by the third-party app.\n Also, you can remove an app's access at any time when you click the **Remove Access**\n button. In this way, you control third-party access to your account data.\n\n The merchant consent dialog, which is accessible in your Google Cloud Project, allows you to\n configure the following consent information about the third-party partners to whom you've\n given access to your account:\n 1. **Application homepage link:** The homepage of the third-party partner to whom you've granted access to your account.\n 2. **Application privacy policy link:** A link to the partner's privacy policy.\n 3. **Application Terms of Service (ToS) link:** A link to the partner's ToS.\n\n For more on consent configuration, see\n [Setting up OAuth 2.0 \\\u003e User consent](https://support.google.com/cloud/answer/6158849).\n2. Set your application name and logo.\n\n Resellers must have the same application name and logo as our partners, or a separate\n Google Cloud Project to distinguish them from the Partner default.\n\nOAuth usage by platforms\n------------------------\n\nPlatforms may act on behalf of the owners and managers. This minimizes the number of required\nmerchant actions and reduces drop-off rates.\n\nOwners and managers must first sign into the partner platform with their Google Account and have\ntheir credentials cached. Cached OAuth 2.0 credentials, access tokens, and refresh tokens are used\nto view or edit location data.\n\nThe following are common examples of OAuth usage by platforms:\n\n- Create locations as the merchant, which establishes the merchant's Google Account as the primary owner.\n- Partners are able to reply to reviews and create posts as the business owner through a platform API integration.\n- Managers can reply as the business owner when they use the APIs.\n- Merchants can automatically [transfer locations](/my-business/content/transfer-locations) into Business Profile organizations.\n- Automatically\n [Add an admin to an account or location](/my-business/content/manage-admins#add_an_admin_to_an_account_or_location), such as a manager.\n\n For example, an invitation to a management user's Google Account is created by use of your\n cached OAuth 2.0 credentials. Then, the invitation is accepted with the use of the management\n user's cached OAuth credentials.\n | **Note:** Google sends email notifications to the merchant when users are added or removed from locations.\n\n### Exceptions that require direct merchant action\n\nNot all actions can be automated by API calls that use the merchant's OAuth credentials.\n\nThe following are some examples of exceptions that require direct merchant action:\n\n- Merchants must sign in to their Google Accounts at least once for the platform to cache OAuth credentials that are later used to make API calls and perform actions as the merchant.\n- Merchants must make a one-time acknowledgement of the OAuth 2.0 consent dialog that grants third party access to location data.\n- Merchants must sign in to their Google Account and manually click a link both to initiate and complete ownership claims.\n\n### Revoking Oauth access\n\nIf a merchant has ended their business relationship with a partner, the merchant can revoke Oauth\naccess of the partner to the merchant's Google Account. For more information, see\n[Manage access to your Google\nAccount](https://support.google.com/accounts/answer/14012355)."]]
