Google this week announced that starting April 1, 2026, the Google Ads API will enforce a minimum daily budget of 5 USD - or its local currency equivalent - for all Demand Gen campaigns. The change, disclosed on the Google Ads Developer Blog on February 27, 2026, by Mattia Tommasone of the Google Ads API Team, will take effect as an unversioned update, meaning it applies across all API versions simultaneously.

The announcement adds another layer of technical constraint to a campaign type that has been steadily accumulating new rules, requirements, and behavioral shifts over the past two years.

Why the floor exists

According to the Google Ads Developer Blog post, the minimum budget is designed to ensure that campaigns "have adequate budget to navigate the initial 'cold start' phase, during which our models learn and optimize for performance." The cold start concept is not new in machine learning-based advertising. When a campaign launches, the automated systems behind it lack historical data specific to that campaign. They require a period of active serving - and therefore spending - to calibrate bid decisions, audience selection, and creative optimization. A budget below a functional threshold can effectively starve that learning process before it reaches any useful conclusion.

The 5 USD floor is modest in absolute terms, but its enforcement at the API level is what makes the change operationally significant for developers and agencies managing campaigns programmatically.

Unversioned changes and what they mean

The update being classified as an unversioned change is a technical distinction worth understanding. Most Google Ads API changes are tied to specific version releases - developers can maintain older API versions for up to roughly 12 months before being required to upgrade. Unversioned changes, by contrast, cut across all active versions simultaneously. There is no version-locking that shields a developer from them.

Google Ads API v21, announced August 6, 2025, and v22, released October 15, 2025, both remain active. Developers on either version - or on any older supported release - will encounter the new budget validation starting April 1.

Different behaviors across API versions

The error handling differs depending on which version is in use, and developers will need to account for this distinction in their code.

For those on Google Ads API v21 and above, the system will return a BUDGET_BELOW_DAILY_MINIMUM error when attempting to create or update a Demand Gen campaign with an insufficient budget. The details.budget_per_day_minimum_error_details field will also provide additional context, including the actual minimum threshold in the relevant local currency.

Those still running on Google Ads API v20 will receive a generic UNKNOWN error code, which provides less immediate clarity. To identify the specific cause, developers must inspect the details.unpublished_error_code field, which will contain the string CampaignBudgetError.BUDGET_BELOW_DAILY_MINIMUM. This represents a more opaque experience that will likely prompt accelerated migration to newer API versions.

The gap between the two behaviors is consequential for anyone managing large volumes of campaigns through automation. A generic UNKNOWN error in a batch operation can be harder to parse and act upon than a named, specific error code - especially when systems are processing dozens or hundreds of campaign updates simultaneously.

When the validation fires

The validation logic is broader than just campaign creation. According to the announcement, the check will trigger "whenever a campaign's budget, start time, or end time is modified in a way that results in a daily budget below the floor." That final phrase carries weight. A campaign with a flighted or custom budget - where the total budget is spread unevenly across a date range - could find itself affected by what appears to be an unrelated edit. Adjusting an end date, for example, might compress the remaining budget across fewer days and push the implied daily spend below 5 USD, triggering the error even if no budget figure was directly changed.

This applies to both standard daily budgets and flighted (custom) budgets, according to the blog post. Developers and campaign managers who use date manipulation as part of their workflow - pacing strategies, flight scheduling, seasonal pausing - will need to build validation logic into their systems before sending API requests.

The treatment of existing campaigns

Existing Demand Gen campaigns running below the 5 USD threshold will not be forced off. According to the announcement, "existing Demand Gen campaigns that currently operate with a budget below the 5 USD threshold will continue to serve without interruption." This is a grandfathering provision, but it comes with a critical condition.

Any future modification to a grandfathered campaign's budget or duration will subject that campaign to the new rules. The implication is clear: once a developer or advertiser touches the budget or schedule of one of these campaigns, the 5 USD floor applies. To complete that edit, the budget must first be raised to meet the minimum.

For advertisers running low-budget test campaigns or narrow experimental Demand Gen flights at sub-threshold levels, the practical consequence is a forced budget decision the next time any campaign parameter changes. Campaigns that were previously left on autopilot at minimal spend may suddenly require attention.

Context: Demand Gen's expanding technical complexity

Demand Gen has accumulated a substantial set of rules and behavioral changes over the past eighteen months. The campaign type launched as a successor to Discovery campaigns and has since absorbed YouTube Video Action campaigns, with the transition completing by April 2025. Google phases out YouTube video action ads for Demand Gen covered the full scope of that migration.

In February 2026, just days before the budget floor announcement, Google quietly changed how Lookalike segments function within Demand Gen, converting them from hard targeting constraints to audience suggestions starting March 2026. That change, like this one, was announced with limited lead time. The Lookalike shift and the budget floor together represent two significant behavioral changes to Demand Gen arriving within weeks of each other.

Earlier in 2025, Google clarified value-based bidding requirements for Demand Gen, establishing that campaigns must accumulate at least 50 conversions with value within the past 35 days - including a minimum of 10 within the past seven days - before accessing maximize conversion value or target ROAS bidding. Combined with the minimum budget floor, these thresholds reflect a platform increasingly designed around the assumption that under-resourced campaigns produce unreliable data and should be constrained at the infrastructure level.

The four new Demand Gen features announced in November 2025 introduced further creative testing and brand safety controls. Target CPC bidding for Demand Gen also surfaced in June 2025, without formal announcement. Taken together, the campaign type has expanded rapidly in scope while simultaneously becoming more prescribed in its technical requirements.

Developer implications

The recommendation in the announcement is direct: "developers update their reporting and management systems to handle these new error codes." That guidance applies regardless of API version, though the implementation differs between v21+ and v20 as described above.

For teams managing programmatic campaign creation at scale - agencies running client accounts through custom tooling, or businesses with automated campaign generation pipelines - the April 1 deadline provides roughly 33 days from the announcement date to make the necessary code changes. That is not an unusually short window by industry standards, but it does require prioritization given the unversioned nature of the change.

The Google Ads API documentation overhaul announced August 14, 2025 improved developer access to campaign type-specific guidance, which may help teams navigate the validation details more efficiently. Developers on v20 who want the cleaner error handling available in v21 have the added incentive of upgrading before April 1 to simplify their error-handling logic.

What the 5 USD figure signals

The 5 USD threshold is low enough that it should not materially affect most live campaigns. Google's own guidance for value-based bidding in Demand Gen recommends daily budgets exceeding 20 times the expected CPA - a figure that dwarfs 5 USD for almost any campaign with meaningful conversion goals. But the floor's significance lies less in the dollar amount than in the precedent: Google is now encoding minimum operating conditions for Demand Gen directly into its API validation layer.

This is consistent with how the platform has approached other campaign types. Budget-to-CPA ratios, conversion thresholds for advanced bidding, and now a hard daily minimum all point toward a system architecture where campaigns that lack the resources to generate reliable learning signals are blocked or constrained before they can produce misleading data.

Timeline

Summary

Who: Google, specifically the Google Ads API Team via Mattia Tommasone, affecting developers and advertisers managing Demand Gen campaigns programmatically.

What: Starting April 1, 2026, the Google Ads API will enforce a minimum daily budget of 5 USD (or equivalent in local currency) for all Demand Gen campaigns. API v21 and above will return a named BUDGET_BELOW_DAILY_MINIMUMerror; v20 will return a generic UNKNOWN error requiring inspection of an unpublished error code field. Existing below-threshold campaigns continue serving but become subject to the new rules upon any budget or duration edit.

When: Announced February 27, 2026; enforcement begins April 1, 2026.

Where: The change applies globally across the Google Ads API as an unversioned update, affecting all supported API versions simultaneously.

Why: According to Google, the floor ensures campaigns have sufficient budget to complete the machine learning "cold start" phase. It is also consistent with a broader platform pattern of encoding minimum operational requirements directly into API validation to prevent under-resourced campaigns from generating unreliable performance signals.

Share this article
The link has been copied!