How to read creative test results after 7 days on Meta, and the three things you can not conclude yet

The read is a fixed procedure: filter to the batch, read delivery share, results and cost per result in that order, then let CTR and hook rates explain rather than decide. And know which three conclusions are not available on day seven.

Adlio team4 min read

Why seven days

Two reasons, one of them Meta's. Meta defines the learning phase over a week: an ad set exits it "after about 50 results in the week after the ad set's last significant edit" (help page on the learning phase, fetched 4 September 2026; detail in adding ads to an existing ad set). Reading before that week is reading the delivery system's exploration, not its verdict. The second reason is ordinary: a week contains every weekday and the weekend once, so a read on day three compares a Tuesday launch to a Thursday one.

Seven days is the earliest read, not the only one. A batch that has not reached its results floor on day seven gets a second read on day fourteen; the kill rules say what happens to individual ads in between.

Set up the view once

  • Filter to the batch by name. If the batch was structured as described in how to structure a creative test batch, "ad name contains SPRING_hook" isolates it. If not, this is the moment you learn why naming matters.
  • Date range: the seven days since activation, not since creation. Paused days before activation are noise.
  • Columns, in this order: amount spent, impressions, results, cost per result, then CTR (link), and for video the 3-second plays and ThruPlays. Save it as a custom column set so every read looks the same.
  • Attribution setting fixed. Whatever your account uses, keep it identical across reads and batches; changing it mid-test changes the results column without changing the ads.
  • No breakdowns on the first pass. Placement and age breakdowns come after the batch-level read, if at all.

Read in this order

1. Delivery share

Sort by amount spent. Meta favours "the ad that's most likely to achieve the lowest cost per optimisation event for the given person", so the spend column tells you which ads the system chose to show and which it barely tried. An ad with a few percent of the batch's spend has not been tested yet, whatever its other columns say.

2. Results count

For each ad, how many results? Below the floor you set before launch (we use Meta's own "about 50 in a week" as the ad-set floor and a smaller per-ad floor you choose in advance; see how many ads to test per week), the cost figure next to it is not stable. Mark those rows as unread rather than as anything else.

3. Cost per result, against the target

Now the deciding column, for the ads that cleared the floor: cost per result against the target you wrote down before launch. This is where winners and losers are named. Not CTR, not CPM, not thumb-stop rate. Those are next, and they explain; they do not decide.

4. Secondary metrics, to explain

CTR, hook rate (3-second plays over impressions), hold rate (ThruPlays over 3-second plays), landing page views over link clicks. Use them to say why a winner won: strong hook and weak hold points to the middle of the video; strong CTR and weak cost per result points to the landing page or the promise. That is the input for the next batch (from a winning ad to the next batch), not a verdict on this one.

The delivery skew trap

The most common misreading at day seven is calling an under-delivered ad a loser. Meta's documentation is explicit that "each of your ads won't necessarily be delivered the same number of times". An ad with 40 impressions and no result did not fail; it was not chosen. The honest labels for a batch are therefore three: winner, loser, unread. Unread ads either get more time in the same ad set, or go back to the queue for a batch where they are not competing with a stronger sibling.

Three conclusions you can not draw on day seven

  1. A winner from under the results floor. Five results at a great cost is an anecdote. Wait for the second read.
  2. A loser from no delivery. See above. Not chosen is not tested.
  3. Anything from CTR alone. Enhancements, a bright thumbnail, a curiosity hook: all raise CTR without moving the result you pay for. If enhancements were on for this batch, the reported figures are "including all variations" and you can not separate your file from Meta's edits of it; turn them off for the next batch.

What you can conclude

  • Which ads cleared the floor and beat the target: winners, to be scaled without editing (next batch).
  • Which ads cleared the floor and missed the target by your kill margin: losers, to be paused per ad, never the ad set (kill rules).
  • Which ads are unread, and whether the batch needs a second week.
  • Whether the variable you tested moved anything at all: if the spread in cost per result across the batch is small, the variable does not matter much on this account, and that is a useful result.

Record it

Fill the result row of the batch sheet: per ad, label (winner, loser, unread), spend, results, cost per result, and the one-line "why" from the secondary metrics. The sheet is what makes the loop cumulative; without it every batch is the first batch.

Where this sits

Step three of the creative testing framework for Meta ads at volume. Adlio's part ended at step two: the batch was launched paused, named by pattern, UTM-tagged and with enhancements off, so that this read is a filter and a sort rather than a reconstruction. First 15 ads free; see how bulk upload works and pricing.

Frequently asked questions

Why not read after 3 days?+

Because Meta defines the learning phase over the week after the ad set's last significant edit, so a day-three read is a read of the delivery system's exploration, not its verdict. And because a three-day window compares a Tuesday launch to a Thursday one; a week contains every weekday and the weekend once.

Which metric decides a creative test?+

Cost per result against the target you wrote down before launch, for the ads that cleared the results floor. CTR, hook rate and hold rate explain why an ad won or lost; they do not decide, because all of them can rise without moving the result you pay for.

What if none of the ads reached the results floor?+

Then the batch is unread, not failed. Give it a second week if the ad set is spending as planned, or, if the budget was too small for the floor, treat that as the finding: the batch was underfunded, and the next one is sized from the budget guide.

Should I look at placement breakdowns?+

After the batch-level read, and only if you will act on them: an ad that wins in Reels and loses in Feed is a candidate for a placement-specific iteration. On the first pass, no breakdowns; they multiply the rows and divide the sample.

Sources

Adlio team

Built by media buyers who launch Meta ads in volume. Questions or corrections: support@adlio.ai.

Topic cluster

Creative testing at volume

How to structure, ship and read creative tests when you launch dozens of ads a week.

Start here

Creative testing framework for Meta ads at volume

Related guides