SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

How to Fix Google Ads Insufficient Authentication Scopes Error

Issue

When attempting to select an Account ID for the Google Ads Remarketing Lists destination in Segment, you may be unable to proceed and encounter the following errors:
  • Select an account Id to start sending data to Google Ads Remarketing Lists
  • Request had insufficient authentication scopes

 

Product

Twilio Segment 

 

Product

Segment Console

 

Cause

This error is returned by Google when the connected Google account does not possess the required permissions for Google Ads, or when the necessary OAuth authentication scopes were not fully accepted and granted during the initial authorization process. Because of these missing scopes, Segment cannot detect or pull a valid Google Ads account connection.

 

Resolution

To resolve this issue, you must reset and reauthorize the connection with the appropriate access levels:
  1. Disconnect the current Google Ads connection within your Segment workspace.
  2. Begin the reconnection or reauthorization process for the Google Ads destination.
  3. When prompted to sign in, ensure you select a Google account that has explicit access to the target Google Ads account (including the correct MCC/manager account, if applicable).
  4. Carefully review and accept all requested permissions and authentication scopes during the Google OAuth sign-in flow.
  5. Once authenticated, return to the Segment interface and attempt to select your Account ID again.

 

Additional Information

For a complete guide on setting up and configuring this destination, please refer to Segment documentation.

 

Have more questions? Submit a request
Powered by Zendesk