Meta Ads Updates (August 2026): What's Changing and What to Do

Every Meta Ads change that affects your campaigns, updated twice a month. August so far: EU AI-disclosure rules now cover ads delivered in Europe, three reporting breakdowns went opt-in and can return silently empty results, exclusion-only custom audiences arrived for suppression lists, WhatsApp marketing messages reached the Marketing API, ad accounts can be funded with USDC, and the Messenger Stories placement disappears from every API version late this month. Below: the full August rundown, July and June in full, action items for each, and the running deadlines table.

August 2026

The first half of August was about rules and reporting plumbing rather than shiny features. The EU's AI-disclosure obligations became binding for ads delivered in Europe, three Ads Insights breakdowns switched to opt-in with a silent failure mode, Meta published an official page for a new exclusion-only custom audience type, WhatsApp marketing messages landed in the Marketing API, and the status page stayed clean: no ad-platform incidents logged between August 1 and 15.

EU AI-Disclosure Rules Now Apply to Ads Delivered in Europe (August 2)

On August 2, the transparency obligations in Article 50 of the EU AI Act became legally binding. The advertiser-facing part: anyone deploying AI-generated or AI-manipulated content that resembles real people, objects, or events has to disclose it clearly, and providers must make AI content machine-detectable. Like the location fees, it applies based on where your ads are delivered, not where your business sits, and penalties run up to 15 million euros or 3% of worldwide turnover. Meta signed the EU's Code of Practice on Transparency of AI-Generated Content on July 28, five days before the deadline. The same day, California's AI Transparency Act took effect for large generative-AI providers (detection tools and hidden watermarks), which binds the tools you use rather than you directly.

Meta's plumbing is already moving: the August 5 update to its published API spec adds an is_ai_generated flag to video and photo publishing endpoints and a much larger set of AI-provenance labels for media. New York's synthetic-performer law in June was one state; this is every EU impression. If your creative pipeline generates human likenesses or realistic scenes, whether through Meta's tools or your own stack, build the disclosure step into production now and keep a record of what was labeled, rather than retrofitting under an enforcement letter.

Three Reporting Breakdowns Went Opt-In (August 6): Empty Data, No Error

A change Meta announced quietly in a May 8 out-of-cycle changelog entry took effect on August 6: the impression_device, hourly-stats, and frequency_value breakdowns in the Ads Insights API now require per-account enablement. The device restriction applies to any breakdown combination that includes it, so a routine device-by-placement query is caught too. The failure mode is the dangerous part: requests from non-enabled accounts still return a success response with an empty data array. No error, no warning, just dashboards rendering zeroes that look like a performance collapse.

The fix is quick once you know it exists. Pull a device or hourly report covering August 6 onward; if it comes back empty on an account that had data on the 5th, an account administrator can enable the breakdowns in Ads Manager, and asynchronous report jobs then return your full history. There is also a new insights/feature-settings endpoint for enabling accounts programmatically, which agencies with long client lists will want. If you build or buy reporting, treat an empty success response as a signal to investigate, not a number to write into a table, and if you routinely export your ads data, re-check any pipeline that leans on these three breakdowns.

Exclusion-Only Custom Audiences: A Permanent Do-Not-Target List (August 7)

Meta published an official Help Center page for exclusion-only custom audiences, a new customer-list audience type that can only ever be used to exclude people. It cannot include anyone, cannot seed lookalikes or value rules, and cannot be converted to a regular custom audience later; the designation is permanent at creation. Meta's stated use cases are the compliance ones: people who opted out of your services, people you have a legal or regulatory obligation not to target, and lists you want a hard guardrail around. It works through Ads Manager and the Marketing API, supports the new audience labels, and is unavailable for Special Ad Category campaigns.

The point of the one-way design is that nobody on the team can quietly repurpose a suppression list as a retargeting source later. If you maintain opt-out lists, litigation holds, or do-not-contact files, rebuild them as exclusion-only audiences so the guardrail is structural instead of a naming convention.

Meta AI Developer Assistant Is Now the Front Door for Developer Support (August 4)

Meta made its AI Developer Assistant the primary support path on the developer site, rolling out gradually and reaching all developers by mid-September. It answers questions about API errors, webhook configuration, permissions, app review, and business verification, grounded in current documentation. If you maintain a Marketing API integration, the practical change is that support tickets now start with an AI triage layer, so precise questions with error codes will get further faster than prose descriptions.

Fund Your Ad Account With USDC (Reported August 4)

Meta now documents stablecoin funding for ad accounts: advertisers in selected countries can add prepaid funds in USDC from a compatible wallet, a third-party partner converts it to local currency, and the amount lands as regular ad credit. Meta never holds the crypto, refunds come back as ad credit rather than USDC, and funds sent to a wrong address are unrecoverable. Irrelevant for most US and EU buyers, genuinely useful if you operate from a market where card payments to Meta fail or currency controls bite.

Granular Security Controls for AI Agent Access (Reported August 11)

Reported from the interface, no official page yet. Practitioners documenting the AI Connectors setup flow now see granular scoping: you can limit an AI agent to selected Pages, Instagram accounts, and business portfolios, manage roughly a hundred tool-level permissions in the Claude connector, and review everything from a new Ads MCP Server panel under Business Settings > Integrations. The detail worth checking today: several sensitive write actions, including budget changes and creating campaigns, ad sets, and ads, are reportedly enabled by default per account. If you connected an AI agent to your ad account since April, open that panel and confirm the write permissions match what you actually want an agent doing unattended.

WhatsApp Marketing Messages Join the Marketing API (August 13)

An August 13 out-of-cycle changelog entry makes WhatsApp marketing messages available through the Marketing API across all versions, covering ad-account reads, ad set and creative creation, and insights. If you run click-to-WhatsApp or messaging campaigns through tooling, the channel you previously managed in the UI is now scriptable end to end. One billing footnote from Meta's own FAQ: WhatsApp marketing messages invoiced together with ads do incur the location fees in the six affected markets.

Messenger Stories: Gone for Every API Version in Late August

A date conflict worth planning around conservatively. The v26.0 release removed the Messenger Stories placement for API calls on the new version, and Meta's two changelog pages now disagree on when it dies everywhere else: the Graph API changelog says October 27, while the Marketing API changelog says late August 2026, and advertiser notifications reportedly cite August 27. Treat the earlier date as the real one. If any placement array in your tooling or saved templates still names story under messenger_positions, strip it this week; on v26.0 the value is already silently dropped from a successful response rather than erroring.

The API Corner: Docs-Only Changes in the August 5 Spec Capture

Meta's biweekly API spec capture on August 5 carried a batch of changes that appear in no blog post. The ones that touch real workflows: the four marketing_messages_website_* conversion fields were removed from Ads Insights while instagram_profile_follow was added; the old feature_preferences endpoint gave way to the insights/feature-settings machinery behind the August 6 breakdown opt-ins; five call-to-action values were removed, including SEE_MENU and GET_UPDATES; ad sets gained an anchor_event_attribution_window_days field; and brand-safety configs picked up per-platform comment-moderation filters for Facebook, Instagram, and Threads. Separately, the Marketing API v26.0 changelog now flags that country and location_spec inside lookalike_spec are deprecated, with all versions cut over on September 1; the fields are silently ignored and the lookalike's location comes from the ad set. If your tooling builds lookalikes with an explicit country, that is a three-week migration window.

Meta's Holiday Trio: The Q4 Playbook Posts (August 11-13)

Meta Business News published three holiday-planning posts in quick succession: turn on Advantage+ placements now so October acts as a learning period before Black Friday, run three or more creative formats matched to the four phases of the season (Meta's data puts purchase intent 2.1x higher when shoppers engage with three-plus formats), and set up a Conversion Lift study before peak, when holiday volume gets results to significance in two to three weeks instead of six. Marketing content rather than product changes, but the sequencing advice is sound: whatever Q4 structure you plan to run should be live and learning before CPMs ramp.

Rollout Watch

Two July announcements still have not landed as of August 15. Muse Image remains outside Advantage+ creative; Meta's July 7 post still says "in the coming weeks" and no official confirmation of the rollout exists, so keep treating Muse-powered image variants as upcoming. And "Push Delivery to This Ad" still has no official Meta documentation a month after reaching what trackers call full rollout; the July section's caveats stand unchanged.

What to Do After the Early-August 2026 Meta Ads Changes: Action Checklist

This week

• Pull a device, hourly, or frequency report covering August 6 onward; if it comes back empty, opt in via Ads Manager and backfill with an async report job.
• Strip story from any messenger_positions placement arrays before the late-August cutoff.
• If AI-generated likenesses appear in creative delivered to the EU, stand up the disclosure step now.

This month

• Review the Ads MCP Server panel under Business Settings > Integrations and confirm which write actions your connected AI agents hold.
• Rebuild opt-out and legal suppression lists as exclusion-only custom audiences.
• If your tooling creates lookalikes with an explicit country or location_spec, migrate before September 1.

Before next quarter

• Get your Q4 structure live early enough to exit learning before Black Friday, and set up a Conversion Lift study before peak volume.
• Messaging stacks: scope the WhatsApp marketing-messages API surface alongside the October 15 Embedded Signup migration.

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.

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.

Profile-Visit Optimization Arrives in the Marketing API (July 20)

A docs-only addition we picked up from the out-of-cycle changelog after the July close: since July 20, ad sets created through the Marketing API can optimize for Instagram profile and Facebook Page visits, with optimization_goal set to PROFILE_VISIT or PROFILE_AND_PAGE_ENGAGEMENT and matching destination and call-to-action types, including a dual Instagram-plus-Facebook destination. Creator-adjacent and local-business tooling that could only build these ads in the UI can now script them.

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_account webhooks, 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.

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.

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は複製したクリエイティブを「新規」として扱わないんですよね。

入稿上は別のIDでも、過去の配信履歴を引き継いだ状態で配信が始まる。
つまり摩耗の途中からの再スタート。

これが実績にどう出るか。

出し直した直後はCTRもCVRも一時的に回復する。
管理画面だけ見れば復活に見えるわけだが、…

— 野嶋友博@オプト (@LAPPER_s_HIGH) July 4, 2026

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.

Upcoming Meta Ads Deadlines

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 August 2026?

The first half of August was rules and plumbing. The EU AI Act's transparency obligations became binding on August 2, so deepfake-style AI content in ads delivered to EU users now needs a clear disclosure. On August 6, the device, hourly, and frequency reporting breakdowns switched to per-account opt-in and return empty results, not errors, for accounts that never enabled them. Meta also published an official page for exclusion-only custom audiences, added WhatsApp marketing messages to the Marketing API, documented USDC stablecoin ad-account funding, and made its AI assistant the front door for developer support.

Why are my device, hourly, or frequency breakdowns suddenly empty?

Since August 6, 2026, the impression_device, hourly-stats, and frequency_value breakdowns in the Ads Insights API only return data for ad accounts that have opted in, and the device restriction applies to any breakdown combination that includes it. Requests from non-enabled accounts still return a success response with an empty data array, so dashboards show zeroes instead of raising an error. An account administrator can enable the breakdowns in Ads Manager, and asynchronous report jobs then return your full history.

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:

• May 2026: Marketing API access tiers overhauled, Embedded Signup v4, Threads brand-safety block lists, legacy Advantage+ API deprecation landed, Graph API v19 expired
• 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