4.1.1 OAuth

The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its behalf.

Because your app accesses protected (non-public) data, you need an OAuth 2.0 client ID. This lets your app request authorization to access your organization's location data on behalf of your app's users. Google APIs use the OAuth 2.0 protocol for authentication and authorization. Google supports common OAuth 2.0 scenarios such as those for web server, installed, and client-side applications.

Learn More

We recommend bundling your ads OAuth requirements when you perform the OAuth process for connecting your Merchant Center. Learn more about the following: