Google announced on February 26, 2026, that its Ads API and Google Ads scripts will introduce stricter account-level enforcement for the European Union Political Ads Regulation, with changes taking effect on April 1, 2026. Developers who use either product to create or manage campaigns will need to update their applications before that date to avoid disrupted operations. The announcement, posted on the Google Ads Developer Blog by Anash P. Oommen of the Google Ads API Team, marks another step in a compliance process that has been building since 2025.
The core change is direct: if a Google Ads account contains one or more campaigns that have not declared their EU political advertising status, all mutate calls related to campaign management will fail. The specific error returned will be MutateError.EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED. The enforcement will apply across API versions v20, v21, v22, and v23. Notably, other types of API calls - including reporting, account management, and keyword planning - will continue to function without interruption.
This distinction matters in practice. An account with a single undeclared campaign will see all of its campaign management operations blocked, even for campaigns that are entirely unrelated to political advertising. The breadth of the block gives urgency to the remediation process.
Developers can check whether a campaign is undeclared by examining the missing_eu_political_advertising_declaration field on the Campaign object. According to the announcement, the field evaluates to true for any campaign that has not yet received a declaration.
To retrieve the full list of undeclared campaigns, the Google Ads API Team provides a GAQL query using either the Search or SearchStream methods of GoogleAdsService:
select campaign.id
from campaign
where campaign.missing_eu_political_advertising_declaration = true
Once that list is obtained, declarations can be set using one of three methods: CampaignService.MutateCampaigns, GoogleAdsService.Mutate, or the BatchJobService. According to the announcement, these methods will not return the MutateError.EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED error as long as the update only modifies the contains_eu_political_advertising field. That exception is critical: it means developers can use those same methods to remediate the problem without triggering the error they are trying to resolve.
The field contains_eu_political_advertising accepts three values: CONTAINS_EU_POLITICAL_ADVERTISING for campaigns that do contain such content, DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING for those that do not, and UNSPECIFIED for campaigns lacking any declaration. The April 1 enforcement targets that third state.
Serving consequences follow the declaration itself, not just the lack of one. According to the announcement, any campaign that declares EU political advertising by setting contains_eu_political_advertising to true will stop serving ads in the EU. That means declaration is not a neutral act for campaigns that do contain political content - it simultaneously resolves the API compliance issue and ends their European distribution.
This February 2026 update is not the first time Google has adjusted its technical infrastructure to accommodate the EU's Transparency and Targeting of Political Advertising regulation, known as the TTPA. The regulation, established under EU Regulation 2024/900, took effect on October 10, 2025, and imposes comprehensive requirements on platforms that carry political advertising across the 27 member states.
Google first announced mandatory enforcement of EU political advertising declarations through the Ads API and Google Ads scripts back in August 2025. That earlier round introduced the contains_eu_political_advertising field across API versions v19.2, v20.1, and v21, with enforcement beginning September 3, 2025. Campaigns that declared EU political content ceased serving in the EU on September 22, 2025 - three weeks before the TTPA formally took effect.
Display & Video 360 followed a parallel path, with its API enforcing declarations starting September 8, 2025. That update added the containsEuPoliticalAds field to both LineItem and Advertiser objects in API versions v3 and v4, and introduced Structured Data Files version 9 with a "Contains EU Political Ads" column requiring explicit YES or NO values. Older SDF versions - 7.1, 8, and 8.1 - faced deprecation with support scheduled to end in March 2026.
Google's broader policy withdrawal from EU political advertising was announced in August 2025, limiting permissible political advertising on its platforms to official communications from EU member states or EU institutions. The application process for those permitted categories takes up to five business days, according to the company's help center documentation. The regulatory context driving these decisions centres on the TTPA's requirements for transparency notices, enhanced advertiser verification, cross-border compliance across 27 jurisdictions, and a seven-year record retention obligation for political advertisement data.
Meta similarly exited the EU political advertising market on October 6, 2025, prohibiting social issue, electoral, and political ads from running across Facebook, Instagram, and WhatsApp in the EU and associated territories. The company cited the TTPA's introduction of obligations to its processes and systems that create complexity and legal uncertainty.
The February 26 announcement focuses specifically on account-level API restrictions, a shift from the campaign-creation-level enforcement introduced in 2025. Where the September 2025 changes required new campaigns to carry a declaration at the point of creation, the April 2026 change looks at existing accounts and blocks all campaign management operations if any campaign within the account remains undeclared.
That difference in scope makes the April 1 deadline more operationally significant for large advertisers and agencies managing accounts with extensive campaign histories. An account that pre-dates the September 2025 enforcement could contain campaigns created before the contains_eu_political_advertising field was introduced - and those older campaigns may still lack declarations.
The enforcement applies to API versions v20 through v23. Version 19 was already sunset on February 11, 2026, which means developers who delayed migrating away from that version are now operating on a current version and will be subject to the new enforcement. Google Ads API version 23 launched on January 27, 2026, and version 22, released October 15, 2025, added targetless bidding for App campaigns alongside other automation features. All of these fall within scope of the April 1 changes.
The announcement explicitly limits the April 1 enforcement to mutate calls for campaign management. Calls involving reporting, account management, and keyword planning are unaffected. That carve-out preserves the ability to run performance analysis and investigate which campaigns need remediation, even in an account that would otherwise be blocked from making changes.
The practical workflow for affected developers involves three stages. First, query the account for undeclared campaigns using the GAQL snippet provided in the announcement. Second, for each undeclared campaign, determine whether it contains EU political advertising content. Third, set the contains_eu_political_advertising field accordingly using one of the three permitted mutate methods.
Google's provision of BatchJobService as an option is relevant for accounts with large numbers of campaigns. Batch operations allow declarations to be applied at scale without requiring individual API calls for each campaign, reducing the operational burden on development teams working against the April 1 deadline.
According to the announcement, these declaration-setting calls are specifically exempted from the MutateError.EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED error, which would otherwise block any mutate operations on an account with undeclared campaigns. That exemption is designed to allow remediation to proceed even in an account that has already entered the blocked state.
For campaigns that genuinely contain EU political advertising content and therefore receive CONTAINS_EU_POLITICAL_ADVERTISING declarations, the consequence is immediate cessation of serving within EU territories. This is not a new outcome - it has been the case since September 22, 2025 - but it remains material for any account that has not yet addressed these campaigns.
The April 1 deadline creates a concrete compliance task for any organization using the Google Ads API or Google Ads scripts to manage campaigns programmatically. Agencies and technology vendors operating on behalf of multiple advertisers face a multiplied version of that task, since undeclared campaigns in any single managed account could block all campaign management operations in that account.
The Digital Advertising Alliance's engagement with political advertising compliance questions in early 2026 reflects the broader industry tension between political advertising transparency requirements and the technical realities of programmatic campaign management. At a structural level, the TTPA's compliance requirements have effectively reorganized the European political advertising market - removing the two largest digital advertising platforms, Google and Meta, from most political advertising activity.
What remains is a narrowly scoped set of official government communications permitted on Google's platforms, combined with ongoing technical obligations for all other advertisers to confirm their campaigns are not within scope of the regulation. The February 26 update tightens that ongoing obligation by connecting declaration status directly to account-level API access.
Developers seeking assistance with these changes can contact Google through the Google Ads API support channel or the Google Ads scripts support channel, both referenced in the announcement from Anash P. Oommen.
Who: Google's Ads API Team, led by Anash P. Oommen, issued the announcement. The changes affect developers, agencies, and marketing technology vendors using the Google Ads API or Google Ads scripts to programmatically create or manage campaigns in any account.
What: Starting April 1, 2026, any Google Ads account with one or more campaigns that have not declared their EU political advertising status will have all campaign management mutate calls blocked, returning a MutateError.EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED error. The enforcement covers API versions v20, v21, v22, and v23. Reporting and account management calls remain unaffected. Campaigns that declare EU political content will stop serving in the EU.
When: The announcement was published February 26, 2026. Enforcement takes effect April 1, 2026.
Where: The enforcement applies globally to any Google Ads account accessed via the Google Ads API or Google Ads scripts, wherever undeclared campaigns exist. The serving restriction specifically applies within European Union territories.
Why: The change supports Google's compliance with EU Regulation 2024/900, the Transparency and Targeting of Political Advertising regulation that took effect October 10, 2025. The regulation imposes transparency, verification, and targeting restrictions on political advertising across 27 EU member states. Google determined that full compliance was operationally unfeasible and withdrew from most EU political advertising in late 2025. The April 2026 API enforcement closes remaining gaps by ensuring all campaigns in all accounts carry explicit declarations about their EU political advertising status.