Signal · Regulation & Trade
Accelerate Google Ads API Basic Access reviews with brand verification
What the source reported
Source-reported<p> Today, we are launching a pilot process to expedite the <a target="_blank" href="https://developers.google.com/google-ads/api/docs/api-policy/access-levels#how-to-apply-for-basic-access?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-brand-verification-may2026&utm_content=learnmore-guides">Basic Access application</a> review process. If you have a pending Basic Access application for your Google Ads API developer token, then you can complete <a target="_blank" href="https://developers.google.com/identity/protocols/oauth2/production-readiness/brand-verification">brand verification</a> for your Google Cloud project to expedite the reviews for your pending application. With this launch, we aim to reduce the review delays and better meet the <a target="_blank" href="https://ads-developers.googleblog.com/2026/02/an-update-on-google-ads-api-developer.html">significant interest</a> from our developer community for Google Ads API access. </p> <p> <strong>What is brand verification?</strong> </p> <p> <a target="_blank" href="https://developers.google.com/identity/protocols/oauth2/production-readiness/brand-verification">Brand verification</a> provides a way for an application developer to verify that they accurately represent their identity and intent as specified by <a target="_blank" href="https://developers.google.com/terms/api-services-user-data-policy">Google API Services User Data Policy</a>. Brand verification is part of the <a target="_blank" href="https://support.google.com/cloud/answer/13463073">OAuth App verification process</a>, and is an automated self-service option for most developers. </p> <p> <strong>How do I expedite the review process?</strong> </p> <p> If you have a pending Basic Access application for your developer token, then follow <a target="_blank" href="https://developers.google.com/google-ads/api/docs/api-policy/brand-verification?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-brand-verification-may2026&utm_content=learnmore-guides">these instructions</a> to expedite the review process: </p><ol> <li><a target="_blank" href="https://developers.google.com/google-ads/api/docs/api-policy/brand-verification#prerequisite">Associate</a> your developer token to your Google Cloud project. This step is important; without it we won’t know which Google Cloud project to use as part of the review process. <li>Complete brand verification for your Google Cloud project. If you completed brand verification for your Google Cloud project in the past while using another Google API, you don’t need to repeat the process. If you have more than one Google Cloud project associated with your developer token, you need to complete brand verification only for one project.</li></ol> <p> Once your Google Cloud project is brand verified, your pending Basic Access application will be reviewed in the next few hours. </p> <p> <strong>Is brand verification mandatory?</strong> </p> <p> Currently, brand verification is optional and is used only as a signal for faster determination of Ads API Basic Access eligibility. This means that </p><ul> <li>You may complete the Brand verification process for your Google Cloud project to expedite the review process for your Basic Access application. <li>The Google Ads API Compliance team may request some developers with pending Basic Access applications to complete brand verification.</li></ul> <p> You don’t need to complete brand verification if you already have an approved developer token and aren’t newly applying for Basic Access level. </p> <p> We will closely monitor the developer experience throughout pilot surveys and use that data to determine the future changes to the application review process for developer token access levels. </p> <p><span class="byline-author"><a target="_blank" href="https://g.dev/anash"><img width="40" height="40" src="https://lh3.googleusercontent.com/a-/AD_cMMRmfdsXvZhyLvWsLuqqcScxtYI0ih7DPGCk8lTee140NzXH=s300" style="vertical-align:middle; border:none;"></a> - <a target="_blank" href="https://g.dev/anash" rel="author">Anash P. Oommen</a>, Google Ads API Team</span></p>
- Publication
- Google Ads Developers Blog · Government/Regulator
- Published
- 7th July 2026
- Original report
- ads-developers.googleblog.com
ProcIntel stores what the source published in its feed — a headline, a summary and a link. It does not store or reproduce the full article.
What ProcIntel recorded
ProcIntel-derived- Category
- Regulation & Trade
- Geography
- United States
- Organisations
- None identified
- Collected
- 3rd October 2026 · 08:09
Initial assessment ProcIntel's automatic, provisional read of this individual Signal -- Initial Significance and Initial Confidence, computed deterministically before any Event extraction or human review.
A provisional, automatically computed reading of this individual Signal, before Event extraction or human review. Not a final rating.
Initial Significance Moderate (28.0/100). Strongest contributor: Procurement Impact (21.0/30 points). Limiting factor: Geographic Breadth (0.0/10 points). Initial Confidence Low (39/100, data sufficiency: Insufficient). Strongest contributor: Source Authority (40.0/40 points). Limiting factor: Specificity (0.0/20 points). Capped at 39 (Low) -- insufficient structured evidence to support a higher Confidence reading, regardless of source authority.
- Strongest contributor
- Procurement Impact
- Limiting factor
- Geographic Breadth