Consent unbundling in Ads APIs: Upcoming Changes to OAuth User Authentication

Beginning May 1, 2025, Google will implement consent unbundling for OAuth user authentication across all Google Cloud projects created before 2019. This significant change requires PPC managers utilizing Ads-related APIs to update their applications to accommodate this new functionality. As the deadline approaches, understanding the implications and necessary actions is paramount for maintaining seamless user interactions and compliance.

Understanding Consent Unbundling

Consent unbundling allows users to selectively authorize specific OAuth scopes rather than approving all permissions simultaneously. This flexible approach enhances user control and privacy while helping your application align with modern authentication standards. Google Cloud projects created post-2019 have this feature automatically enabled, while older projects will need updates.

Google Consent unbundling
Source: https://ads-developers.googleblog.com/

Who Will Be Affected?

Your application will be impacted if it meets the following criteria:

  1. Utilizes a Google Cloud Console project created before 2019.
  2. Implements the OAuth 2.0 user consent flow.
  3. Uses multiple Google APIs, including an Ads-related API.

Who Will Remain Unaffected?

  • Existing Refresh Tokens: Previously authenticated users will not face disruptions; existing refresh tokens will continue to operate normally.
  • Single Scope Applications: Applications utilizing a single OAuth scope won’t be affected as unbundling is irrelevant.
  • Service Accounts: Applications relying on service accounts for authentication are exempt from these changes.

Action Required: Steps to Prepare Your Application

PPC managers must ensure their applications can manage user consent flexibly. Follow these actionable steps:

  1. Include the include_granted_scopes parameter in your OAuth flow to request previously consented scopes.
  2. Analyze the OAuth response to determine which scopes a user has authorized.
  3. Integrate incremental authorization in your application.

For detailed guidance, refer to the granular consent guide provided by Google.

Testing the New Feature

To effectively test the unbundled consent feature:

  1. Create a New Project: A fresh Google Cloud project will have the unbundling feature already enabled, allowing for thorough testing.
  2. Enable in Existing Projects: For current projects, set the enable_granular_consent parameter to true in your authorization request.

APIs Affected by This Update

Below are the Ads-related APIs impacted by this change:

APIOAuth Scope
Google Ads APIhttps://adwords.google.com/api/adwords

Why This Matters for Your Campaigns

Understanding and adapting to these changes is critical for PPC managers to ensure uninterrupted service and compliance with new authentication protocols. By implementing these updates, you enhance user experience and trust, which can lead to better engagement rates and campaign success.

Never miss an update!

Stay informed, stay efficient and make data work for you.

Explore Our Free Tools

Simplify your PPC and SEO tasks with easy-to-use tools designed for marketers like you.

More Similar Posts

Your subscription could not be saved. Please try again.
Your subscription has been successful.

Deep Dive Newsletter

Subscribe to our newsletter and get a summary of PPC/SEO/Analytics deep dives regularly.

We use Sendinblue as our marketing platform. By Clicking below to submit this form, you acknowledge that the information you provided will be transferred to Sendinblue for processing in accordance with their terms of use