This page tracks both feature deprecations and unversioned changes in the Google Ads API. For versioned changes, see the Release notes.
Regularly monitor the Google Ads developer blog 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 |
|---|---|---|---|
| July 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
(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.
|
| January 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.
|
| February 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.
|
| April 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
or
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.Note: Developer tokens have since been deprecated in favor of Google Cloud projects, but this historical access restriction remains in effect. |
| April 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
to retrieve the minimum required daily budget for a currency (see
Create a
Demand Gen campaign). API creation or update operations that
result in a daily budget under this threshold fail with a
CampaignBudgetError.BUDGET_BELOW_PER_DAY_MINIMUM
error and return the minimum required amount in
details.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
for more details.
|
| June 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. |
| June 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
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
for more details.Note: Developer tokens have since been deprecated in favor of Google Cloud projects, but this historical access restriction remains in effect. |
| September 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 guide. |
| September 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. |
| September 2026 | Language targeting | Deprecation |
Manual language targeting (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. Adding or updating
CampaignCriterion.language on Search campaigns fails
with a ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT
error (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. Read more in
the blog post about language targeting changes.
|