Blog4 min read

The platform changes that cost you money are silent

Meta flipped Shop destinations on by default, removed Explore as a placement, and is deleting the delivery forecast fields your dashboard runs on.

It is Tuesday morning. The reported conversion rate on your shopping campaigns has slipped since Friday. Nobody paused anything. Budgets are flat. The creative is the same and so is the audience. You open the change log in Ads Manager and it is empty. You check it twice, because an empty change log feels like a broken report.

Nothing broke. Something moved underneath you, and it was built to need no approval from you. This is the part of platform risk that teams on 8 and 9 figure budgets keep underrating. The expensive changes are rarely the loud deprecations. Those get a post, an argument in a group chat, and a fix by Thursday. The expensive ones arrive as a default you never set.

The default that flips itself on

The Meta Graph API and Marketing API v26.0 changelog is the clearest recent case. That release landed on 29 July 2026. Eligible Shop Ads creatives now default to a destination_type of WEBSITE_AND_SHOP. Destination type just means where the click lands. Unless you write the opt out value into the ad, traffic can start splitting to a Shop destination you never chose.

Look at what that does to a number you report on. A Shop destination is a different buying surface with different friction. Your measured conversion rate moves. Your cost per purchase moves. Nobody on the team touched the campaign, so nobody goes hunting for a cause. The likely ending is a buyer calling it creative fatigue and killing a winning ad.

A default you never chose is still a decision. Meta made it. Your report carries the result.

The same changelog carries a quieter item. Instagram Explore Feed is removed as a placement, so explicit requests for it now error. The story value under messenger_positions is dropped silently. Two things follow. Any Explore exclusion still sitting in your templates now means nothing at all. And your placement level reporting has a gap that no alert will raise.

The fields your dashboard runs on

Same changelog again. Meta removed daily_outcomes_curve, budget_guardrail and estimate_dau from Delivery Estimate, with no replacement. Delivery Estimate is the endpoint that tells you what a budget should buy before you spend it. Removal across all API versions completes on 27 October 2026. Graph API v20.0 is removed on 24 September 2026.

Read that first date again. 27 October 2026 sits in the middle of peak season. If your pacing sheet or your in house forecasting tool calls those fields, it starts coming back empty during your heaviest weeks. That is not a deprecation you schedule into a sprint. That is a Sunday night in November staring at a blank column.

The Meta Marketing API v25.0 changelog, dated 18 February 2026, did something similar to campaign structure. Advantage+ Shopping and Advantage+ App campaigns can no longer be created, duplicated or updated, with enforcement from 19 May 2026. Advantage+ Shopping is Meta's automated shopping campaign type. Duplicating a winner is gone as a scaling move. Worse for anyone reading history, your old comparisons against business as usual stopped being comparable at the cutover.

The obvious objection

Here is the strongest case against me. None of this is secret. Every item above sits in a published Meta changelog with a date on it. If your team missed it, that is a process failure, not a platform ambush. Hire someone who reads release notes. I accept most of that. The changelogs are public and the dates are real.

The problem is who the notice actually reaches. These notes are written for developers and they land in a developer's inbox. The person whose number moves is a buyer looking at a dashboard. Nothing inside the account tells that person a default changed last week. Public is not the same as noticed. A change is silent when it is silent where the money is.

There is a second version of the objection and it is fair. Meta is testing removal of ad set level exclusions for placement, platform, device and operating system, starting with Sales and Leads objectives. Jon Loomer Digital covered this on 20 August 2026. Loomer's position is that value rules, which bid a segment down rather than cutting it, are an adequate replacement. He may be right about the performance. It is still a change you want to find before your client finds it.

What to do Monday

  • Pull every active Shop Ads creative and read destination_type. If it says WEBSITE_AND_SHOP and you did not pick that, set the opt out value.
  • Search your templates and saved setups for Explore exclusions. Delete them. They do nothing now.
  • Search your reporting code and sheets for daily_outcomes_curve, budget_guardrail and estimate_dau. Anything that calls them needs a plan before 27 October 2026.
  • Check which Graph API version your connectors and partner tools run on. v20.0 is removed on 24 September 2026.
  • Write your Advantage+ campaign cutover date into your reporting notes. Any trend line crossing it is not like for like.

Then put a standing thirty minutes on one person's calendar to read the Meta changelog. It is dull work and it is easy to skip. It is also the only alarm you get.

Let's talk about
growing your revenue.

Bring your goal and your numbers. You leave the first call with our first ideas, a clear scope and what we would test first.

Scale your business