Connect Google Ads
Authorize Google and choose direct or MCC child accounts.
Open Connections & AI settings. Add a named connection and optionally enter an MCC / Login Customer ID.
Use your own Google Cloud OAuth Web client, or leave the custom client fields empty to use the platform client. Register the callback URL shown in the form. The client’s Cloud project must enable Google Ads API and have permission to access production accounts. OAuth consent verification and test-user restrictions are controlled by Google.
Developer Tokens were sunset on September 9, 2026. API access levels now belong to the OAuth client’s Google Cloud project. Google’s migration guide explains the current process.
Click Google 授权, choose the Google user with access, then select and save the advertising accounts you want to use. A connection can cover multiple accounts, including MCC descendants. Changing the OAuth client or MCC requires reauthorization and account selection.
Credentials are encrypted. Disconnecting removes MyAd’s refresh token and disables access from the workspace. It does not pause running campaigns or revoke all permissions at Google; pause campaigns first if needed, and revoke the app in your Google account for complete removal.
If discovery fails, check the connection’s error, Cloud project access, Google user’s account permissions and MCC ID. No guessed accounts or currencies are created.