Stay organized with collections
Save and categorize content based on your preferences.
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:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-03 UTC."],[[["OAuth 2.0 allows third-party apps to access protected data with user or app's own authorization."],["You need an OAuth 2.0 client ID for your app to request access to your organization's location data on behalf of users."],["It's recommended to combine Merchant Center and Ads OAuth requirements during setup."],["Offline access is crucial for refreshing access tokens without repeated user prompts."],["Using a client library for OAuth implementation is highly recommended."]]],[]]