Write Your Kill Criteria Before You Launch, Not After

Why do buyers who know the kill rules still fail to kill?

Buyers who can recite their own kill rule from memory still blow through it, because sunk-cost psychology recalculates the decision in real time. Every dollar already spent gets treated as evidence the campaign is 'due,' not as a bill already paid. The brain doesn't ask what a fresh $500 would buy today — it asks how to justify the $500 already gone, and campaigns don't get killed on justification.

Attribution lag makes the trap worse. A campaign's CPA often looks its worst on day 3 or 4, before delayed conversions post, so a buyer who checks the dashboard mid-lag sees a number that's temporarily inflated and reads it as proof the rule was too strict. That reading is sometimes correct. More often it's the same story the buyer tells every time spend crosses the line, and the story is what makes a written rule necessary in the first place.

A kill rule set after the campaign is already underperforming isn't a rule — it's a rationalization with a deadline attached. The only version that survives contact with a bad day is one written and signed before the first dollar spends, with no clause letting the buyer who's emotionally invested in the outcome be the one who waives it.

What belongs in a written kill plan before any launch?

A written kill plan needs four fixed numbers and one named approver, set before the first impression serves: a maximum spend, a CPA multiple against the offer's payout, a time-in-market ceiling, and a person other than the buyer running the campaign who can authorize an exception. Nothing on that list should get filled in after launch day, and none of it should live only in the buyer's head — a rule nobody else can see is a rule nobody can enforce.

The specific numbers matter less than the fact that they're written down and checked against, which is the whole argument behind the exact kill criteria most Facebook buyers actually use — a fixed checklist beats a gut check every time performance gets uncomfortable.

• Spend ceiling in dollars and as a multiple of payout, checked at a fixed interval, not whenever the buyer happens to look.
• CPA multiple threshold, set relative to the offer's actual payout, not a round number pulled from habit.
• Time-in-market ceiling, independent of spend, for campaigns that limp along under the spend cap without ever converting.
• A compliance trigger independent of performance — a policy rejection, an account restriction, or for regulated categories such as weight-loss and peptide offers, a landing-page claim that starts to read like a drug claim under FDA's disease-claim framework.
• A named approver who did not build the campaign and has no stake in defending it.

How do you set a spend stop-loss from the offer's payout?

Set the spend stop-loss as a multiple of the offer's payout, not as a flat dollar figure, because a $40 payout and a $400 payout can't share a $200 ceiling. The multiple should buy enough spend to see one full conversion cycle complete, including any delayed attribution window, without letting a single ad or audience burn through a test budget before the data means anything.

None of the multiples below are a platform rule or a regulated figure. They're trade convention, reported consistently by working buyers rather than published anywhere, and they should tighten or loosen against your own account's historic variance rather than get copied wholesale from someone else's vertical.

• Creative or audience test, cold traffic: roughly 1 to 1.5x payout per variant — enough for one clean read, not enough to bury the account testing losers.
• Confirmed structure, new audience: roughly 2 to 3x payout, the range cited most often as convention among performance buyers.
• Scaling checkpoint: reset the multiple at each scaling step rather than carrying the original test budget forward — a 5x budget increase earns its own ceiling.
• Warm or retargeting pools: allow a longer runway, often 3 to 4x, since volume is thinner and conversions lag further behind spend.

Which time-based rules prevent zombie campaigns from lingering?

A time-in-market ceiling kills campaigns that never breach the spend stop-loss but also never do anything, drifting at low volume for weeks under a cap sized for a real test. Fourteen days with no clear signal, win or lose, is a common outer bound among buyers who track this, mainly because creative fatigue and diminishing frequency start working against a stalled campaign well before spend does.

Ad review timing sets the floor under any time-based rule. Meta's review relies primarily on automated checks, usually finishes within 24 hours, and can re-review a live ad at any point after approval, per Meta's Advertising Standards on the ad review process. TikTok publishes a similar 24-hour target and re-triggers review automatically whenever you edit creative or the ad group's targeting location, per TikTok's Ads Manager Ad Review FAQ — a rule clock shouldn't start until review actually clears.

For the exact day-by-day thresholds, when a 3-day CPA spike means something and when it's noise, see how long you should run an ad before killing it, which breaks the window down by funnel stage rather than a single flat number.

When is breaking your own kill rule actually the right call?

Breaking a kill rule is legitimate only when the exception was written down before the rule was ever tested, never when it's negotiated in the moment the number crosses the line. A pre-registered exception might read: if the account is mid-review and delivery is paused, the clock stops, or if sample size is under 50 conversions, extend once, by a fixed and pre-agreed amount. Both are decisions made in advance, by a calm version of the buyer, not the version staring at a red number.

Here's the part most disciplined buyers get wrong: a stop-loss rule that never bends isn't discipline, it's a cruder tool pretending to be a refined one. Attribution lag is real — Meta itself notes ads can be reviewed again after they're live, meaning delivery and delayed conversions can keep shifting well after a rigid clock would have pulled the plug — and a buyer who treats every override as weakness ends up killing slow-starting winners at the same rate as genuine losers. The fix isn't fewer exceptions. It's exceptions written down in advance, with numbers attached, instead of invented on the spot.

Legitimate exceptions cluster around three cases: an active platform review holding delivery, a sample size too small for the CPA to mean anything yet, and a documented tracking or pixel failure that invalidates the numbers being used to judge the campaign. Anything outside those three, written down before launch, is the sunk-cost instinct wearing a rule's clothing.

How do teams enforce kill criteria across multiple buyers?

Teams enforce kill criteria by removing the in-flight decision from the buyer with a stake in the outcome — a second sign-off, a dashboard that flags the CPA multiple automatically instead of waiting for someone to check, and a compliance checkpoint that runs independent of performance. If the only enforcement mechanism is a buyer's own judgment under pressure, the rule will bend exactly when it matters most.

Compliance deserves its own kill trigger, separate from CPA, especially in weight-loss and health-adjacent verticals where claim drift is constant and often unintentional. Run new creative through a compliant claim rewrite before it launches rather than waiting for a rejection to force the issue.

Imagery needs the same pre-launch check. Meta permits transformation imagery for general cosmetic products when targeted at adults 18 and older, while TikTok bans before-and-after comparisons outright for supplements, OTC medicines and medical devices across a named set of MENA and African markets — confirm which platforms actually allow before-and-after photos before the shoot, not after the rejection.

What should the post-kill review capture for the next launch?

A post-kill review captures what killed the campaign, not just that it got killed: the CPA trend at the moment of the decision, whether the rule was honored or overridden and under which pre-registered exception, and whether the underlying problem sat in the campaign or in the offer itself. Skipping that distinction is how teams re-launch the same broken offer under a new campaign name and blame the buyer again.

Before writing up a generic 'creative fatigue' verdict, check whether the offer, not the campaign, was actually the constraint — a campaign that dies fast across every buyer and every angle is usually telling you something about payout, landing page, or product-market fit that no amount of new creative will fix.

• Final CPA and spend against the pre-set multiple, plus how many days elapsed versus the time-in-market ceiling.
• Whether the kill rule was followed, overridden, or extended, and which pre-registered exception, if any, justified the override.
• Any compliance flag triggered during the flight, including ad rejections, account restrictions, or claim rewrites forced mid-campaign.
• Whether the same offer failed under multiple buyers or angles, which points at the offer rather than the execution.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.

For deeper evaluation, continue through Daily Intel research methodology, Teste de Criativos no Meta Ads: Estrutura Completa, How to Know an Offer Is Saturated Before You Spend, Como Encontrar Campanhas Vencedoras Para Modelar Hoje, Facebook Ad Library Impressions: The New Spend Signal, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.