Every Meta Ads change that affects your campaigns, updated twice a month. July closed with the Graph and Marketing API v26.0 release and its batch of ad-API deprecations, a public ads MCP server for any developer, new ad-account webhooks that replace polling, an official Lead Capture AI agent for Instant Forms, the location fees now landing on invoices in six markets, and two Ads Delivery incidents. Below: the full July breakdown, June's Cannes commerce and AI push, May's plumbing changes, action items for each, and a running deadlines table on one bookmarkable URL.
July 2026
July was a developer-heavy month that still reached the account. The Graph and Marketing API v26.0 release on July 29 retired several ad placements and paths, Meta opened its ads MCP server to any developer and documented ad-account webhooks that replace API polling, the location fees started landing on invoices, an official Lead Capture AI agent arrived for Instant Forms, and the status page logged two Ads Delivery incidents.
| Date | Change | Impact | Who's affected |
|---|---|---|---|
| Jul 1 | Location fees now charged (UK 2%, FR/IT/ES 3%, AT/TR 5%) | High | Advertisers delivering in six markets |
| Jul 7 | Muse Image announced; Advantage+ creative rollout "in the coming weeks" | High | All advertisers using AI creative |
| Jul 9 | Lead Capture AI agent for Instant Forms goes official | Medium | Lead-gen advertisers |
| Jul 10 | "Push Delivery to This Ad" surfaced (no official page yet) | Medium | Advertisers running multiple ads per ad set |
| Jul 14 | Website custom audience retention: 365-day max appears in developer-doc FAQ | Medium | Retargeting and exclusion audiences |
| Jul 16 | Ads MCP server opened to all developers | Medium | Developers, ad tools |
| Jul 16 & 19 | Ads Delivery incidents logged on Meta's status page | Medium | All advertisers |
| Jul 22 | Ad-account webhooks documented as the replacement for API polling on ads changes | Medium | Developers, ad tools |
| Jul 27 | Meta Holiday Insights Center launched | Low | Small-business advertisers planning Q4 |
| Jul 29 | Graph and Marketing API v26.0 released with ad-API deprecations | High | Developers, ad tools, some advertisers |
Graph and Marketing API v26.0 (July 29): The Deprecations That Could Break Your Setup
On July 29, Meta shipped Graph API v26.0 and Marketing API v26.0, and the version changelog carries the most ad-facing batch of deprecations of the year. Several land on advertisers, not just developers: the Instagram Explore Feed is removed as an ad placement, so any campaign that hardcoded it now redistributes to other placements; the Advantage+ Audience flag must be set explicitly or calls fail; Shop Ads creatives default to a website-and-shop destination unless you opt out; poll ad creation and the Messenger Stories placement are deprecated; and web-only destinations are banned for Web-plus-App campaigns. Two more matter for tooling: the delivery-estimate fields (daily_outcomes_curve, budget_guardrail, estimate_dau) are gone, and the Commerce Order Management API is sunset with no replacement (47 endpoints, blocked in v26.0 now and across all versions on October 27). On the additive side, ads in WhatsApp Status expanded, with carousels up to 10 cards and offsite-conversion optimization for Sales, Leads, and Engagement.
The practical work is an audit, not a panic. Check which API version every integration is pinned to, since apps left on an unsupported version get force-upgraded into these changes without warning. Review any placement logic that named Explore or Messenger Stories, set advantage_audience explicitly wherever you build targeting, and put the October 27 Commerce Order Management cutoff on the calendar if you touch Shops order data.
Muse Image: Meta's New Image Model Is Heading Into Advantage+ Creative
On July 7, Meta introduced Muse Image, the first image generation model from Meta Superintelligence Labs, and the business post is explicit about where it lands: Advantage+ creative image generation, rolling out to advertisers and agencies "in the coming weeks". Meta says the model brings agentic reasoning and iterative refinement - it parses a creative brief, adjusts individual elements, swaps styles, and produces on-brand variations with fewer round trips. Meta cites more than 8 million advertisers already using its AI creative tools. As of the end of July, no official post confirms the Advantage+ integration has shipped, so treat it as announced-not-live and watch Advantage+ creative for the rollout.
Today, we’re introducing Muse Image: our first image generation model from Meta’s Superintelligence Labs. It uses advanced reasoning to understand prompts and lets you turn your ideas into high-quality, relevant visuals that you can share directly to your chat, story, or feed.…
— Meta Newsroom (@MetaNewsroom) July 7, 2026
This is the model layer underneath June's brand-memory announcement getting a serious upgrade, and it sharpens the same trade-off. Image variations get better and cheaper, which raises the output floor for everyone, while the delivery system keeps grouping structurally similar creative into one entity and one audience pool. When Muse variants hit your account, treat them as variation fuel inside a concept, not as new concepts. And if your creative uses AI-generated people, remember the New York disclosure law from the June section applies to Muse output too.
Meta Location Fees Are Now on Your Invoice (July 1)
The fees announced in March are now being charged: United Kingdom 2%, France, Italy and Spain 3%, Austria and Turkiye 5%, applied to impressions delivered in those countries regardless of where your business is based, billed as a separate line item outside your campaign budget per Meta's location fees help page. Your first invoices containing them arrive this month: reconcile the line item against delivery by country and reforecast Q3 CPMs for affected markets. Full breakdown in our Meta location fees guide.
Meta's Ads MCP Server Is Now Open to Every Developer (July 16)
On July 16, Meta announced that its ads MCP server is now available to any developer with their own Meta app. April's AI Connectors put a no-code MCP server in front of end users; this opens the build-your-own layer, so any AI application can let its users create and optimize campaigns, manage product catalogs, and pull performance data through natural language. Business portfolio administrators also get controls to scope how much access an AI agent gets.
The direction is consistent: Meta is making the ad account addressable by agents at every layer, from the end user who just wants to talk to their campaigns to the developer building the tool that does it. If you build software on top of Meta Ads, this is the sanctioned path to an AI interface without waiting on partner status. For the practitioner-facing version of the same shift, our Meta Ads MCP guide covers what the connectors do and where they fit.
Ad-Account Webhooks Now Replace Polling for Ads Changes (July 22)
Around July 22, Meta documented webhooks for ad accounts as the sanctioned way to get real-time notifications when ads change, instead of polling the API on a timer. The ad_account object now exposes standalone webhook fields: ad_recommendations (marked improved), creative_fatigue, in_process_ad_objects, with_issues_ad_objects, and product_set_issue. A new effective_status field, reported to fire on delivery blocks, policy rejections, and sync delays, appears in coverage of the launch but is not yet listed on Meta's field-reference page, so treat it as reported until the reference catches up. The same coverage puts the full ads subscription at more than 88 ad-object and insights notifications and says push delivery does not spend your rate-limit allowance on the receiving side; both of those figures come from the announcement rather than the reference doc, so hold them with that caveat. You turn a field on by subscribing your app, then authorizing the specific ad account.
The practical point for anyone running tooling on Meta Ads is that this is the way off polling loops. If your stack wakes every few minutes to diff ad statuses, recommendations, or fatigue, you can move that to push and stop spending rate limit on checks that usually return nothing. It fits the same month's agent-addressable direction and the v26.0 removal of the delivery-estimate fields: fewer scheduled reads, more event-driven reactions. Audit where you poll today and convert the noisiest loops first.
Custom Audience Retention: 365 Days Now Appears in Meta's Developer Docs
Still partially confirmed, reported here with that caveat. Meta's website custom audiences developer documentation, updated July 14, now states in its FAQ that "the longest duration can be set for 365 days" before audience members drop off unless they match the rule again. The catch is internal: the same page's retention_days API parameter still reads "between 1 and 180 days", and the Business Help Center gives no maximum number at all. So the 365-day figure is now in official documentation, but the API field and the Help Center have not caught up. The 730-day number circulating in practitioner posts appears nowhere official. If a full-year window holds, retargeting and exclusion audiences can reach a year of purchasers; until the field and Help Center align, build as if 180 is the enforced ceiling and revisit next update.
"Push Delivery to This Ad": Steer More Delivery Toward One Ad You Choose
Around July 10 a new "Push Delivery to This Ad" option began appearing, and it looks fully rolled out. It lets you push more of an ad set's or campaign's delivery toward one specific ad you select, rather than leaving the split entirely to Meta's delivery system. We are noting it from what advertisers are seeing in the interface. Meta has not published a help page for it yet, so treat the exact mechanics as provisional and watch for official documentation to confirm the details.
The trade-off is a familiar one. Meta's delivery system optimizes the ad split on signal you cannot see, so overriding it toward a favorite can help when you have a clear winner the system is under-serving, and hurt when your read is worse than the algorithm's. If you try it, change one variable, give it enough spend to judge fairly, and compare against an ad set where you left delivery alone.
Lead Capture AI Agent for Instant Forms: Meta Turns the Form Into a Conversation
The conversational lead flow that practitioners started spotting in early July is now official. Meta's Lead Capture AI agent for instant form ads Help Center page documents it: instead of always showing a static form, Meta decides per person whether an AI chat or the standard form is more likely to convert, and the agent asks and follows up in a back-and-forth to collect the lead. Meta says conversations are not stored, only the final submitted lead is shared. You turn it on with an ad-level "Enable lead capture AI agent" toggle. At launch it is English-only, does not support conversion-leads optimization, conditional logic, or appointment requests, and is gated for regulated verticals like financial services, health, and employment/housing/credit.
This is the natural next step after June's embedded appointment booking: Meta is turning the Instant Form from a form into a conversation. A chat-style capture can lift completion when a static form feels like work, but it also hands your qualifying questions to an AI, so if you test it, read the transcripts and check lead quality, not just lead volume, before you scale it. The regulated-vertical exclusions are the tell about where Meta is least confident, so keep that flow static if you sell in one of them.
Ads Delivery Incidents on July 16 and 19, 2026: When to Suspect the Platform
Meta's status page logged Ads Delivery incidents on July 16 and July 19, both since resolved. The July 19 event lined up with a wider Facebook and Instagram disruption that users reported in the early hours, US time. No Ads Manager, Ads Reporting, or Marketing API incidents were logged in the window beyond these two.
If delivery or pacing looked off on either day, that is the first place to check before you touch a campaign. Annotate both dates in your reporting so a delivery dip does not get mistaken for creative fatigue or an audience problem, and as a standing habit on odd days, read the status page's Ads section first, then trust your own MER and CRM numbers over in-platform reporting on incident days.
Meta's 2026 Holiday Insights Center: Plan Q4 Before the CPM Ramp
On July 27, Meta launched a 2026 Holiday Insights Center, a free hub of consumer research and platform benchmarks aimed at small businesses getting ready for the holiday season. It is a marketing resource, not an ad-mechanics change, but the timing is the useful part: it is the cue to lock your Q4 plan before auction prices climb into the back-to-school and holiday windows. Build your creative and budget calendar now, while CPMs are still at their summer floor.
Meta Reported Q2 2026 Earnings (July 29): Price per Ad Up 12% Again
Meta's Q2 2026 results, reported July 29, put average price per ad up 12% year over year, the second consecutive quarter at that rate, on 14% more ad impressions delivered. Ad revenue reached $59.36 billion, up 27%. For advertisers the regional split matters more than the blend: price rose 20% in US & Canada against 1% in Asia-Pacific. The full quarter-by-quarter read, and what it means for your CPMs, is in our Meta earnings for advertisers tracker.
What to Do After the July 2026 Meta Ads Changes: Action Checklist
This week
- Confirm which Graph and Marketing API version every integration is pinned to before an unsupported version force-upgrades you into the v26.0 changes.
- Annotate July 16 and 19 in reporting dashboards as platform delivery incidents.
- Check any campaign that named the Instagram Explore Feed or Messenger Stories placement; both are gone in v26.0.
This month
- Set the Advantage+ Audience flag explicitly anywhere your tooling builds targeting.
- Lead-gen: test the official Lead Capture AI agent against your current static form, and read the transcripts for quality, not just volume.
- Reconcile the location-fee line items on your July invoices against delivery by country.
- Developers: move status, recommendation, and fatigue polling to
ad_accountwebhooks, and stop spending rate limit on checks that return nothing.
Before next quarter
- Calendar the October 27 Commerce Order Management API cutoff if you touch Shops order data.
- Lock your Q4 creative and budget plan before holiday CPMs climb.
- Watch for the Muse Image rollout into Advantage+ creative and plan variations as concept fuel, not new concepts.
Launch More. Click Less.
Upload hundreds of creatives at once, auto-match thumbnails to videos, and export directly to Meta Ads Manager.
Try Ads Uploader FreeNo credit card required • 7-day free trial
June 2026
June was Meta's loudest month of 2026 so far. A Cannes double-header pushed commerce and AI creative hard, a quiet privacy-settings change widened what your Pixel data personalizes, two API deadlines landed, and Ads Manager had its roughest day of the year.
| Date | Change | Impact | Who's affected |
|---|---|---|---|
| Jun 3 | Meta Business Agent announced (Conversations 2026) | Medium | Click-to-message advertisers |
| Jun 9 | Off-Meta activity control replaced; business data personalizes Feed and AI | High | All advertisers |
| Jun 9 | Marketing API v23.0 sunset | High | Developers, ad tools |
| Jun 12 | Ads Manager multi-component incident + Marketing API incident | Medium | All advertisers |
| Jun 16 | Cannes: Live Video Ads, virtual-card checkout, affiliate expansion | High | Ecommerce and retail |
| Jun 22 | Nielsen DMA to Comscore cutoff for automotive model ads | High (niche) | Automotive advertisers |
| Jun 23 | Lead ads: embedded appointment booking in Instant Forms | Medium | Lead-gen advertisers |
| Jun 23 | Cannes: AI creative suite with brand memory, translations, Creator Marketing Hub | High | All advertisers |
| Jun 30 | Developer Tools MCP | Medium | Dev teams, API tools |
Meta's "Activity From Other Businesses" Change: Your Pixel Data Now Personalizes Feed and AI
On June 9, Meta announced it is retiring the "Your activity off Meta technologies" control. The activity that businesses share with Meta through tools like the Pixel and Conversions API will now personalize Feed recommendations and Meta AI responses as well as ads, all governed by a single "Activity from other businesses" setting. The change starts rolling out in July 2026 in the US and other countries. Meta says no new data is collected; existing signals are being used on more surfaces.
This cuts both ways. The events you already send now influence organic and AI surfaces, which should compound the value of clean signal setup without you configuring anything. At the same time, it is a new, simpler opt-out surface: users who never found the old control will see the new one. Signal quality work keeps rising in value while the audience that allows it may narrow slightly at the edges. Nothing to change in your setup this week, but if you handle customer privacy questions, brief that team on the new setting's name and scope.
Meta Live Video Ads and Virtual-Card Checkout: The June 2026 Commerce Push
Meta's first Cannes announcement was a commerce package: Live Video Ads expanding globally on Facebook and Instagram with in-stream product browsing, virtual one-time card numbers with Mastercard and Visa rolling out to checkout this summer, and affiliate-creator expansion into 22 countries with retail partners across India, Brazil, Mexico and Southeast Asia.
The line that matters most sits lower in the post: product data becomes "foundational" across all Sales campaigns this summer, with Meta's AI matching products to likely buyers even outside catalog-first formats.
Catalog hygiene is no longer just a catalog-ads concern. If your feed has stale prices, missing attributes, or thin product data, that quality now propagates into every Sales campaign. Fixing the feed is the highest-leverage boring task on this month's list. Live Video Ads are worth a structured test if you sell demonstrable products, but treat the virtual-card checkout as a signal of where Meta wants transactions to happen: closer to the ad, with less friction and more measurable purchases.
Meta AI Creative Suite and Brand Memory: What Launched in June 2026 (And Why Distinct Concepts Still Win)
A week later Meta announced an end-to-end AI creative suite. The centerpiece is "brand memory": generation that learns from your existing ads so output stays on-brand, launching first through an agency integration and reaching broader rollout "in the coming months". Alongside it: text-on-media translation in five languages, AI video voiceover in eleven, an in-platform creative approval workflow in testing, and a Creator Marketing Hub that merges Creator Marketplace with the Partnership Ads Hub and adds Facebook creators later in 2026.
The floor for creative volume keeps dropping, which makes the Andromeda logic from April more important, not less. When everyone can produce brand-consistent variations cheaply, structurally distinct concepts remain the scarce input, because the delivery system groups lookalike creative into one entity and one audience pool. Practitioners are already documenting the sharp edge of that mechanic: duplicating a creative under a new ID does not reset its delivery history, so the "fresh" ad restarts mid-fatigue, recovers briefly, then decays faster than the original. That observation, from a Japanese media buyer at a major agency, was one of the most-shared operator posts of the window:
Metaは複製したクリエイティブを「新規」として扱わないんですよね。
— 野嶋友博@オプト (@LAPPER_s_HIGH) July 4, 2026
入稿上は別のIDでも、過去の配信履歴を引き継いだ状態で配信が始まる。
つまり摩耗の途中からの再スタート。
これが実績にどう出るか。
出し直した直後はCTRもCVRも一時的に回復する。
管理画面だけ見れば復活に見えるわけだが、…
Rough translation of the key point: "Meta does not treat a duplicated creative as new. Even under a different ID, delivery starts with the past delivery history carried over, so you are restarting mid-decay. CTR and CVR recover briefly after a re-upload, and the dashboard makes it look like a comeback." Duplication is maintenance, not testing. Budget your pipeline for genuinely new concepts.
Facebook Lead Ads Appointment Booking: The Instant Forms Update That Closes the Show-Rate Gap
Meta added embedded appointment booking to Instant Forms. Paste a scheduling link and a calendar widget loads on the thank-you page with the lead's contact details pre-filled. Calendly and HighLevel work at launch, HubSpot arrives in early August, and global availability is expected in October. On Instagram and other unsupported placements, leads get a "Book time" button that opens the scheduler in an in-app browser.
The biggest leak in lead-gen funnels is the gap between form submission and a booked call, and this closes most of it for services businesses. If you run lead ads with any appointment-based follow-up, this is the single most testable change of the month: same campaign, booking link added, watch show-rate. Setup details for forms are in our Instant Forms guide.
Meta Business Agent: AI Now Answers Your Click-to-Message Ads
At Conversations 2026, Meta introduced Meta Business Agent, an AI agent that answers customers, recommends catalog products, qualifies leads, and closes sales across WhatsApp, Messenger, and Instagram. It is expanding globally to businesses of all sizes, free at first with paid membership tiers planned "within months", and Shopify and Zendesk integrations are on the roadmap.
If you spend on click-to-message, the responder on the other end of that spend can now be Meta's own agent. That can lift conversion on volume you currently drop after hours, but it also puts an AI in front of paying customers with your brand on it. Test it on a low-risk segment, read the transcripts, and note the pricing signal: free is a launch state, not the deal.
Meta Ads Manager Outage on June 12, 2026: Why That Day's Numbers Look Wrong
Meta's status page logged simultaneous incidents across Ads Creation and Editing, Ads Reporting, and Ads Delivery on June 12, alongside a Marketing API incident, all since resolved. Smaller single-component Ads Delivery incidents were also logged on May 5 and June 23.
Annotate June 12 in every reporting dashboard the way you annotated the March 3 attribution change. If delivery, editing, or reporting looked broken that day, it was the platform. And as a standing habit when delivery behaves oddly: check the status page's Ads section first, then verify against your own MER and CRM numbers rather than trusting in-platform reporting alone on incident days.
Meta API Changes June 2026: v23 Sunset, Comscore Cutoff, and What Could Break Your Setup
Three dated items for API teams. Marketing API v23.0 sunset on June 9; apps pinned to it were force-upgraded, and v24.0 follows on October 6, so put the migration on the calendar now. For automotive advertisers, Nielsen DMA targeting stopped working on June 22: campaigns still using DMA codes stop delivering until they move to Comscore Markets. And on June 30, Meta shipped a Developer Tools MCP, an MCP server that lets AI coding agents query Meta's developer platform for API discovery, error troubleshooting, app health, and compliance deadlines.
April made the ad account agent-addressable; June did the same for the developer platform. The practical win is mundane and real: an agent that can look up why a call failed and which deadline is about to break your integration shortens exactly the kind of debugging that eats afternoons.
New York's Synthetic Performer Law: AI Ad Disclosure Required From June 9, 2026
Not a Meta change, but it lands on Meta advertisers. New York's synthetic performer disclosure law took effect on June 9, 2026: the first US state law requiring a conspicuous disclosure when an ad uses an AI-generated human performer. It applies based on where the ad is seen, not where your business sits.
This collides directly with the AI creative wave above. If your pipeline generates human likenesses, whether through Meta's new tools or your own stack, ads delivered in New York need a disclosure workflow now, and more states are expected to follow the template. Get legal's read on your AI creative before scaling it, and label proactively rather than retrofitting under enforcement.
What to Do After the June 2026 Meta Ads Changes: Action Checklist
This week
- Reconcile the new location-fee line items on your first July invoices against delivery by country.
- Annotate June 12 in reporting dashboards.
- Confirm which Marketing API version every integration is pinned to.
- If any live creative uses AI-generated people, flag New York delivery for disclosure review.
This month
- Clean your product feed: data quality now propagates into all Sales campaigns, not just catalog formats.
- Lead-gen: test embedded appointment booking against your current thank-you flow.
- Brief support and compliance teams on the "Activity from other businesses" setting.
Before next quarter
- Build the creative pipeline around distinct concepts, not variations; brand-memory tools will make sameness cheaper and therefore more common.
- Evaluate Meta Business Agent on a low-risk message segment before pricing arrives.
- Plan the v24.0 migration ahead of the October 6 sunset.
May 2026
May was a plumbing month. Nothing changed in the ads you see, but the access rules underneath every ad tool shifted, two legacy API paths hit their end dates, and Threads picked up brand-safety controls.
| Date | Change | Impact | Who's affected |
|---|---|---|---|
| May 4 | Marketing API access tiers overhauled | High | Developers, ad tools |
| May 14 | Embedded Signup v4; v2/v3 deprecation set for Oct 15 | Medium | Messaging and CTWA stacks |
| May 18 | Brand-safety block lists extended to Threads Feed ads | Medium | Brand advertisers |
| May 18 | metastatus.com adds a dedicated Ads section | Low | Anyone triaging delivery issues |
| May 19 | Legacy Advantage+ Shopping and App campaign API deprecation landed | High | Developers |
| May 21 | Graph API v19.0 expired | Medium | Developers |
Marketing API Access Tiers Update (May 2026): Full Access Just Got Easier
An out-of-cycle Marketing API changelog entry overhauled access tiers. "Ads Management Standard Access" is now the "Marketing API Access Tier", with "Standard" relabeled "Limited access" and "Advanced" relabeled "Full access". The auto-approval threshold for full access dropped from 1,500 to 500 calls in 15 days, the error-rate requirement is now assessed on a rolling 500-request window (below 15%), and the screen-recording requirement was dropped from tier-upgrade applications.
Full access got meaningfully easier for small tools and in-house scripts, which is good news if you have ever been stuck in limited-access purgatory. The flip side is that a rolling error-rate window punishes sloppy retry logic faster. If you run anything against the Marketing API, check your current tier label (it changed under you) and your error rate.
Meta API Deadlines That Landed in May 2026: ASC/AAC Deprecation and v19 Expiry
The May 19 deprecation of the legacy Advantage+ Shopping and App campaign API paths, flagged here since March, took effect: creation, duplication, and updates through the old paths are done. Graph API v19.0 expired two days later on May 21. If a script or third-party tool started failing mid-May, these two dates are the first suspects.
Threads Ads Brand Safety Update (May 2026): Block Lists Remove the Adoption Blocker
Meta extended third-party content block lists to Threads Feed ads, with DoubleVerify, IAS, Scope3, and Zefr supported at launch and Channel Factory and Protected by Mediaocean onboarding in the coming months.
If brand-safety controls were the reason Threads placements stayed off your plan, that reason expired in May. Threads inventory is still cheap relative to Feed; a controlled placement test is now defensible to the most conservative brand team.
Save Hours on Creative Testing
Stop uploading ads one by one. Bulk process unlimited creatives with automatic media matching and direct API publishing.
Try Ads Uploader FreeNo credit card required • 7-day free trial
Other May 2026 Meta Updates
Meta added a dedicated Ads section to its status page on May 18, grouping Ads Manager, Marketing API, Messaging Ads, Catalog, Audience Network, Instagram Boost, and Shops in one place; it earned its keep on June 12. For messaging stacks, Embedded Signup v4 arrived on May 14 with v2/v3 deprecation set for October 15: most integrations auto-upgrade, but only_waba_sharing, marketing_messages_lite, and coex flows need manual migration. And metastatus logged a single-component Ads Delivery incident on May 5, since resolved.
What to Do After the May 2026 Changes: Action Checklist
This week
- Check your Marketing API tier label and rolling error rate against the new thresholds.
This month
- If any automation still references legacy ASC/AAC paths or v19, treat every mid-May failure as this and migrate.
- Bookmark the status page's Ads section next to this page.
Before next quarter
- Messaging/CTWA stacks: calendar the October 15 Embedded Signup migration and check whether your flow auto-upgrades.
Upcoming Meta Ads Deadlines
| Date | Deadline | Who needs to act |
|---|---|---|
| Summer 2026 | Virtual-card checkout rollout; product data becomes foundational to all Sales campaigns | Ecommerce advertisers |
| Oct 6, 2026 | Marketing API v24.0 sunset | Developers, API tools |
| Oct 15, 2026 | Embedded Signup v2/v3 deprecation (v4 migration) | Messaging and CTWA stacks |
| Oct 27, 2026 | Commerce Order Management API and Messenger Stories placement sunset across all versions | Shops and commerce developers |
| Late 2026 | Facebook creators join the Creator Marketing Hub | Creator and partnership teams |
| Feb 3, 2027 | Developer policy 10.6.a: spend-and-fee transparency on advertiser request | Agencies, resellers, ad-buying platforms |
Keep Up Without the Noise
The pattern across these months is consistent. Meta is automating setup, opening the ad account and the developer platform to AI agents, pushing commerce closer to the ad, tightening transparency for resellers, and putting hard dates on legacy API paths. The advertisers who win are the ones who treat the "small" help-center notes and API deadlines as the real roadmap, not trivia.
When you are testing more creative concepts, across more placements and markets, at this pace, the bottleneck stops being strategy and starts being launch consistency. That is the problem bulk launching with Ads Uploader is built to remove, so your time goes to the decisions that move performance.
Frequently Asked Questions
What changed in Meta Ads in June 2026?
June was Meta's busiest month of 2026 so far. Two Cannes announcements brought Live Video Ads, virtual-card checkout, an AI creative suite with brand memory, and a unified Creator Marketing Hub. Meta also replaced the off-Meta activity control so business-sourced data now personalizes Feed and AI, sunset Marketing API v23.0, added embedded appointment booking to lead ads Instant Forms, launched Meta Business Agent, shipped a Developer Tools MCP, and had a multi-component Ads Manager incident on June 12.
Are the Meta location fees in effect now?
Yes. The fees announced in March took effect July 1, 2026: United Kingdom 2%, France, Italy and Spain 3%, Austria and Türkiye 5%. They are charged on impressions delivered in those countries, not where your business is based, and appear as a separate line item on top of your ad spend, outside your campaign budget. A $100 delivery to Italy bills as $103.
What is the Activity from other businesses change?
From July 2026, starting in the US and other countries, Meta is retiring the old "Your activity off Meta technologies" control. Data that businesses share through tools like the Pixel and Conversions API now personalizes Feed recommendations and Meta AI responses as well as ads, all governed by a single "Activity from other businesses" setting. Meta says no new data is being collected; existing signals are being used on more surfaces.
What are Meta Ads AI Connectors?
They are a secure, Meta-authenticated bridge between your ad account and an AI agent, made up of an ads MCP server and an ads CLI. The MCP server needs no developer credentials, API setup, or coding, so you can create, edit, report on, and troubleshoot campaigns from AI tools you already use. The CLI is built for developers and automated pipelines, with resources created paused by default. In June, Meta extended the same idea to its developer platform with a Developer Tools MCP.
Do I need to do anything about the AI-enriched Meta Pixel?
Yes. Existing Pixel users get a notification with a 30-day window before the AI enrichment feature turns on. Use that window to review which page and product data categories will be shared, confirm none of it is sensitive, and decide whether to keep it on. You can adjust or disable it any time in Events Manager.
What is the new Meta ad-buying transparency rule?
Under updated developer policy section 10.6.a, effective February 3, 2027, ad-buying solutions must disclose to an end advertiser, on request, the amount spent on Meta advertising separate from fees, the fee structure, and the campaign configuration, settings, and reporting in Meta terminology. It is a reactive model: disclosure is required when the end advertiser asks.
Did Meta Ads have an outage in June 2026?
Yes. On June 12, 2026, Meta's status page logged simultaneous incidents across Ads Creation and Editing, Ads Reporting, and Ads Delivery in Ads Manager, plus a Marketing API incident, all since resolved. Smaller Ads Delivery incidents were logged on May 5 and June 23. If your reporting or delivery looked strange on June 12, annotate it as a platform event rather than a campaign problem.
How often is this page updated?
Twice a month. This is a living page, not a series of separate posts. Early each month we finalize the previous month's section, and mid-month we fold in newly confirmed changes as they land. The newest month sits at the top, up to three months stay in full, and older months move to the yearly archive so you have one URL to bookmark.
Archive
Months roll off this page when more than three are live, and move to the archive in full so every link and detail survives:
- April 2026: AI Connectors open beta, AI-enriched Pixel and one-click CAPI, ad-buying transparency policy, Instagram API updates, the Andromeda creative-volume reality
- March 2026: click attribution redefined, location fees announced, Nielsen to Comscore migration, webhooks mTLS change
