Announcing v26 of the Google Ads API

<p> Today we are announcing the release of v26 of the Google Ads API. To use the new capabilities, you must upgrade your <a href="https://developers.google.com/google-ads/api/docs/client-libs?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-clientlibs" >client libraries</a > and client code. We've published all updated client libraries and code examples. </p> <p> Come join us for a live walkthrough of this release in our <a href="https://discord.gg/8jk8kaDh?event=1558145119318704218" >"Google Ads API Release Highlights" event on Discord</a > or our <a href="https://www.youtube.com/watch?v=x2zBr7XEYcU" >Ads Developers YouTube Live</a > tomorrow (October 15 at 10:00 AM ET). We'll also record the walkthrough and post it on YouTube if you can't attend live. </p> <h2>New features</h2> <p>Here are the highlights of what’s new in v26:</p> <ul> <li> <strong >Streamlined EU political advertising declarations: <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Campaign?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#contains_eu_political_advertising" >Campaign.contains_eu_political_advertising</a ></code ></strong > is now optional for campaigns and Demand Gen ad groups with upgraded targeting that positively target only locations outside the European Union and contain no proximity or location group criteria. You can check whether a declaration is required using the new <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/GeoTargetConstant?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#require_eu_political_advertising_declaration" >require_eu_political_advertising_declaration</a ></code > field on <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/GeoTargetConstant?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs" >GeoTargetConstant</a ></code >, <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/CampaignCriterion?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs" >CampaignCriterion</a ></code >, and <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/AdGroupCriterion?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs" >AdGroupCriterion</a ></code >. </li> </ul> <ul> <li> <strong>Vertical-agnostic travel bid modifiers: </strong>We've renamed hotel-specific <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/AdGroupBidModifier?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs" >AdGroupBidModifier</a ></code > criteria to apply consistently across travel verticals: <code>user_set_dates</code> (replacing <code>hotel_date_selection_type</code>), <code>advance_booking_window</code> (replacing <code>hotel_advance_booking_window</code>), <code>length_of_booking</code> with <code>min_days</code> and <code>max_days</code> (replacing <code>hotel_length_of_stay</code>), <code>start_day_of_week</code> (replacing <code>hotel_check_in_day</code>), and <code>start_date_range</code> (replacing <code>hotel_check_in_date_range</code>). </li> <li> <strong>Search Lift measurements: </strong>We've expanded lift measurement capabilities with support for Search Lift studies. You can now query the new read-only <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/SearchLiftKeywordBundle?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs" >SearchLiftKeywordBundle</a ></code > resource and segment by <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Segments?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#search_lift_keyword_bundle" >segments.search_lift_keyword_bundle</a ></code > and <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Segments?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#search_property" >segments.search_property</a ></code >. You can also analyze 15 new Search Lift metrics (including <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Metrics?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#relative_search_lift" >relative_search_lift</a ></code >, <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Metrics?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#normalized_incremental_searches" >normalized_incremental_searches</a ></code >, and <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Metrics?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#search_lift_impressions" >search_lift_impressions</a ></code >) alongside <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Campaign?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#lift_measurement_config" >Campaign.lift_measurement_config</a ></code >. </li> <li> <strong>Local Services Performance Max campaign creation: </strong>You can now create Google Local Services Performance Max campaigns with the API by setting <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Campaign.PmaxCampaignSettings?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#local_services_enabled" >PmaxCampaignSettings.local_services_enabled</a ></code > (which is now settable on creation and immutable afterwards) and providing the required <code>country_code</code> and Google Business Profile <code>listing_id</code> in <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Campaign.LocalServicesPmaxCampaignSettings?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs" >LocalServicesPmaxCampaignSettings</a ><strong>. </strong></code >We've also added support for <a href="https://developers.google.com/google-ads/api/reference/rpc/v26/LocalServicesLead?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#campaign" >linking leads to campaigns</a >, <a href="https://developers.google.com/google-ads/api/reference/rpc/v26/LocalServicesLeadTypeEnum.LeadType?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#coupon" >coupon lead type</a >, and <a href="https://developers.google.com/google-ads/api/reference/rpc/v26/ConversionActionCategoryEnum.ConversionActionCategory?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#message_lead" >message lead conversion category</a >. </li> <li> <strong>Unified enhanced conversions configuration: </strong>We have added <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Customer?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#enablement_setting" >Customer.enablement_setting</a ></code > and <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Customer?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#effective_enablement_setting" >Customer.effective_enablement_setting</a ></code > to expose the unified enhanced conversions configuration for the account, replacing <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Customer?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#enhanced_conversions_for_leads_enabled" >Customer.enhanced_conversions_for_leads_enabled</a ></code >. </li> <li> <strong>Shopping and Demand Gen enhancements: </strong>We've expanded <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/Campaign?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#listing_type" >Campaign.listing_type</a ></code > support to Shopping campaigns. <code ><a href="https://developers.google.com/google-ads/api/reference/rpc/v26/CurrencyConstant?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs" >CurrencyConstant</a ></code > now exposes the <a href="https://developers.google.com/google-ads/api/reference/rpc/v26/CurrencyConstant?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-refdocs#demand_gen_info.minimum_budget_per_day_micros" >minimum budget per day</a > for a Demand Gen campaign in a given currency. </li> </ul> <h2>Reminder: changes to release cadence</h2> <p> As <a href="https://ads-developers.googleblog.com/2026/10/google-ads-api-release-and-sunset.html" >announced</a > on October 12, 2026, Google Ads API is moving to two releases per month starting with v26. This faster cadence gives your automated agents and workflows earlier access to new Google Ads features. Our release blog posts and YouTube live events will move to twice a quarter, covering key updates across several releases at once. To follow individual releases, add the<a href="https://developers.google.com/google-ads/api/docs/release-notes?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-releasenotes" > Google Ads API release notes</a > to your<a href="https://developers.google.com/profile/help/saved-pages"> saved pages</a > to receive notifications whenever they change. </p> <h2>Getting started</h2> <p> If you use our client libraries, download the latest version of your client library to start using these features. Review the <a href="https://developers.google.com/google-ads/api/docs/release-notes?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-release-v26-0&utm_content=learnmore-releasenotes#v26-2026-10-14" >official release notes</a > for a full list of changes. If you have any questions or want to discuss this post, reach out to us on our <a href="http://goo.gle/ads-and-measurement-discord" >Google Advertising and Measurement Community Discord server</a >. </p> <p> For technical support issues, reach out to the <a href="https://support.google.com/google-ads/contact/google_ads_api" >Google Ads API support channel</a >. </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 >&nbsp;-&nbsp;<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

14th October 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.