Google Ads API ends new Smart Campaign creation
Google is drawing another line under legacy automation products in the Google Ads API: From August 3, 2026, developers and advertisers will no longer be able to create new Smart Campaigns through the interface. The decision is not an isolated technical detail but another signal in Google's longer consolidation around AI-driven campaign types such as Performance Max. Anyone still using API-based workflows for Smart Campaigns must review their processes before the deadline and migrate to future-ready campaign formats.
Smart Campaigns were among the simplest entry formats for smaller budgets and automated ad delivery. Through the API, such campaigns could be created programmatically in tools, agency platforms, and custom applications. With the planned end of new creation, Google is shifting focus again toward newer, cross-channel automation. Existing Smart Campaigns remain unaffected and continue running; updates and management through the API are still possible for live campaigns. Only the creation of new Smart Campaigns is impacted.
What changes from August 2026
Google has officially announced that creating new Smart Campaigns through the Google Ads API will no longer be supported from August 3, 2026. Anyone attempting to create such campaigns after that date will receive an error instead of a successful operation. For companies, agencies, and software providers that provision client campaigns automatically, this can cause noticeable disruptions if no migration has been prepared.
The technical boundary is clearly defined: developers should review all API requests where campaign creation sets advertising_channel_type to SMART and advertising_channel_sub_type to SMART_CAMPAIGN. This exact combination will trigger errors going forward. In version 24 of the Google Ads API, the response is SmartCampaignError.CREATION_FAILED. In version 23 and older releases, the API returns OperationAccessDeniedError.CREATE_OPERATION_NOT_PERMITTED instead. Teams still using older API versions should adapt error handling accordingly.
Why Google is betting on Performance Max
Behind the API change lies Google's broader strategic shift toward AI-driven ad products. Performance Max is the central alternative: the campaign uses machine learning for bidding strategies, audience selection, and creative optimization across multiple Google inventory surfaces. Smart Campaigns offered simplicity but do not reach the same scope of channels and automation that Google envisions for the future of campaign management.
Google explicitly recommends that advertisers choose Performance Max instead of new Smart Campaigns. Depending on objectives, classic Search campaigns or Demand Gen campaigns may also be suitable. Search works when search intent and keyword control are priorities. Demand Gen targets awareness and engagement through visual formats. The choice depends on budget, conversion goals, and how much control a team wants over targeting and creatives.
Alternatives at a glance
| Campaign type | Strength | Typical use |
|---|---|---|
| Performance Max | AI automation across many channels | Scaling with conversion focus |
| Search | Precise keyword and ad control | Demand-driven acquisition |
| Demand Gen | Visual reach and engagement | Top-of-funnel and remarketing |
Impact on developers and platforms
Applications that onboard new customers through Smart Campaigns are especially affected. SaaS tools, white-label solutions, and internal marketing automation must rebuild campaign creation. Simply swapping campaign types is rarely enough: Performance Max requires different assets, goal definitions, and sometimes different conversion setups. Reporting and budget logic can also change because Performance Max optimizes across channels and delivers less transparent single-channel metrics than classic Search campaigns.
Development teams should therefore define a migration plan early. This includes auditing all affected API calls, testing in a sandbox or with small budgets, updating error handling, and communicating changes to end customers. Waiting until August 2026 risks failures when creating new campaigns precisely when ad budgets are often scaled for quarterly goals.
Strategic context for marketing teams
For performance marketers, the change mainly means planning certainty: Smart Campaigns were never the core of large enterprise setups, but they served many SMBs as an entry point. The shift to Performance Max fits the pattern of recent years in which Google has prioritized bid automation, broad match, and asset-based ads more strongly. Teams combining organic visibility and paid search should examine how migration affects brand traffic, conversion tracking, and channel attribution.
The interface between SEO and SEA also gains relevance. When Performance Max increasingly converts branded searches and warm traffic, costs for visibility in paid search rise—a effect many brands already know from earlier PMax rollouts. Brands that simultaneously expand organic rankings for brand and product terms can reduce dependence on automated paid campaigns. The API change is therefore not only a developer topic but a prompt to rethink paid strategies holistically.
Checklist before the deadline
- Identify and document all API requests with
SMARTandSMART_CAMPAIGN. - Define and test a migration path to Performance Max, Search, or Demand Gen.
- Adapt error handling for API v23 and v24 to the new response codes.
- Review asset requirements, conversion tracking, and budget logic for the target campaign type.
- Inform customers and internal stakeholders about workflow changes before August 3, 2026.
By ending new Smart Campaign creation through the API, Google sets another milestone in consolidating automated ad products. Existing campaigns keep running, but every new API workflow will need a different foundation from summer 2026 onward. Migrating now avoids outages and positions teams for campaign management increasingly centered on Performance Max and AI-driven control.
