Plan API migrations, campaign transitions and advertising restriction windows. Find the affected workflow, a suggested owner and evidence to retain alongside each verified source date.
10 changesTiming as of 27 October 2026 · Source time zone where stated
Stated deadline
Google Merchant CenterPast milestone
Deprecation and sunset
PMC interpretation
Content API for Shopping: sunset and staged service degradation
Who is affected
Custom product-feed and Merchant Center integrations still using Content API for Shopping v2.1.
What to do
For a custom integration, complete and validate a Merchant API migration. If a commerce platform manages the connection, establish which partner owns it and verify that product price, availability and diagnostics remain current.
Suggested owner
Feed integration owner or ecommerce platform partner
Evidence to keep
The active endpoint, migration or extension status, request logs and recent product-update timestamps.
The sunset milestone has passed. Google describes intermittent HTTP 410 errors from 1 September for clients without an active extension and full decommissioning in early 2027, subject to revision. There is no confirmed final shutdown day.
Adds an all-day reference using the published dates. Calendar copies do not update automatically.
Stated deadline
Google AdsPast milestone
Google Ads API v22 sunset reminder
PMC interpretation
Google Ads API v22 has reached its sunset
Who is affected
Connectors, scheduled exports and custom tools still sending Google Ads API v22 requests.
What to do
If reporting or automation failed around the sunset, inspect the request version and migrate affected jobs to a supported API version. Reconcile any reporting gaps rather than assuming a campaign stopped serving.
Suggested owner
Reporting engineer or connector support team
Evidence to keep
Versioned request logs, vendor upgrade confirmation and a checked export covering the interrupted reporting period.
This is a past API availability milestone, not an advertising-account shutdown. Google states that v22 requests fail from the sunset date. A successful interactive report does not validate every scheduled job.
Google Ads Developer BlogLast successful source review:
Adds an all-day reference using the published dates. Calendar copies do not update automatically.
Restriction window
Meta AdsCurrent window
Upcoming 2026 Restriction Period for US Ads About Social Issues, Elections, or Politics
PMC interpretation
US political-ad restriction period
Who is affected
New US ads about social issues, elections or politics. Qualifying existing ads have different rules.
What to do
Identify affected campaigns and confirm the permitted submission and editing rules before scheduling creative.
Suggested owner
Paid social lead and the person responsible for ad authorization
Evidence to keep
The current policy notice, affected ad IDs and a documented submission plan.
Dates follow Meta’s Pacific Time restriction window. Source access was limited on the latest check; follow the original announcement and current account guidance before acting.
Adds an all-day reference using the published dates. Calendar copies do not update automatically.
Stated deadline
LinkedIn AdsUpcoming
Migrations
PMC interpretation
LinkedIn Marketing API version 202511 sunset
Who is affected
Applications that send requests with LinkedIn Marketing API version 202511, not every LinkedIn advertiser.
What to do
Ask each connector owner which API version its current requests use. Schedule an upgrade and verify a recent reporting or campaign-management workflow before the sunset.
Suggested owner
Connector maintainer or reporting vendor
Evidence to keep
The requested API version, vendor migration confirmation and a recent successful scheduled output.
Version 202511 denotes November 2025, not the report period. A vendor claiming support is not proof that your scheduled job migrated. The linked PMC article explains version retirement using an earlier version.
Adds an all-day reference using the published dates. Calendar copies do not update automatically.
Month only
Display & Video 360Upcoming
Announced Deprecations
PMC interpretation
DV360 YouTube responsive ads require business identity assets
Who is affected
YouTube responsive ads managed through DV360 API or Structured Data Files when advertiser defaults do not supply the business name and logo.
What to do
Review advertiser defaults and ad-level identity assets. Update SDF templates and validate the inherited values or explicit business name and logo before the requirement takes effect.
Suggested owner
Programmatic operations and creative trafficking lead
Evidence to keep
Advertiser defaults, resolved business identity for a sample ad and a validated SDF export or upload.
Google now lists January 2027, without a specific day. Defaults can supply the values, so an empty ad-level field is not automatically a missing asset. This is a DV360 requirement, not a blanket Google Ads migration.
Google for DevelopersLast successful source review:
Adds an all-day reference using the published dates. Calendar copies do not update automatically.
Projected month
Google AdsUpcoming
Deprecation and sunset
PMC interpretation
Google Ads API v23 family: projected sunset
Who is affected
Reporting tools and automations requesting v23, v23.1 or v23.2.
What to do
Inventory request versions across scheduled jobs. Plan an upgrade to a supported version and compare reporting outputs before the projected sunset month.
Suggested owner
Reporting engineer or connector vendor
Evidence to keep
The request version used by each job, its supported client-library version and a reconciled scheduled export.
February 2027 is tentative and can change. The v23 minor versions share that month. A newer client library alone does not prove that a job sends a newer request version.
Adds a planning window for the whole month, not a confirmed cutover day. Calendar copies do not update automatically.
Month only
Google AdsUpcoming
Upgrade your Call-Only Ads to Responsive Search Ads with Call Assets in the Google Ads API
PMC interpretation
Existing call-only ads stop serving
Who is affected
Advertisers still relying on the legacy call-only ad format, including API-managed campaigns.
What to do
Identify remaining call-only ads and prepare responsive search ads with the appropriate call assets. Check the phone destination, eligibility and call-conversion measurement before relying on replacements.
Suggested owner
Search lead and call-tracking owner
Evidence to keep
The legacy ad inventory, replacement ad and asset status, verified phone destinations and conversion checks.
New call-only ad creation was already blocked in January 2026. February 2027 concerns existing ads and the end of API support. The announcement does not specify a universal day or guarantee equivalent call volume.
Google Ads Developer BlogLast successful source review:
Adds a planning window for the whole month, not a confirmed cutover day. Calendar copies do not update automatically.
Month only
Google AdsUpcoming
Google’s Dynamic Search Ads are upgrading to AI Max
PMC interpretation
Dynamic Search Ads auto-upgrade to AI Max begins
Who is affected
Search campaigns using Dynamic Search Ads. This is a separate transition from Display Expansion.
What to do
Inventory DSA campaigns, review the current AI Max controls and agree how to compare targeting, creative and landing-page behaviour during the transition.
Suggested owner
Search strategy lead and account owner
Evidence to keep
The campaign inventory, existing settings and the source’s dated update rather than an older summary.
Google’s 11 June update moves the DSA transition to February 2027. Older page summaries still mention September. Automatically Created Assets and campaign-level broad match follow a separate timetable. No universal February day is stated.
Google Ads & CommerceLast successful source review:
Adds a planning window for the whole month, not a confirmed cutover day. Calendar copies do not update automatically.
PMC CHANGE-PLANNING FRAMEWORK
Turn an advertising deadline into an owned task
A platform announcement is the starting point. Before creating a task, identify the accounts, features or integration versions actually affected. A campaign migration, an API sunset and an ad-submission restriction have different owners and different evidence of completion.
Read the date before setting your internal target
Date type
What it means here
Planning response
Stated deadline
The source names a particular calendar day.
Set an earlier internal check appropriate to your own testing and approval time.
Restriction window
Rules apply over a period, with a publisher time zone when known.
Review submission and editing conditions before scheduling affected ads.
Month-only transition
The publisher gives a month rather than a universal cutover day.
Prepare before that month and monitor the account notice. Do not invent a first-day deadline.
Keep a small change record
Scope: List the campaigns, connectors or workflows in use and the source condition that makes them relevant.
Owner: Assign someone who can verify the setting or request version, with a vendor contact where needed.
Proof: Retain the notice, before-and-after configuration and a representative output. A successful login alone does not validate a scheduled reporting job.
Follow-up: Record what remains uncertain and who checks it after the expected change. Passing a calendar date does not prove a rollout is complete.
The suggested owners and evidence on these cards are PMC planning advice. They are not additional platform requirements or confirmation that your account has migrated. Source-check dates describe when the supporting page was read; they do not replace its publication date or effective date.
For the announcement and its wider implications, open the newsfeed. Use this calendar when the question is who needs to prepare, by when, and how to establish that the work is done.
Dates with context, not countdown pressure.
Source publication, the effective date and our source review are different things. Platform-specific time zones and restrictions appear in the notes. A past date indicates that the stated window has passed, not proof that a rollout finished in every account.
Use this calendar to assign a review owner. Calendar options create a copy for you to review and save. Copies do not update automatically. This page does not connect to advertising accounts or change campaigns.
Google Merchant APILast successful source review: 
