This page tracks both feature deprecations and unversioned changes in the Google Ads API. For versioned changes, see the [Release notes](https://developers.google.com/google-ads/api/docs/release-notes). Regularly monitor the [Google Ads developer blog](https://ads-developers.googleblog.com/) to be the first to hear about upcoming feature deprecations. The following table lists the specific feature deprecations, validation changes, and other unversioned updates in the Google Ads API. | Effective date | Change area | Change type | Guidance and description | |---|---|---|---| | 2025-07-01July 2025 | Brand guidelines | Behavioral shift | For Performance Max campaigns with brand guidelines enabled (which is the default for new campaigns), **Business Name** and **Business Logo** assets must be managed at the campaign level using [`CampaignAsset`](https://developers.google.com/google-ads/api/reference/rpc/v26/CampaignAsset) (with field types `BUSINESS_NAME` and `LOGO`, respectively) instead of at the asset group level using `AssetGroupAsset`. Read more in [the blog post about business name and logo assets](https://ads-developers.googleblog.com/2025/07/what-you-need-to-know-about-business.html). | | 2026-01-01January 2026 | Call-only ads | Deprecation | The creation of new call-only ads (`CallAdInfo`) is no longer supported. Existing call-only ads will stop serving in February 2027, and API support will be completely removed. Use Responsive Search Ads with call assets instead. Read more in [the blog post about upgrading call-only ads](https://ads-developers.googleblog.com/2025/10/upgrade-your-call-only-ads-to.html). | | 2026-02-02February 2, 2026 | IP address and session attributes | Access restriction | New adopters of session attributes or IP address data in conversion imports are restricted from using these fields. Sending session data using `ClickConversion.session_attributes_encoded` or `ClickConversion.session_attributes_key_value_pairs`, or IP address using `ClickConversion.user_identifiers` without first being added to the allowlist fails with a `CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE` error. Use the Data Manager API instead. Read more in [the blog post about IP address and session attributes](https://ads-developers.googleblog.com/2026/01/changes-to-ip-address-and-session.html). | | 2026-04-01April 1, 2026 | Customer Match | Access restriction | Developer tokens with no Customer Match requests between October 1, 2025 and March 31, 2026 are restricted from using the Google Ads API for Customer Match workflows. Requests to [`OfflineUserDataJobService`](https://developers.google.com/google-ads/api/reference/rpc/v26/OfflineUserDataJobService) or [`UserDataService`](https://developers.google.com/google-ads/api/reference/rpc/v26/UserDataService) for these tokens fail with a `CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE` error. Use the Data Manager API for Customer Match workflows instead. Read more in [the blog post about Customer Match support](https://ads-developers.googleblog.com/2026/03/changes-to-customer-match-support-in.html). **Note:** Developer tokens have since been [deprecated in favor of Google Cloud projects](https://developers.google.com/google-ads/api/docs/api-policy/developer-token), but this historical access restriction remains in effect. | | 2026-04-01April 1, 2026 | Demand Gen campaigns budget | Validation rule | A minimum daily budget of 5 USD (or local currency equivalent) is enforced for all Demand Gen campaigns. In v26 and later, you can query [`CurrencyConstant.demand_gen_info.minimum_budget_per_day_micros`](https://developers.google.com/google-ads/api/reference/rpc/v26/CurrencyConstant.DemandGenInfo#minimum_budget_per_day_micros) to retrieve the minimum required daily budget for a currency (see [Create a Demand Gen campaign](https://developers.google.com/google-ads/api/docs/demand-gen/create-campaign#create-budget)). API creation or update operations that result in a daily budget under this threshold fail with a [`CampaignBudgetError.BUDGET_BELOW_PER_DAY_MINIMUM`](https://developers.google.com/google-ads/api/reference/rpc/v26/CampaignBudgetErrorEnum.CampaignBudgetError#budget_below_per_day_minimum) error and return the minimum required amount in [`details.budget_per_day_minimum_error_details`](https://developers.google.com/google-ads/api/reference/rpc/v26/ErrorDetails#budget_per_day_minimum_error_details). Existing campaigns running with less than the minimum budget are unaffected until their budget or duration in days is edited. See [the blog post about minimum budget requirements](https://ads-developers.googleblog.com/2026/02/minimum-budget-requirement-for-demand.html) for more details. | | 2026-06-01June 1, 2026 | Data retention | Policy change | The retention period for granular reporting data (daily, hourly, weekly) is reduced to 37 months. High-level data (monthly, quarterly, yearly) remains available for 11 years. Read more in [the blog post about data retention policies](https://ads-developers.googleblog.com/2026/05/new-data-retention-policy-for-google.html). | | 2026-06-15June 15, 2026 | Offline conversions | Access restriction | Developer tokens with no offline conversion upload requests between December 17, 2025 and June 15, 2026 are restricted from using the Google Ads API for offline conversions. [`UploadClickConversions`](https://developers.google.com/google-ads/api/reference/rpc/v26/ConversionUploadService/UploadClickConversions) requests for these tokens return a `CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE` error. Migrate your offline conversion workflows to the Data Manager API instead. See [the blog post about offline click conversion changes](https://ads-developers.googleblog.com/2026/05/changes-to-offline-click-conversion.html) for more details. **Note:** Developer tokens have since been [deprecated in favor of Google Cloud projects](https://developers.google.com/google-ads/api/docs/api-policy/developer-token), but this historical access restriction remains in effect. | | 2026-09-09September 9, 2026 | API policy | Deprecation | Developer tokens are deprecated and have been sunset. For more information on how API access is managed, see the updated [API access management and developer token sunset](https://developers.google.com/google-ads/api/docs/api-policy/developer-token) guide. | | 2026-09-23September 23, 2026 | Smart Campaigns | Deprecation | New Smart Campaigns cannot be created. Existing Smart Campaigns continue to serve ads and can be updated. Read more in [the blog post about support for Smart Campaigns](https://ads-developers.googleblog.com/2026/06/changes-to-support-for-smart-campaigns.html). | | 2026-09-30September 2026 | Language targeting | Deprecation | Manual language targeting (`https://developers.google.com/google-ads/api/reference/rpc/v26/CampaignCriterion#language`) is no longer supported for Search campaigns, AI Max for Search campaigns, and Performance Max ads shown on Google Search. Instead, ads automatically match to users based on the language of your ad creatives and landing pages alongside user language preferences. Adding or updating `CampaignCriterion.language` on Search campaigns fails with a `https://developers.google.com/google-ads/api/reference/rpc/v26/ContextErrorEnum.ContextError#operation_not_permitted_for_context` error, though existing language criteria are still returned in queries and can be removed using `https://developers.google.com/google-ads/api/reference/rpc/v26/CampaignCriterionService` (Performance Max requests don't return an error because the setting still applies to other channels). Stop setting language criteria when creating or updating Search campaigns. For details, see [Language targeting criteria](https://developers.google.com/google-ads/api/docs/targeting/criteria#language-targeting) and [the blog post about language targeting changes](https://ads-developers.googleblog.com/2026/08/google-ads-language-targeting-changes.html). |