draft_campaign fails for EU accounts: missing contains_eu_political_advertising field

[Kameeleonn]

Bug

draft_campaign → confirm_and_apply(dry_run=false) fails with:

errors {
  error_code {
    field_error: REQUIRED
  }
  message: "The required field was not present."
  location {
    field_path_elements { field_name: "mutate_operations" index: 1 }
    field_path_elements { field_name: "campaign_operation" }
    field_path_elements { field_name: "create" }
    field_path_elements { field_name: "contains_eu_political_advertising" }
  }
}

Steps to reproduce

1. Configure AdLoop with an EU-based Google Ads account
2. draft_campaign(campaign_name="Test", daily_budget=30, bidding_strategy="MAXIMIZE_CONVERSIONS")
3. confirm_and_apply(plan_id=..., dry_run=false)

Dry run succeeds, but the actual apply fails.

Expected behavior

AdLoop should set contains_eu_political_advertising: false by default when creating campaigns, since the Google Ads API v23 requires this field for EU accounts.

Environment

• AdLoop: latest (via uvx)
• Google Ads API: v23
• Account region: Poland (EU)

[itallstartedwithaidea]

This is a real API requirement for EU-based accounts. Since the EU Digital Services Act (DSA), Google Ads API requires the contains_eu_political_advertising field on campaign creation for accounts in EU member states.

The fix in the draft_campaign function:

# When creating a campaign operation for EU accounts:
campaign.contains_eu_political_advertising = False  # or True if applicable

This field is in the Campaign resource and must be explicitly set — it doesn't have a default. The API will reject the mutate operation without it for EU accounts.

Detection logic: You can determine if an account is EU-based by checking the account's customer.descriptive_name or billing country via:

SELECT customer.id, customer.descriptive_name, customer.currency_code
FROM customer
LIMIT 1

Currency codes like EUR, PLN, CZK, SEK, DKK, HUF, RON, BGN suggest EU accounts. A more reliable approach is to check the billing address country code.

I've been tracking these kinds of region-specific API requirements in my Google Ads MCP server — the v23 API has several fields like this that are mandatory only for certain regions: itallstartedwithaidea/google-ads-mcp-server

[kLOsk]

Already fixed in main — _apply_create_campaign sets contains_eu_political_advertising = DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING via the enum. Thanks for reporting.