How do I know which Facebook ads to turn off?

Updated November 12, 2026

The three kill signals at a glance

A Facebook ad should be turned off for exactly three reasons: it spent past your CPA with nothing to show, its audience is worn out, or Meta itself has stopped delivering it. Each signal has a number attached, so the decision can be made from data instead of mood.

The table below is the whole decision. The rest of this page explains why each threshold sits where it does, and how to run the check by hand in about twenty minutes a week.

Note what is missing from the table: one bad day, a CPA slightly over target, a gut feeling that the creative looks stale. None of those are kill signals. Many accounts lose more money to panic pausing than to slow pausing, because every pause throws away auction history the ad already paid for.

Wait for the learning phase before judging anything

The learning phase ends after roughly 50 conversion events in an ad set within a seven-day window, and before that point performance data is mostly noise. Meta is still exploring who should see the ad: it tests placements, audiences and times of day, and costs swing widely while it does. An ad that looks terrible on day two is often the winner by day six.

Two practical consequences follow. First, never judge an ad against your CPA target while its ad set shows Learning in Ads Manager, unless spend has already passed the kill line below. Second, every significant edit - a large budget jump, a targeting change, new creative added to the same ad set - resets learning and restarts the noisy period. Accounts that get edited daily live in permanent learning and never produce readable data.

Ad sets stuck in Learning Limited are a different problem: they cannot reach 50 weekly conversion events at the current budget and audience size. Waiting does not fix that. The fix is consolidation - fewer ad sets, broader audiences, or optimizing toward an event that fires more often - so that the events concentrate instead of spreading thin.

Signal 1: spend past CPA with zero conversions

Pause an ad once it has spent more than one full target CPA after the learning phase with zero conversions. Here is the logic as a worked example: say your target CPA is $40. An ad that has spent $45 since learning ended and produced nothing has had a full purchase worth of budget to prove itself, and the honest reading is that the market declined.

Why one CPA and never less: below that line you are reading luck. With a $40 target, an ad that spent $25 with no sale simply has not had enough traffic for a conversion to be statistically likely, even at a healthy conversion rate. Pausing it tells you nothing and may cost you a winner.

Why one CPA and rarely much more: conversions arrive in streaks, so a rare ad redeems itself at 1.5x spend. But the expected value of the second CPA of spend on a silent ad is poor, and that budget almost always earns more on a sibling that is already converting. If you want a safety margin, use 1.5x on new ad sets with little history and 1x on proven ones, and write the rule down so it gets applied the same way every week.

Signal 2: frequency rising while CTR falls

Creative fatigue shows up as frequency climbing while CTR falls over five or more days, and it predicts a CPA rise before the CPA actually rises. Frequency is average impressions per person. When it creeps up, Meta is re-showing the ad to people who already declined to click, and click-through rate decays as the novelty wears off.

The mechanism that turns fatigue into cost is the auction. Meta estimates how likely each user is to engage with your ad, and that estimate is part of your bid's effective strength. As engagement drops, the estimate drops, and Meta charges you more to win the same impression. CTR decay therefore converts into CPM and CPA increases on a delay of a few days. Catching the CTR slide early is how you rotate creative before paying for that lag.

The five-day rule exists to filter noise. CTR wobbles daily with placement mix and audience churn, so a single red day means nothing; five descending days with frequency above its own prior level is a trend. On small audiences such as retargeting, fatigue arrives faster and frequency runs structurally higher, so judge the trend against the ad's own history rather than against any absolute number.

Signal 3: Meta has already starved the ad

When an ad receives under 10% of its ad set's delivery for a full week, Meta has effectively paused it for you, and keeping it live only muddies your data. Within an ad set, Meta runs a continuous internal contest between sibling ads and routes impressions to whichever it predicts will perform best. A consistently starved ad lost that contest.

The argument for making the pause official is cleanliness. A starved ad still takes occasional impressions, pollutes the ad set's averages, and sits in every report as a distraction. Pausing it formalizes a decision Meta already made and leaves a cleaner test among the survivors.

One exception is worth knowing. A new ad added to an ad set with an entrenched winner sometimes starves on arrival, because the winner's accumulated auction history dominates the contest before the new ad gets a fair sample. If you want the new ad genuinely tested, give it its own ad set or a structured test instead of reading its starvation as failure.

Pause the ad, the ad set, or the campaign?

Pause the ad when its siblings perform; pause the ad set when all of its ads fail together; rethink the campaign when several ad sets fail against an offer that works elsewhere. Failure at a level above the ad points at a shared cause: the audience, the offer, the landing page, or the event being optimized.

• One ad failing while siblings convert: a creative problem. Pause the ad and keep the structure.
• Every ad in the ad set failing: an audience or offer problem. Pausing ads one by one just reorders the same loss.
• An ad set failing right after a budget raise: a learning reset or audience saturation. Give it a few days before judging.
• Under CBO (campaign budget optimization), the campaign budget flows to the surviving ad sets automatically when you pause one. Check the survivors can absorb the extra spend without tipping into fatigue.
• A whole campaign failing while another campaign converts: wrong objective, wrong conversion event, or wrong funnel stage. That is a structure decision, and no amount of ad-level pausing fixes it.

The 20-minute weekly pause review

A weekly manual pause review needs one saved report and six repeatable steps.

1. Build a saved view in Ads Manager with these columns: spend, conversions, cost per conversion, frequency, CTR and delivery status, over the last 7 days, with a lifetime toggle for context.
2. Filter out everything still in learning. Those ads are exempt from judgment this week, unless spend has already passed 1x target CPA.
3. Sort by spend and check every ad with more than one target CPA of post-learning spend and zero conversions. Those are pauses.
4. Scan frequency and CTR trends: compare this week's CTR to the ad's own prior two weeks, flag ads where CTR falls while frequency rises, and brief replacement creative for them now, before they fail.
5. Open each ad set's per-ad delivery split and note ads under 10% of delivery for the full week. Pause them.
6. Write one line per pause in a log: date, ad name, which signal fired, and the numbers. The log is what stops the same loser being relaunched in a month.

The log matters more than it looks. Accounts cycle through operators - a founder, then a freelancer, then a tool - and without written reasons, every new operator re-tests the same dead creative. The habit also forces honesty: if you cannot name the signal, you are pausing on mood.

Mistakes that kill healthy ads

Most pausing mistakes come from reacting to noise or to the wrong metric. These are the common ones:

• Pausing on one bad day. Daily CPA on a small budget swings hard because conversions are whole numbers: a zero-conversion day and a great day can be the same ad having a normal week.
• Judging ads mid-learning. The data is unstable by design, and the pause wastes the spend that bought the learning progress.
• Pausing on CTR alone. CTR is an early-warning signal, never a verdict: plenty of low-CTR ads convert cheaply because the clicks that do come are qualified.
• Editing or duplicating an ad to 'refresh' it. The copy starts with zero auction history and re-enters learning; the original's history is the asset.
• Relaunching paused losers unchanged, hoping for a different answer. Same creative, same audience, same result.
• Pausing everything at once during a bad week. If the whole account dropped, the cause is shared - tracking, auction or landing page - and mass pausing destroys the data you need to diagnose it. Run the ten-minute drop diagnosis first.

Where AdsGuru automates this exact job

AdsGuru runs these three checks on every ad in the connected account daily and turns each firing signal into a proposed pause with the reason written in plain language. A proposal reads like a colleague's note: which ad, which signal, the numbers behind it, and what happens to the budget if you approve. Nothing is applied until you approve it - approval mode is the default - and every applied change lands in a log you can audit later.

Two honest limits. AdsGuru needs 7-14 days of account data before its proposals carry real weight, because trend signals need a baseline; in week one expect flags rather than confident calls. And it cannot save creative that was never going to work - it manages the pausing and rotation of ads you supply, which is why the creative testing loop matters as much as the pause logic. The full feature list is on the AI Meta ads tool page; the thresholds above ship as editable defaults. Pro is $89/month flat with a 7-day free trial - see pricing.

Common questions

Related