GoScript
Back to Blog
GoScript Journal

Sample Size for Title Tests: Know When Data Is Real

·6 min read·GoScript Team /Design

Title test sample size is the number of impressions or viewers a variant needs before its click-through rate means anything. Below that number you are comparing noise. Above it, the result starts to hold.

Most creators quit tests too early. I did for years, because a leader after ninety minutes feels like an answer. It usually is not.

Why small samples lie

Click-through rate is an average, and averages wobble when the sample is small. A title can post a nine percent CTR on forty impressions and a two percent CTR on four thousand. The first number is not a hidden insight. It is a tiny denominator.

The fix is uncomfortable: wait. A test that resolves in an hour is resolving because there is almost no data, not because the answer is obvious.

If your winner was decided by fewer impressions than a busy grocery store sees in a day, you did not measure anything. You noticed a fluctuation.

Rough thresholds I use

  • Under five hundred impressions per variant: treat the result as a hunch, not a finding.
  • One to three thousand impressions: enough to see a large gap, not enough to trust a small one.
  • Five thousand and up: a two percent CTR difference starts to be worth acting on.
  • Similar audience window: compare variants that ran over comparable days and hours, or the clock confounds the result.

Effect size beats sample size

A huge lift shows up fast even with modest data. A tiny lift needs a mountain of impressions to separate from random variation. So the question is not only how big the sample is, it is how big the effect you are hunting.

If two titles differ by half a percent, I rarely chase it. Half a percent might be real, but the cost of a clean test to prove it usually exceeds the value of winning it. I save my tests for questions where a win would change what I do.

When your channel is small

Small channels face a real constraint: not enough impressions to run clean tests on everything. The workaround is to pool. Run one title format across five videos and compare that format's average to your baseline, rather than comparing two titles on a single video.

You can also test with a panel before upload, then let the platform numbers confirm or deny it. The panel is cheap and fast. The platform data is real but slow. Using both covers the gap while the channel grows.

Build patience into the process

I schedule title decisions a week out now. The test runs, I do not touch it, and I read it on a fixed day. Removing the option to peek killed most of my early-call mistakes.

Sample size rules are boring, and boring is the point. They stop you from rewriting a winning title because it looked weak in its first two hours.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel