Testing vs Scaling Budget Split: The 70/20/10 That Isn't Dogma
70/20/10 gets repeated as gospel, but the right testing vs scaling split depends on your winner inventory and fatigue rate, not a fixed percentage. Here's the framework instead.

A common starting split for testing vs scaling budget is roughly 70% to proven winners, 20% to close variants of things that are already working, and 10% to genuinely new creative or offer tests, but treat that 70/20/10 as a starting point to adjust, not a rule to follow blindly. The right split depends on how many winners you currently have, how fast your best creative is fatiguing, and how much runway you have to survive a bad testing week.
Why the ratio isn't the point#
The 70/20/10 (or 80/15/5, or 60/30/10, depending on who you ask) framework gets repeated because it's a reasonable default for someone with no other information. But it answers the wrong question. The actual decision buyers need to make isn't "what percentage should I test with," it's "how much can I afford to lose this week without threatening the campaign, and how many creative concepts do I need running concurrently to keep a pipeline of winners coming."
Those two questions produce very different splits depending on account size. A buyer spending $500 a day testing at 10% has $50 a day to find a new winner, which at typical native testing costs is barely enough to get a directional read on one new angle. A buyer at $10,000 a day has $1,000 a day for testing, which supports running four or five real tests in parallel. The percentage is identical; the practical testing capacity is not.
The real inputs to your split#
Winner inventory. If you currently have one working ad and it's showing early fatigue signs, you need to be testing more aggressively than 10%, because you're one bad week from having zero winners. If you have five stable winners across different angles, you can afford to lean harder into scaling and test more conservatively.
Fatigue rate. Native creative fatigue timelines vary by vertical and network, but the pattern is consistent: performance degrades as frequency builds and the same audience segment sees the ad repeatedly. Track how many days your typical winner holds before decay starts, and size your testing budget to have a replacement ready before that point, not after. See creative fatigue for the underlying mechanic.
Account runway. How many bad weeks can the business absorb before spend has to shrink? Thinner runway argues for a smaller, more conservative testing allocation even if it slows how fast you find new winners; the tradeoff is real and there's no formula that removes it.
Testing cost per learning. A cheap Revcontent or MGID test in a lower-tier geo can get you a directional read for a few hundred dollars. A Taboola test in a competitive Tier-1 vertical like finance or insurance needs meaningfully more spend before the data is trustworthy. Budget your test allocation to the cost of a real answer, not an arbitrary dollar figure.
A practical framework instead of a fixed ratio#
- Set a testing floor, not a percentage. Decide the minimum weekly dollar amount needed to run at least two real creative or angle tests to a statistically useful sample. That's your floor regardless of total spend.
- Scale the winner allocation to fill the rest, but cap how much goes into any single creative or publisher, since publisher-level performance data will often show that even a "winning" campaign has weak pockets worth trimming rather than blindly scaling everything proportionally.
- Reserve a middle tier for iteration, not brand-new concepts: variations on a winning hook, a new image on a proven headline, a different CTA. This is cheaper to test than fully new concepts and has a higher hit rate, which is most of what the "20%" in 70/20/10 is actually doing.
- Revisit weekly, not monthly. The right split shifts as winners fatigue and new tests either succeed or fail; a fixed monthly allocation gets stale fast in a channel where creative decay is measured in days or weeks, not quarters.
Where testing budget should actually go#
Not every network or geo deserves equal testing spend. Cheaper geos and networks let you get a read faster and cheaper: testing a new angle in a Tier-2 geo on MGID or Revcontent before committing it to a Tier-1 Taboola campaign is a common pattern precisely because the cost of a wrong answer is lower. If the angle works cheap, it's a much safer bet to scale into premium inventory. This is also where checking whether a similar angle is already proven elsewhere pays off. Before spending test budget on a concept from scratch, analyzing winning native ad creatives already live in your vertical tells you whether the angle has legs before you pay to find out yourself.
A worked example across account sizes#
Consider two accounts both nominally running a 70/20/10 split. Account A spends $400/day; its 10% testing allocation is $40/day, which on most native networks isn't enough to reach a single conversion in a Tier-1 vertical within a week, let alone compare two concepts against each other. Account B spends $8,000/day; its 10% is $800/day, enough to run three or four real tests concurrently and get a trustworthy read within days.
The fix for Account A usually isn't "test less," it's restructuring the ratio so the testing floor is a fixed dollar amount rather than a percentage: maybe $150/day regardless of what that represents as a share of total spend, funded by trimming the scaling allocation slightly rather than shrinking test quality below the point where it produces usable data. A test that can't reach a real sample isn't cheaper, it's just a way of spending money without learning anything, which is worse than not testing at all.
Signals that your split needs to change#
A few concrete triggers worth watching for, rather than waiting for a scheduled review:
- Your best creative's performance has dropped two weeks running. That's an early fatigue signal, and it means your testing pipeline needs to already have a candidate ready, not start from zero once the winner fully decays.
- Your test hit rate has been unusually high recently. If three of your last five tests turned into viable winners, that's a sign the vertical or angle pool you're pulling from is unusually fertile right now, and leaning into more testing temporarily can compound faster than sticking to a fixed ratio.
- You've had zero new winners in a month despite consistent test spend. This is a signal to look at where your test concepts are coming from, not necessarily to change the ratio; more testing dollars against weak concepts just burns budget faster.
Common mistakes with the split#
- Treating the ratio as fixed regardless of results. If testing is producing winners at a high hit rate, that's a signal to lean in further, not to mechanically cap it at 10%.
- Testing too many variables at once. A test that changes headline, image and landing page simultaneously doesn't tell you which change mattered. Isolate variables where budget allows.
- Killing tests too early. Underfunded tests that get judged on day one or two of spend are usually judged on noise, not signal. Size the test budget to the sample you actually need before deciding.
- Never revisiting "scaling" spend. Money allocated to winners isn't set-and-forget; it still needs ongoing publisher-level and device/geo bid discipline to keep a winner winning.
How to know if your split is working#
Track a simple ratio over a rolling four-week window: dollars spent testing versus new winners produced. If that ratio is getting worse (more testing dollars per winner found), the problem usually isn't the split percentage, it's the quality of the concepts going into testing. Better inputs, informed by what's actually working across the vertical right now, fix that faster than reshuffling the budget ratio.
The 70/20/10 is a fine place to start on day one of a new account. By week four, your own fatigue rate, winner count and test hit rate should be driving the number, not a rule you read in a blog post.







