Threads Is Now a Default Meta Ads Placement

The Threads ads placement is on by default in every active Meta campaign, globally. Meta announced the change on October 19, 2026, and Common Thread Collective reports the full rollout completing the week of October 26 — this week. You did not opt in, and you can no longer fully opt out.

Why this matters

Threads CPMs run 20–40% below Instagram feed, per the same reporting. That sounds like good news and it is the problem.

Cheap impressions pull your blended CPM down. Your account-level efficiency numbers improve while the mix of where your money actually goes shifts underneath them. Nothing in Ads Manager's default view tells you the improvement came from a placement you never chose.

This is the exact shape of a weekly read that looks fine and isn't. It lands four weeks before BFCM, which is the worst month of the year to be wrong about which placement is carrying your spend.

What changed, exactly

Lever	Before	Now
Threads in a new campaign	Opt-in placement	On by default
Threads in an already-running campaign	Not included unless selected	Added automatically
Excluding Threads entirely	Placement exclusion checkbox	Not available
Strongest remaining lever	n/a	Placement value rule, bid cut capped at 90%
Visibility in default reporting	n/a	None — requires a placement breakdown

The removal of placement exclusions happened in August, quietly, and it is the reason this month's change is not reversible. PPC Land reported on August 26, 2026 that advertisers were seeing the placement exclusion control disappear, with no official Meta announcement. Bram Van der Hallen of Edge.be, quoted in that piece, flagged it on LinkedIn:

"Some advertisers are seeing the ad placements control being removed." — Bram Van der Hallen, via PPC Land

He added that he had not seen it on his own accounts yet. That detail matters: the exclusion removal rolled out account by account rather than all at once, so check your own ad sets instead of assuming. Open one, go to Placements, and see whether an exclusion option still exists. The answer varies by account and by objective.

What the 90% value rule does and does not do

The replacement for exclusions is a value rule: at the ad set level, under Placements, choose to adjust bids for placements and set a decrease for Threads. PPC Land states the constraint plainly:

"A bid decrease under value rules cannot exceed 90%, so a placement can be made expensive to win but never made impossible to win." — PPC Land

Read that twice before you call it a fix. A 90% bid cut on a placement whose CPMs are already 20–40% cheaper than Instagram feed does not take Threads to zero. It takes it to a trickle that still shows up in your numbers. Common Thread Collective's framing is the same: the rule "will dramatically limit how much budget flows to Threads, but it does not eliminate it entirely."

So the honest posture is not "turn it off." It is: find out what it is costing you, decide whether that is acceptable, and only then reach for the bid cut.

See your Threads line in 15 minutes

Ads Manager does not surface this by default. You have to ask for it.

1. Open Ads Manager and set the date range to the last 7 days.
2. Open Breakdown → By Delivery → Placement. Meta documents this view in its help center.
3. Find the Threads row. Third-party guides report it appearing as a Threads feed placement alongside Facebook feed, Instagram feed, Reels and Stories.
4. Record four numbers for Threads: spend, impressions, CPM, and purchases or leads.
5. Repeat for the 7 days before October 19 and compare.

One caveat on the output: Meta notes in its breakdown specifications that placement values are estimated. Use them to size the problem, not to settle a dispute to two decimal places.

If step 5 shows a Threads row with meaningful spend and no conversions, you have a reallocation problem. If it shows a Threads row with cheap conversions, you have a new placement that is working — which also happens, and is the reason not to reflexively cut it.

A walkthrough: when the CPM improves and nothing else does

Illustrative numbers for a $30,000/month account, using the reported 20–40% CPM gap. These are modeled to show the arithmetic, not pulled from a specific account.

Metric	Week before rollout	Week after	Read
Spend	$7,000	$7,000	Unchanged
Blended CPM	$18.40	$16.95	↓ 8% — looks like a win
Impressions	380,000	413,000	↑ 9% — looks like a win
Purchases	142	139	Flat to slightly down
Blended CPA	$49.30	$50.36	↑ 2% — the actual signal
Threads share of spend	0%	11%	Invisible without the breakdown

Two of the three headline metrics improved. Volume went up, efficiency went up, and the business got slightly worse. An account-level scan this week returns a green light.

That pattern — cheaper impressions, flat conversions — is the standard signature of inventory expansion into a lower-intent surface. It is also why spotting wasted spend is a placement-level job, never an account-level one.

Act today / This week / Monitor

Act today

• Pull the placement breakdown for the last 7 days on every account. Write down the Threads spend share. If you only do one thing this week, do this one.
• Check whether a placement exclusion option still exists in your ad sets. Document the answer per account — it is not uniform.
• Freeze any CPM-based or CPM-triggered automated rule you run. A rule that scales budget on improving CPM will now scale on a placement mix change.

This week

• Re-baseline your weekly report. Any week-over-week CPM or impression comparison that straddles October 19 is comparing two different inventory sets.
• For accounts where Threads is taking spend with no conversions, apply the placement value rule with a bid decrease. Expect reduction, not removal.
• Check creative fit before you cut. Threads is a text-forward feed, and a direct-response static built for Instagram is not the same asset there. Weak Threads performance can be a creative problem rather than a placement problem.

Monitor

• Watch Threads CPA separately for four weeks. A cheap placement with poor intent in October can convert differently in BFCM traffic.
• Watch for a Threads-specific reporting improvement from Meta. Right now the depth is thinner than Facebook or Instagram placements.
• Re-run the breakdown weekly through BFCM. The mix will keep moving while the rollout settles.

Common mistakes

Treating a falling blended CPM as an efficiency gain. Right now it is more likely a composition change. Check the mix before you take the credit.

Assuming the 90% bid cut is an off switch. It is a 90% bid cut. Budget still flows. Teams that set it and move on will find Threads spend in next month's breakdown and assume the rule failed.

Cutting Threads before measuring it. The CPM discount is real. Some accounts will find their cheapest converting placement here. Reflexively suppressing it costs money in exactly the accounts where it works.

Comparing this week to last week without noting the date. Every WoW delta that spans October 19 is contaminated. Annotate it in your client reporting before a client asks why CPM dropped and revenue didn't.

Reading your September notes as current. Threads ads reached general availability back in January and we called it a mature placement in the September Meta ads update. That was accurate then and it is the wrong conclusion now. Availability is not the same thing as a default.

FAQ

Can I turn off Threads ads completely? No. Full placement exclusions were removed for many advertisers in August 2026, and the rollout was account-by-account with no official announcement. The strongest available lever is a placement value rule that cuts Threads bids by up to 90%, which suppresses delivery without ending it.

Where do I see Threads performance in Ads Manager? Breakdown → By Delivery → Placement. Threads appears as its own row next to Facebook feed, Instagram feed, Reels and Stories. Meta treats placement values as estimated, so read them as directional. You also have to pull this manually every time — it is not in the default column set.

Why did my CPM drop this week? Most likely because Threads entered your placement mix at a CPM 20–40% below Instagram feed. Cheap impressions pull the blended average down without any improvement in how your ads perform. Pull the placement breakdown and compare against the week before October 19.

Does this affect campaign objectives differently? The reported removal of exclusions centred on objectives including sales, leads and engagement. Because the rollout was uneven, verify per account and per objective rather than relying on a general rule.

Is this in the October changelog? No. Our October 2026 Meta ads update covers the agentic assistant and Customer Lifecycle Strategy, both of which landed earlier in the month. The Threads default arrived on October 19, after that post shipped, and is a separate story with a separate action list.

What to do with this

The work here is small and specific: one breakdown pull, one number written down, one decision about a bid rule. The hard part is remembering to do it, on every account, in a week when a silent default change produced metrics that look better than the business is performing.

That is the job a weekly read should already be doing for you. GoodMorning is built so that the placement mix shift shows up as an action item rather than something you have to go looking for — pre-diagnosed, sorted into Act today, This week and Monitor, with zero analysis required on your end. Our Meta Ads audit tool runs the placement check as part of a read-only account pass, and Meta Ads reporting software is the broader weekly version. Agencies running this across a client roster will want the multi-account setup, since the breakdown pull multiplies by every account you manage.

And if the Threads row turns out to be eating your best-performing creative's budget, that is a different diagnosis — see our creative fatigue tool for the rotation side of it.