Deciding when to kill an underperforming ad is one of those calls that feels obvious in hindsight and agonizing in the moment. You watch the spend tick up, the conversions stay flat, and you ask yourself whether one more day will turn it around. This guide gives you a repeatable way to decide when to kill an underperforming ad — with specific thresholds you can set before launch, the signals that justify waiting, and what to do the moment you pull the plug.
Why this decision is harder than it looks
Killing an ad too early wastes the learning period and the money you already spent getting the algorithm to understand who to show it to. Killing an ad too late burns budget on something that was never going to convert. Both mistakes come from the same root cause: judging performance on vibes instead of a rule you decided on in advance.
The fix is to treat every new ad like a small experiment with a pre-registered stopping point. You write down what success and failure look like before you see any data. That single habit removes most of the emotional back-and-forth, because by the time the numbers come in, the decision has already been made.
How to decide when to kill an underperforming ad: the core framework
At the simplest level, you need three numbers before you launch anything: your target cost per result (purchase, lead, install — whatever you're optimizing for), the minimum spend you'll allow before judging the ad, and the minimum number of days you'll let it run regardless of early signals. Everything else is a refinement of these three.
- Set a spend ceiling relative to your target cost per result. A common starting point to test is roughly 2–3x your target cost per result with zero or near-zero conversions — if an ad has spent that much without producing a result, it has had a fair shot.
- Set a minimum runtime, usually 24–72 hours, so the algorithm has time to find an audience before you judge the creative.
- Check secondary signals (click-through rate, thumb-stop or hook rate, cost per add-to-cart) to diagnose why it's underperforming, not just that it is.
- Compare it against your current best-performing ad, not against an abstract ideal. If it's clearly behind your control ad on the metric you care about after the spend ceiling is hit, kill it.
- Decide on the spot what replaces it, so the kill doesn't leave a gap in your testing calendar.
Set kill criteria before you launch, not after
Write your thresholds down somewhere you'll actually look at them — a shared doc, a spreadsheet column, a note in your ad platform. For each new ad, fill in four fields before it goes live: target cost per result, spend ceiling, minimum runtime, and the ad it's being compared against. This takes two minutes and removes almost all of the guesswork later.
If you're testing several creative concepts at once, apply the same ceiling to all of them so the comparison is fair. An ad that's allowed to spend three times as much as its competitor before judgment will look artificially better just because it had more chances.
Adjust the ceiling for your price point and sales cycle
A low-price impulse product (a phone stand, a snack subscription) should show signal fast — if nobody is adding to cart within your spend ceiling, the creative or the offer isn't working. A higher-price or considered purchase (a mattress, a course) needs a longer runway, because people click, think, and come back days later. Widen your spend ceiling and runtime for these, but track cost per add-to-cart or cost per lead as an earlier proxy so you're not flying blind for a week.
Signals that say kill it vs signals that say wait
Not every weak number means the ad is dead. Some signals point to a genuine creative failure; others point to something you can fix without touching the video at all, or to normal variance that will settle once spend is higher.
- Kill it: cost per result stays well above your target after the spend ceiling, and click-through rate is also below your account average — the hook and the offer aren't landing together.
- Kill it: thumb-stop or hook rate (how many people watch past the first few seconds) is low relative to your other ads. This usually means the opening seconds aren't earning attention, and no amount of extra spend fixes that.
- Wait: spend hasn't hit your ceiling yet, even if the first day looked rough. Early data is noisy, especially in the first 24 hours.
- Wait: click-through rate is healthy but cost per result is high — this often points to a landing page, pricing, or checkout friction problem, not the ad itself.
- Refresh instead of kill: a previously strong ad is showing a slow decline in click-through rate alongside rising frequency. That's a sign of fatigue, not a fundamentally bad ad — see our guide on how to spot ad fatigue before it hurts performance for how to tell the two apart.
A quick decision table
Use this as a fast reference when you're reviewing ad performance and need to decide in the moment.
| Metric | Healthy sign | Kill signal |
|---|---|---|
| Spend vs. target cost per result | Under your spend ceiling, or converting near target | At or above spend ceiling with no conversions |
| Click-through rate | At or above your account average | Well below account average, especially combined with high cost per result |
| Hook / thumb-stop rate | Most viewers watch past the first few seconds | Sharp drop-off in the opening seconds across multiple days |
| Frequency (on an older ad) | Stable, steady results | Rising fast alongside a falling click-through rate |
| Add-to-cart or lead rate | In line with your other active ads | Consistently lower despite similar or higher spend |
Common mistakes that keep dead ads alive
- Judging on day one. A single bad morning is not a trend; wait for your pre-set minimum runtime before reacting.
- Comparing against an average instead of your best ad. If your bar is "better than nothing," you'll keep mediocre ads running far longer than you should.
- Blaming the audience when it's the hook. If an ad has low thumb-stop rate everywhere you've shown it, broadening the audience won't fix a weak opening three seconds.
- Blaming the creative when it's the offer or landing page. Strong click-through rate with poor conversion is usually a post-click problem, not a video problem.
- Keeping an ad alive out of sunk-cost thinking because it "might turn around." Your spend ceiling exists precisely so you don't have to make that call emotionally.
What to do the moment you kill an ad
Killing an ad without a replacement ready just shrinks your testing pipeline and your account's overall reach. Before you pause anything, have at least one new variant queued — ideally one that changes a single variable (the hook, the offer framing, or the opening visual) so you learn something from the next round instead of starting from zero again.
If the diagnosis was a weak hook, don't rebuild the whole ad — swap the first few seconds and keep the rest. Our guide on how to write multiple hooks for one ad script walks through generating several hook options from a single script so you always have a next attempt ready. If the diagnosis was a stale angle on an otherwise solid product, it may be time to go back to basics and build a fresh ad around the product's core benefit — see how to turn a bestseller product into a video ad for that process.
It also helps to plan your testing cadence ahead of time rather than reacting ad by ad. A simple content calendar — a set number of new concepts per week, each with its own kill criteria already assigned — keeps you from scrambling every time an ad underperforms. Our piece on how to plan a video ad content calendar covers how to structure that cadence.
Where FrameNotion fits into this process
The slowest part of killing and replacing ads is usually producing the next creative, not making the decision. FrameNotion is built for that gap: paste a product link and FrameNotion AI writes and renders a custom 30-second vertical ad — hook, problem, benefit, proof, offer, and call to action — in about 10 to 20 minutes, with no templates involved. Because every ad also comes out in 4:5, 1:1 and 16:9, you can drop the same creative into whichever placement your killed ad was running in without starting over.
If your diagnosis was specifically a weak hook, Pro and Agency plans let FrameNotion generate A/B hook variants of the same ad, so you can test a new opening without rebuilding the whole script. And once an ad is live, you can request text and color changes directly rather than producing a new one from scratch. FrameNotion doesn't publish ads to ad platforms or report back on performance — you'll still make the kill decision inside your ads manager using the framework above — but it removes the production bottleneck that usually causes teams to let a dead ad run a few extra days just because nothing new is ready. You can see the output style on the examples page, or compare your product's fit for different ad structures first in our guide on how to choose the right video ad format for your product.
For a deeper look at the underlying logic behind these thresholds, our companion piece When Should You Kill an Underperforming Ad? A Clear Framework breaks down the reasoning metric by metric.
Frequently asked questions
How long should I let a brand-new ad run before judging it?+
Give it a minimum runtime, typically 24 to 72 hours, regardless of early numbers. Early performance is noisy, and the first day in particular can look worse or better than reality once the algorithm settles on an audience.
Should I kill an ad that has a good click-through rate but no sales?+
Not immediately. A good click-through rate with no conversions usually points to the landing page, price, or checkout experience rather than the ad itself. Check your post-click funnel before you blame the creative.
Is it better to pause an ad or kill it outright?+
Pausing makes sense when you want to keep the ad's existing data and revisit it later, for example if a seasonal angle might work better in a few months. Kill (fully end) an ad when the underlying idea has been tested and clearly failed, so you free up budget for a genuinely new concept.
How many ads should I be testing at once before I start killing any?+
There's no fixed number, but running only one or two ads at a time makes any single kill decision feel high-stakes. A steadier approach is to always have a small rotation of active concepts, so pausing one underperformer barely dents your overall testing pipeline.
Does a falling click-through rate always mean the ad is dead?+
Not on its own. A falling click-through rate on a previously strong ad, especially alongside rising frequency, usually points to fatigue rather than a broken concept. That calls for a creative refresh or a new hook, not necessarily a full kill.