[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eGoogle Ads supports optional Two-Step Verification (2SV) for enhanced security, allowing you to mandate its use for all sub-accounts under your Google Ads MCC account.\u003c/p\u003e\n"],["\u003cp\u003eIf 2SV is enabled, Google prompts the user for verification during the OAuth2 authentication flow before issuing a refresh token for API access.\u003c/p\u003e\n"],["\u003cp\u003eIf 2SV is required but not enabled, API calls using older refresh tokens will result in an error, prompting the user to enable 2SV for their Google account.\u003c/p\u003e\n"],["\u003cp\u003eAfter enabling 2SV and completing the OAuth2 flow again, a new refresh token is issued, allowing API calls without encountering the 2SV error.\u003c/p\u003e\n"]]],["Google Ads supports optional Two-Step Verification (2SV) for accounts. When enabled, during OAuth2 authentication, Google prompts users for 2SV before issuing a refresh token. Pre-existing refresh tokens remain valid unless 2SV is required. If 2SV is required and a pre-existing refresh token is used, the \"TWO_STEP_VERIFICATION_NOT_ENROLLED\" error occurs. The solution is to enable 2SV in the user's Google account and then repeat the OAuth2 flow to generate a new valid refresh token.\n"],null,["4.1.2 Two-Step Verification (2SV)\n---------------------------------\n\nGoogle Ads authorization supports 2-Step Verification (2SV) for Google Ads\naccounts. 2SV is optional, so you can choose whether to require all sub-accounts\nof your Google Ads MCC account to enable it. Even if you don't require your\nusers to set up 2SV, they can still activate it in their Google account\nsettings.\n| **Note:** 2SV is set up for the entire Google account and is not limited to ads.\n\nIf the user has enabled 2SV, during the OAuth2 authentication flow, Google\nprompts the user for 2SV before issuing a refresh token. Once issued, the\nrefresh token can be used to generate the access token needed in API calls.\nRefresh tokens that were issued prior to the user enabling 2-Step verification\nremain valid and not encounter an API error.\n\nIf you require users to set up 2SV, the error\n[TWO_STEP_VERIFICATION_NOT_ENROLLED](https://developers.google.com/google-ads/api/reference/rpc/v13/AuthenticationErrorEnum.AuthenticationError#two_step_verification_not_enrolled) is returned if API calls are made using\naccess tokens generated from a refresh token that was issued prior to the user\nenabling 2-Step verification.\n\nThe application should handle this error and direct the user to\n[enable 2-Step verification for their Google account](https://safety.google/authentication/).\n\nOnce the user has enabled 2-Step verification, they can go through the OAuth2\nauthentication flow again, this time encountering the prompt for the 2-Step\nverification. Completing the prompt issues a refresh token that can be used to\nissue access tokens that no longer encounter the error when API calls are made\nwith them.\n\nLearn More about [2-Step Verification](https://developers.google.com/google-ads/api/docs/oauth/2sv)."]]
