Meta Removed Placement Exclusions: Your Brand-Safety Block Is Now a 90% Bid Cut
Exclusions left the ad set level
An in-product notice started appearing across Ads Manager accounts in the second half of August 2026: advertisers can no longer exclude individual ad placements, platforms, devices, or operating systems at the ad set level. The checkboxes that let you keep Facebook Feed and drop Audience Network, or run iOS only, are going away.
Before, a placement you unchecked never served and cost you nothing. What replaces that is a value rule: you bid a placement or a device class down, and the reduction is capped at 90 percent. A placement can be made expensive to win. It cannot be made impossible to win, because it still enters the auction at a tenth of your normal bid, and in any auction where nobody outbids you, it serves and it spends.
Hard blocks still exist. They moved up to account-level settings, where the publisher block list, content type exclusions, and inventory filter all work the way they did before. The difference is scope: one setting, every campaign in the account, no per-campaign variation.
This is broader than the Advantage+ change most teams already absorbed. Placement allocation inside Advantage+ was the price of opting into automation. This applies across campaign types, including the manual campaigns people kept specifically to retain that control.
Find every ad set that depends on an exclusion
Bulk export is the fastest path. Select all campaigns in the account, export at the ad set level, and the resulting sheet carries placement, device, and operating system columns. Flag three groups: any ad set whose placement field is not the full automatic set, any ad set restricted to iOS or Android, and any ad set with an operating system value.
The interface filter gets you most of the way too. In the ad set list, filter by placement type and pull the ad sets that are not on fully automatic placements. That view misses ad sets carrying only a device restriction, so use the export as the source of truth and the filter as a spot check.
Then sort what you found by why the exclusion exists. Brand safety exclusions were built to keep creative away from certain inventory, and they get rebuilt at account level. Performance exclusions came out of a report showing a placement with bad CPA, and they become value rules. Technical exclusions cover things like a checkout flow that breaks on older Android browsers, and they need a fix on your site or an accepted leak. Handling all three the same way is how accounts break.
What rebuilds cleanly and what does not
| Old ad set setting | Where it goes now | Equivalent? |
|---|---|---|
| Block a specific publisher or app | Account-level publisher block list | Yes, but account-wide |
| Exclude sensitive content categories | Account-level inventory filter and content type exclusions | Yes, account-wide |
| Exclude Audience Network | Value rule at a 90% bid reduction | No, residual spend continues |
| iOS only, no Android | Value rule bidding Android down | No, Android still gets delivery |
| Campaign A blocks Reels, campaign B keeps it | Account-level is all or nothing | Not reproducible |
That last row is the one with no replacement anywhere. Account-level blocks apply to every campaign, so two product lines with different brand-safety requirements cannot coexist under one ad account any more. A baby-care line that needs strict inventory rules and a hardware line that does not now pull in opposite directions on a single switch.
The only real workaround is a second ad account for the stricter line. That costs you pixel history, custom audience overlap, and a fresh learning phase on every campaign you move. It is a decision to make now rather than in the middle of November, when the learning phase is the most expensive thing you own.
Audience Network needs its own plan
Turning off Audience Network has been a standing habit for DTC advertisers running US and EU traffic, on the grounds that the click quality is poor and accidental taps inflate the numbers. That switch is gone.
What you still have is a bid floor, a block list, and your own reporting. Build a value rule in the ad set’s optimization and delivery settings that bids Audience Network down by 90 percent, which is the floor. Submit your specific low-quality apps to the account-level publisher block list and set the inventory filter. Then break your reporting out by placement every week and watch what Audience Network actually costs you.
The weekly placement report is what tells you whether the first two steps were enough. A 90 percent bid reduction does not mean zero spend, and the only way to know the residual is to read it. Pull spend, conversions, and cost per conversion by placement. Under roughly 3 percent of spend, treat it as leakage and move on. Above 8 percent with poor conversion quality, the second-account option stops being theoretical.
Creative needs a hedge as well. Inventory you cannot block means some share of your budget runs as interstitials and banners inside third-party apps, where a vertical Reels-native asset reads badly. Have one low-density, large-subject variant in rotation before Q4 volume arrives.
A three-week runway before Q4
Week one is inventory. Export every ad set, sort into the three groups, and calculate what share of account spend flows through ad sets that depend on an exclusion. Under 10 percent means this is an afternoon of work. Above 40 percent means it needs a real project plan and a named owner.
Week two is the account-level rebuild. Merge the brand-safety group into a single account-wide block list and allow at least 48 hours before you judge whether it took effect. You will hit conflicts, where one campaign’s blocked publisher is another campaign’s best converting source. Log each conflict rather than resolving it silently, because that log is the input to the second-account decision.
Week three is value rules and verification. Convert the performance group, let it run three to five days, then compare the placement-level spend distribution against your pre-change baseline. Doing this in September buys you a cheap week of data. Discovering in November that a placement doubled its share of budget costs real money per day.
阅读本文中文版: Meta 取消了版位排除：你设的品牌安全屏蔽，现在只是把出价打了一折
Related Articles
It Is Not DSA Getting Auto-Upgraded to AI Max in September: It Is ACA and Broad Match
From September 2026, Search campaigns running automatically created assets or the campaign-level broad match setting are auto-upgraded to AI Max, with Google aiming to finish by the end of the month. The DSA upgrade slipped to February 2027. How to check scope in ten minutes and which controls survive.
Google PMax Channel-Level Reporting: See Where Every Ad Dollar Goes
Google Performance Max now offers channel-level reporting, letting advertisers see spend and performance across Search, Display, YouTube, Gmail, and Maps for the first time. This guide covers how to read the reports, optimize budget allocation, and what the Search Partners opt-out alpha means.
TikTok Symphony vs Meta Image-to-Video vs Amazon Video Generator: 2026 Comparison
TikTok, Meta, and Amazon all upgraded their platform-native AI video ad tools in 2026. Upload a product image and get a video ad in minutes — but the real-world output and use cases differ significantly across all three. Here is a direct comparison.