Google 发 v26、Meta 全版本收网：这周真要改代码的人该做什么Google ships v26 while Meta closes every escape hatch: what teams rewriting code must do now

2026-10-29 · 中英双语 · 来源见文末 · 编辑：Hermes

这一周有两条硬时间线撞在一起。10 月 14 日，Google 推了 Google Ads API v26 大版本，一批字段被改名、被移除；10 月 27 日，Meta 把 v26 的全部限制推到了每一个残存版本上——包括你没有指定版本的调用。前者要你自己动手改，后者已经在替你改，只是没通知你。另外三条：金融/房产/招聘类广告多了一道显式开关、Google 松动了「商业名称必须等于域名」的旧规矩、TikTok 把投放入口开给了 MCP 智能体。

Two hard deadlines landed in the same week. On 14 October Google shipped Google Ads API v26, renaming and removing a set of fields. On 27 October Meta extended every v26 restriction to every remaining API version, including unversioned calls. The first asks you to change code; the second has already changed it for you, without telling you. Three more items: a new mandatory switch for finance and housing ads, Google loosening the business-name-versus-domain rule, and TikTok opening its ad stack to MCP agents.

1. Google Ads API v26 上线：字段改名、移除，客户端要升到 34.0.0

Google Ads API v26 is out: fields renamed and removed, Python client now needs 34.0.0

v26 于 2026 年 10 月 14 日发布，是年内第三个大版本（v25 在 7 月 22 日、v25.2 在 9 月 23 日）。破坏性变更集中在三处：LocalServicesPmaxCampaignSettings 的 country_code 由可选变必填，并新增必填的 listing_id；ConversionTrackingSetting 里的 enhanced_conversions_for_leads_enabled 被移除，改看 enablement_setting；酒店类条件字段与酒店专属错误码全部改名为行业无关命名，min_nights/max_nights 平移到 min_days/max_days。新增能力包括搜索次数提升评测（SearchLiftKeywordBundle 与 15 个指标）、AI Max 实验校验错误码、需求开发系列的最低日预算字段、LINE 与短信商家私信、YouTube 音频可听度指标。官方时间表：v23 停用 2027 年 2 月，v24/v24.1 停用 2027 年 5 月，v24.2 停用 2027 年 6 月，v25 停用 2027 年 8 月。

Released on 14 October 2026, v26 is the year's third major version after v25 on 22 July and v25.2 on 23 September. The breaking changes sit in three places: country_code in LocalServicesPmaxCampaignSettings becomes required alongside a newly required listing_id; enhanced_conversions_for_leads_enabled is removed from ConversionTrackingSetting in favour of enablement_setting; and every hotel-specific criterion field and error reason is renamed to a vertical-neutral name, with min_nights and max_nights carrying over to min_days and max_days. New capability includes search lift measurement (SearchLiftKeywordBundle plus 15 metrics), an AI Max experiment validation error, a minimum daily budget field for Demand Gen, LINE and SMS business messaging, and YouTube audio audibility metrics. Sunset schedule: v23 in February 2027, v24 and v24.1 in May 2027, v24.2 in June 2027, v25 in August 2027.

对投手意味着什么 / What it means for the operator：
别指望「我们的调用没报错」这种安慰——被移除的字段在 v26 上直接报错，被改名的字段是静默失效。当务之急三件：把客户端版本钉死（Python 侧 v26 要求 ≥34.0.0），跑一遍 v25→v26 的 proto diff 找出你真正用到的字段，再把字段改名纳入 CI 检查。四个月三个大版本，靠人肉记 changelog 已经跟不上了，做自建投放系统的团队得把这张停用表接进自己的发布流程。
Do not take 'nothing errors' as comfort: removed fields fail hard on v26, while renamed ones simply stop working without a message. Three actions now: pin the client library (Python needs at least 34.0.0 for v26), diff the v25-to-v26 proto to find the fields you actually touch, and put field renames into CI. Three major versions in four months means nobody can track the changelog by hand; teams with in-house tooling should wire the sunset table into their release process.

2. Meta 的 10 月 27 日已经过去：v26 限制覆盖全部版本，版本锁定不再是退路

Meta's 27 October has passed: v26 restrictions now apply to every version, so pinning no longer helps

Meta 在 7 月 29 日随 Graph/Marketing API v26.0 发布的一批变更，于 10 月 27 日扩展到所有仍在支持的版本，包括未指定版本的调用。具体包括：Delivery Estimate 接口的 daily_outcomes_curve、budget_guardrail、estimate_dau 三个字段删除且无替代接口；47 个 Commerce Order Management 端点阻断，无替代方案；Instagram Explore Feed 版位被移除，显式指定即报错；Messenger Stories 从 messenger_positions 中被静默剥离，接口照样返回 200，但版位已经不投；poll 互动创意不能再创建。

A batch of changes Meta shipped with Graph and Marketing API v26.0 on 29 July reached every still-supported version on 27 October, unversioned calls included. The list: three Delivery Estimate fields — daily_outcomes_curve, budget_guardrail and estimate_dau — are gone with no replacement; 47 Commerce Order Management endpoints are blocked with no successor API; the Instagram Explore Feed placement is removed and now returns an error when explicitly requested; Messenger Stories is silently stripped from messenger_positions while the call still answers 200; and poll creatives can no longer be created.

对投手意味着什么 / What it means for the operator：
最该紧张的是「静默」那一条。任何会重写 ad set 的自动化——预算规则、批量编辑器、从自己数据库回灌的同步任务——都会在无报错的情况下把 Messenger Stories 抹掉；等发现时通常已经是三周后的报表，且找不到错误日志。唯一可靠的自查方式是写完就读回：拉一次 targeting spec，跟你发出去的内容逐字段比对。另外查一下那三个预测字段：还在给客户看「预估日均结果」的看板，这两天开始会返回 null，界面不会崩，数据会空。
The silent one is the danger. Any automation that rewrites an ad set — budget rules, bulk editors, a sync from your own campaign database — strips Messenger Stories from messenger_positions with no error at all; you find out weeks later in a report, with nothing in the logs. The only reliable check is to read back after every write: fetch the targeting spec and diff it against what you sent. Then check the three forecast fields: any dashboard still promising estimated daily outcomes is returning nulls as of this week. The page still renders, the numbers are just gone.

3. 金融、房产、招聘类广告：不显式声明受众自动化就直接报错

Finance, housing and employment ads now fail outright unless audience automation is declared

v26 起，住房、就业、金融产品与服务（HEC-F）类目中受限的非宽泛、非放宽型 ad set，创建时必须显式设置 targeting_automation.advantage_audience 为 1 或 0，省略会返回 ADS_TARGETING__REQUIRE_EXPLICIT_ADVANTAGE_AUDIENCE_FLAG。宽泛或默认结构、以及放宽型结构仍保留默认值；对存量 ad set 的更新不受影响。

From v26, constrained non-broad and non-relaxed ad sets in the housing, employment, and financial products and services categories must explicitly set targeting_automation.advantage_audience to 1 or 0 when created. Omitting it returns ADS_TARGETING__REQUIRE_EXPLICIT_ADVANTAGE_AUDIENCE_FLAG. Broad and default setups keep their defaulting behaviour, and updates to existing ad sets are unaffected.

对投手意味着什么 / What it means for the operator：
做贷款、保险、信用卡、招聘、房产的出海团队，自动建单会在模板这一层整批失败——而且是硬错误，很容易被当成账号权限问题查半天。改动很小：在投放模板里把 advantage_audience 显式写死成你要的值，不要依赖平台默认。顺手也把这件事当成合规提醒——受限类目本来就不该让系统自由扩量，显式写出来反而方便留痕。
Teams running loans, insurance, credit cards, hiring or property abroad will see bulk creation fail at the template layer, and the hard error reads enough like a permissions problem to burn an afternoon. The fix is small: hard-code advantage_audience to the value you want in your campaign template rather than trusting the default. Treat it as a compliance nudge too — restricted categories should not expand audiences on autopilot, and writing the flag down gives you something to show later.

4. Google 松口：商业名称可以不等同于落地页域名，但有三种人不在内

Google relaxes the business-name rule, but resellers and affiliates are still shut out

Google Ads 政策帮助中心 2026 年 10 月 1 日发布公告，将于 2026 年 10 月更新「商业名称要求」政策：在特定情况下允许广告中显示的商业名称与落地页域名不一致，条件是三条同时成立——商业名称准确反映广告主被认可的正式名称或品牌；广告主与域名所有者之间存在已验证的直接关系；广告主的产品或服务在落地域名上直接提供。第三方转售商、独立预订中介、联盟分销商与二级卖家不适用本条规定，并且被禁止把所售商品、服务或房源的品牌名单独作为自己的商业名称。政策页只写「2026 年 10 月」生效，未给具体日期。

A notice posted on 1 October 2026 in Google's Advertising Policies Help Center says the Business name requirements policy will change in October 2026 to permit differences between the business name and the destination domain, provided all three conditions hold: the name accurately reflects the advertiser's recognised name or brand; there is a verified direct relationship between advertiser and domain owner; and the advertiser's products or services are directly offered on the destination domain. Third-party resellers, independent booking intermediaries, affiliate distributors and secondary sellers are excluded and are barred from using the standalone brand name of the goods, services or properties they offer. The notice gives a month, not a day.

对投手意味着什么 / What it means for the operator：
这条对出海的集团架构最有价值：母公司持域名、子公司或子品牌投广告，过去常因名称与域名不符被拒，现在有了合规路径。但反过来更要小心——代投、分销、站群模式拿品牌名裸称现在是被明文禁止的，改素材时别踩。另外 Google 没有说明「已验证的直接关系」要拿什么证明，落地页域名归属、品牌授权文件这些证据最好提前备齐，别等被拒了才去找。
This is most useful to group structures common in cross-border advertising: a parent company owns the domain, a subsidiary or sub-brand runs the ads, and the name mismatch used to draw disapprovals. Now there is a lawful route. The risk runs the other way too — running ads as a reseller, distributor or on a network of sites under a bare brand name is now explicitly prohibited, so check creatives before relaunching. Google does not say what proves a verified direct relationship, so gather domain ownership and brand authorisation evidence in advance rather than after a rejection.

5. TikTok for Business 开放 MCP：投放可以直接接智能体，素材审批归口到 Smart+

TikTok opens MCP for advertisers, folding creative approval into Smart+

据 10 月 6 日至 7 日的行业报道，TikTok for Business 正式开放 MCP（模型上下文协议）接口，开发者与广告主可将 Claude、Kimi、Manus、Perplexity、Replit、Snowflake、腾讯 WorkBuddy 等智能体接入，用来规划、投放与管理广告工作流；平台称接口上线后使用它的广告主数量增长超过 200%。同批更新还有两项工具：Smart+ Creative Selection 把品牌自有素材、Symphony AI 生成的创意与达人内容汇总进同一个审批流；GMV Max 面向 TikTok Shop，可自动创建广告计划并自动消耗预算。

Industry reports from 6-7 October say TikTok for Business has opened an MCP (Model Context Protocol) interface, letting developers and advertisers connect agents including Claude, Kimi, Manus, Perplexity, Replit, Snowflake and Tencent WorkBuddy to plan, launch and manage campaigns. TikTok says the number of advertisers using the interface has grown more than 200 percent since launch. Two tools came with it: Smart+ Creative Selection pools brand assets, Symphony-generated creative and creator content into a single approval flow, and GMV Max, built for TikTok Shop, creates campaigns and spends budget automatically.

对投手意味着什么 / What it means for the operator：
对自建系统的团队，这是第二条接入路径——过去只能啃 REST 接口，现在可以让智能体走 MCP。但要先想清楚两件事：素材审批一旦归口到 Smart+ Creative Selection，「谁有权放行」就变成了合规责任人问题，得重新指定；GMV Max 自动花预算意味着必须配套预算上限和止损规则，否则代理商的日预算控制权是被架空的。接入前先在测试账户跑通一遍花费上限，别在客户账户上试。
For teams with in-house tooling this is a second integration path: instead of wrestling with REST endpoints, an agent can work through MCP. Two things need deciding first. Once creative approval funnels through Smart+ Creative Selection, whoever can approve becomes the compliance owner, so name that person. And GMV Max spending budget on its own means you need hard caps and stop-loss rules, or the agency quietly loses control of daily spend. Test the caps on a sandbox account, not a client's.

信息来源 / Sources

本页为公开信息的二次整理与解读，不构成对任何平台政策的官方说明。原文以各平台官方文档为准。

Google Ads APIMeta Marketing APITikTok AdsMCP政策合规出海投放

← 全部简报广告 API 文档库