Projects · Meta Ad Center

FACEBOOK ADS.

what is live, what is in rotation, what is pending, and what is coming up.

NewWant the short version? See the Analytics Snapshot for this week and what to do next, or the Case Study for the wins.

Meta is the only paid channel, and the account is now down to one live ad set: the CMS 2027 Final Rule campaign buying completed webinar registrations inside Florida, at a $40 daily budget. The seven state CMS campaign and the Page Likes campaign were paused at ad set level on Sept 18 to conserve budget, and both Agency Ceiling campaigns closed on Sept 16 on 5 registrations across $255.15. Legacy stays paused. The thing to know about the last few days is spend, not creative: the one live campaign has closed over its $40 budget three days running, at 157, 170 and 130 percent, so the month no longer fits at the nominal rate and the open call is an account level spending limit. Two cautions carry into everything below. Every figure here is a ratio, and a ratio is silent about whether anything ran. And with only one campaign buying registrations there is no second arm to compare against, so day to day swings are noisy and are not read as verdicts on the creative. For the short version of all of this, see the Analytics Snapshot linked at the top.

By the numbers

THE ACCOUNT IS STILL OFF, AND IT STAYED STILL. Oct 11 closed at $0.00 on every campaign, ad set and ad, with no delivery, no impressions and no charge. The activity log carries no owner action after the 9:02pm Sept 22 pause, so there was no restart. Its only lines since Sept 30 are ten custom audiences Meta itself created at 10:55am Oct 8, which are neither an owner action nor delivery, and nothing has been added since. Meta restated nothing this check could see, so the winning ad still reads 85 registrations across $717.98 and the Florida campaign 89 at $8.53 across $759.38, both re-read on the Oct 12 pull. All three campaigns still read ACTIVE because the pauses are at ad set level. WHAT IS LEFT. About $311 of the roughly $500 went unspent in September, today is Oct 12, and nothing is spending it. A restart at the nominal $40 is $40, and at the rate the last seven delivering days ran it is about $45. The worst day on record ran 170 percent of budget, about $68, so even the worst case fits and the spending limit stays a backstop rather than a necessity. The winning ad's frequency read 3.39 for a twentieth morning, 0.11 short of its fatigue threshold with no second creative behind it, and the page no longer prints a crossing date because a paused ad has none. The CMS 2027 angle decayed on Oct 1 and nothing was bought on it. BILLING: the $4.40 Account billed event at 4:07am Sept 30 stays the only charge since $25.00 at 7:39pm on Sept 22, and no new charge or owner action appears since (the log's only lines since 6:16pm Sept 30 are the ten Meta generated custom audiences of 10:55am Oct 8). It is recorded and not explained. AD LIBRARY: 445 ads across all 21 pages, 426 yesterday. The diff printed no revival, and every new ad was checked against ad ids across the whole archive. No tier one page shows a new agent recruiting concept. The tier one advocacy page added two consumer event headlines (a town event and a painting workshop), both on a capped page. A tier three lead vendor swapped all eight of its ads for eight fresh ids with the same two headlines, created Oct 11, which is a refresh and not a disappearance. A tier three agency tooling page added a batch of five untitled ads created Oct 9 to Oct 11. Several complete pages returned ids the archive already held from earlier pulls but not from yesterday, which says the index varies day to day, not that the pages relaunched anything. Five pages returned zero and five hit the 50 cap. Batch size is a proxy for activity only and is not a claim about spend. Nothing was published, paused, edited or budgeted by this check.

Active and queryable. No delivery-blocking errors, no failed charge since Sept 13Ad account status
NOTHING. Every ad set is paused. The owner paused the last one, CMS 2027 | FL | Leads, at 9:02pm Sept 22What is live
All three campaigns and their ads still read ACTIVE. The pauses are at ad set level, so status is not deliveryReads live, is not
Oct 11: $0.00 and no delivery anywhere, the nineteenth full day with every ad set paused. No owner action, no restatementYesterday, closed
The last seven delivering days, Sept 16 to 22, spent $314.22 against $280, 112 percent of a weekly budget, after a twenty cent restatementThe week before the pause
About $311 of the roughly $500 unspent and nothing spending it. September is over; whether that money carries into October is the owner's callBudget left
A spending limit at about $310 caps the total whatever the daily rate does. A billing action, the owner's aloneIf it restarts
$0.00 and no delivery, because every ad set is still paused and the log shows no restartToday so far
105 across the registration campaigns. The owner verified 76 on Sept 16, so 29 added since, about 28 percent unverifiedRegistrations, lifetime
PAUSED at ad set level. 89 registrations at $8.53 lifetime across $759.38CMS 2027, Florida
PAUSED at ad set level. Closed on 11 registrations at $10.35 across $113.83CMS 2027, seven states
PAUSED at ad set level. Closed on 748 follows at $0.87 across $653.47Page Likes
Closed Sept 16. 5 registrations on $255.15, which is $51.03 eachAgency Ceiling, both campaigns
Still status ACTIVE, effective_status ADSET_PAUSED inside its paused set. Runs on restart with no actionService Fire, armed
3.39 on a reach of 3,470 at AD level, Maximum window, the same for a twentieth morning. Frozen while its ad set is pausedWinner's frequency
Not datable while paused. 0.11 below the 3.5 threshold, so a restart crosses it inside a day or twoFrequency runway
The ad set still holds one creative. A restart brings the missing second creative back as a live questionNo rotation behind the winner
Decayed on Oct 1. Days not bought before that date cannot be bought on this angle at allCMS 2027 angle decays
445 ads across all 21 watchlist pages on Oct 12. No revival and no new agent recruiting concept; a tier three lead vendor refreshed all eight ads under the same headlines. Ten pages hit the 50 cap or returned zero, so they carry no disappearance claimsAd Library archive

Internal ad-account metrics, Mon Oct 12 morning pull. Every ad set is still paused by the owner and Oct 11 closed at $0.00 with no delivery anywhere and no restatement. Today is a partial day read at about 8:30am, so its prices are early and flattered by conversions arriving ahead of the impressions that earned them; the closed-day numbers are directly below, and the charts under them run on complete days except where a bar is marked as still open. Every price and ratio on this page is a measure of how the money performed, so none of them can report that the money stopped. Read the spend figures first.

Yesterday, complete

A NINETEENTH DAY OF NOTHING, AND AGAIN NO RESTATEMENT. Oct 11 closed at $0.00 on every campaign, ad set and ad, with no impressions and no charge. Every ad set has read PAUSED since the owner stopped the last one at 9:02pm on Sept 22, and the activity log carries no owner action since (its only lines are ten custom audiences Meta itself created at 10:55am Oct 8, and nothing after them), so status and delivery agree. The three campaigns and the ad still read ACTIVE, which is the ad set level trap this page has named before. Meta moved no earlier day that this check could see: the winning ad's lifetime still reads 85 registrations across $717.98, and all three campaign lifetimes were re-read unchanged on the Oct 12 pull. WHAT IS LEFT. About $311 of the roughly $500, nothing spending it, and the month it was meant for has ended. The CMS 2027 angle decayed on Oct 1, and nothing was bought on it.

SUNOct 11complete day, midnight to midnight, and the nineteenth full day with every ad set on the account paused$0.00 spent of $40.00 committed
Off

CMS 2027 Final Rule, Florida

No registration
Campaign off, nothing spent
Impressions
0
Reach
0
Frequency
0
CPM
CTR, all
Off

CMS 2027 Final Rule, seven states

No registration
Campaign off, nothing spent
Impressions
0
Reach
0
Frequency
0
CPM
CTR, all
Off

Page Likes

No follow
Campaign off, nothing spent
Impressions
0
Reach
0
Frequency
0
CPM
CTR, all

Every ad that spent, Oct 11

AdResultCostSpendReachFreq
CMS Social A · The ClockPaused with its ad set, so it served nothing. Its lifetime frequency read 3.39 on a reach of 3,470 for a twentieth morning, which is what a paused ad should do. Lifetime at ad level is 85 registrations at $8.45 across $717.98, unchangedNo registrationn/a$0.0000
Same Day B · Ready ClientZero because its ad set is paused, not because Meta withheld anything. It closed on 3 registrations across $36.81 and never produced a price worth quotingNo registrationn/a$0.0000
Brand AdZero because its ad set is paused. It closed on a lifetime $0.93 over $156.59, the dearest of the seven ads this campaign ever ranNo follown/a$0.0000
Page Likes · Service FireStill reads status ACTIVE with effective_status ADSET_PAUSED: armed, unable to deliver, and ready to run the moment the campaign restarts with no further actionNo follown/a$0.0000

Every ad in the account that took any delivery on Oct 11. Ads not listed spent nothing that day.

Registrations, day by day

This chart is the Florida CMS campaign only, on the one creative this page spent a week calling worn out, and since Sept 14 it is no longer the whole CMS story: a second campaign launched that day on a new hook across seven states and has its own chart below. Keeping them apart matters, because averaging two campaigns that buy the same event at different prices produces a number nobody can act on. Read the last four bars together and read the money as carefully as the price. Sept 13 finished at 78 cents with no registration because the ad account was disabled for non-payment. Sept 14 finished at $23.38 with no registration on a full funded day. Sept 15 bought six at $5.66 on $33.93. Sept 16 bought three at $7.73 on $23.18, and that bar is short because delivery across the whole account faded out that day, normal until about 9am and gone by 1pm, not because this campaign was throttled. A series that does this is a spread rather than a trend, and every story this page has tried to lay over it, an audience ceiling, a weekday effect and a wear step, has been falsified within a week of being written. The Agency Ceiling campaigns are kept off this chart and have now closed: 5 registrations across $255.15 is a result rather than a rate. Each pair of bars is one day: how many registrations it bought, beside what each one cost, with the weekday and the date underneath. Daily spend now lives in the Day by day section rather than on the axis, which keeps this chart readable as the run grows. A tall teal bar next to a short gold one is a good day.

02$0$5noneTUESep 29noneWED30noneTHUOct 1noneFRI2noneSAT3noneSUN4noneMON5noneTUE6noneWED7noneTHU8noneFRI9noneSAT10noneSUN11noneMON12so far
registrations that day (left axis) what each one cost (right axis) $8.53 lifetime averageLast 14 days shown; full history is in the Day by day section. Weekday and date under each pair; daily spend is in the Day by day section

Does spending more cost more?

$0$5$10$15$20$20$30$40$50FRISATSUNMONTUEWEDTHUFRISATTUEWEDTHUFRISATMONmoney spent that day

If money into a small audience were driving the price up, the dots would climb from left to right. They do not. Across 15 priced days the dearest registrations came on the seventh heaviest day, MON at $19.41, and the two cheapest came on the fifth heaviest and eighth heaviest. No slope. The question this chart was built to test next is whether there is a direction in time. The three most recent days that bought anything, picked out in red, all sit in the dearer half of the chart, ranked 13, 9, 15 of 15 by price. A weekday effect does not put its expensive days at the end of the run; a creative wearing out does, and both weekdays this account has now read twice moved from its cheap group to its dear one. Sep 2 on $0.30 and Sep 13 on $0.78 and Sep 14 on $23.38 and Sep 22 on $29.65 and Sep 23 on $0.00 and Sep 24 on $0.00 and Sep 25 on $0.00 and Sep 26 on $0.00 and Sep 27 on $0.00 and Sep 28 on $0.00 and Sep 29 on $0.00 and Sep 30 on $0.00 and Oct 1 on $0.00 and Oct 2 on $0.00 and Oct 3 on $0.00 and Oct 4 on $0.00 and Oct 5 on $0.00 and Oct 6 on $0.00 and Oct 7 on $0.00 and Oct 8 on $0.00 and Oct 9 on $0.00 and Oct 10 on $0.00 and Oct 11 on $0.00 are complete days that are not on this chart, because they bought no registration at all and so have no price to plot. The money each of them spent is the thing to read: a day with almost none was an account that was switched off, and a day with a full share of budget was a campaign that delivered and did not convert. Sep 3 and Sep 20 are left off, at $23.40 and $51.91 they were learning-phase prices and would flatten everything else.

How much runway is left?

0.01.02.03.04.03.5 fatigue thresholdnot datable while the ad set is paused. The frequency has read 3.39 on a reach of 3,470 for twenty mornings running, 0.11 short of the threshold, and the last two steps are both 0.00, so there is no climb to project. The crossing arrives only after a restart, inside one or two days at the 0.06 to 0.11 steps this series ran while it was deliveringSATMONWEDFRISUNTUETHUSATTUETHUSATMONWEDFRISUNTUETHUSATMON3.39the last two steps average 0.00 a day, so there is no runway to draw

The thirty-seventh reading is 3.39 on a reach of 3,470, identical to the nineteen before it, read at a morning hour on the AD on the Maximum window. A flat step is exactly what a paused ad should produce, and that is the check it passes: the instrument agrees with the status for a twentieth morning of the pause. WHAT THE PAUSE DOES TO THE PANEL. A cumulative frequency cannot move while nothing is served, so every reading from here to a restart will repeat 3.39. With two flat steps in a row the checker's rule has now reached its own undated branch and stays there, so the page prints no crossing date at all. That removes the need for the pause-aware rule while the pause lasts; it does not remove the lag, which will return for two readings after any restart, so the proposal stays with the owner and is NOT executed. WHAT A RESTART MEANS FOR IT. The ad sits 0.11 below the optimization plan's 3.5 fatigue threshold with no second creative in its ad set. At the steps this series ran while delivering, 0.06 to 0.11 a day, a restart crosses it inside one or two days. That is the structural question a restart brings back with it, and it is the owner's.

The new hook, day by day

The seven state campaign, launched Sept 14 on the Same Day script. This is the fresh creative and the geo re-render in one build, and it is the first time this account has had two campaigns buying the same registration event with different creative, which makes the chart above and the chart here the closest thing to a controlled comparison it has ever run. Two complete days have now run side by side and the older creative has won both: 4 at $8.12 against 6 at $5.66 on Sept 15, then 1 at $11.71 against 3 at $7.73 on Sept 16. Lifetime the two campaigns have gone from 24 cents apart to $1.85 apart, $9.02 here against $7.17 there. Sept 16 is the day worth reading closely rather than discounting. Delivery across the account faded out during the day, so both campaigns were cut short on the same curve from the same budget, which is exactly the shock a paired test absorbs and a time series does not. What it exposed is allocation: in the hours the account did run, Meta gave the Florida campaign $23.18 and this one $11.71 from identical $40 budgets. The campaign is four days old and inside its learning phase, which is a real defence and a shrinking one. The reading that breaks it is a complete day above $12, and Sept 16 came in at $11.71.

01$0$5noneTUESep 29noneWED30noneTHUOct 1noneFRI2noneSAT3noneSUN4noneMON5noneTUE6noneWED7noneTHU8noneFRI9noneSAT10noneSUN11noneMON12so far
registrations that day (left axis) what each one cost (right axis) $10 lifetime averageLast 14 days shown; full history is in the Day by day section. Weekday and date under each pair; daily spend is in the Day by day section

Follows, day by day

The same read for the Page Likes campaign, from the Sept 2 relaunch forward rather than the campaign's whole life, because the ads before that relaunch were a different set at a different price. The delivery worry this chart carried for several mornings is closed: the campaign took 110 percent of its budget on Sept 17 and 42 percent by 9am today. What is not closed is the price. Its three dearest days of the whole relaunch are among its last four, and the dashed average line has moved with them. Read the level beside the ratio on the short bars: a $1.01 follow on ten follows is not the same claim as a $0.95 follow on thirty eight, and the chart draws them the same height. What no bar here shows is the thing that actually moves this campaign, which lives one level below it. Five ads were live in this ad set and Meta funded one: Brand Ad took 70 percent of the money on Sept 17 and every cent of Sept 18. This page argued for a week that Meta was starving the set's best creative and that claim was wrong, but the lifetime prices underneath it say something plainer. Brand Ad bought follows at $0.93 over $156.59, the dearest of the seven ads this campaign ever ran. The ad it replaced reached $0.82 over $220.48, on more money than Brand Ad ever had. The owner switched that ad back on at 11:55am on Sept 18, three minutes before pausing the whole ad set, so it now sits ACTIVE inside a paused set: armed, and ready if this campaign restarts. The campaign closed on 748 follows at $0.87 across $653.47.

020$0.00$0.50noneTUESep 29noneWED30noneTHUOct 1noneFRI2noneSAT3noneSUN4noneMON5noneTUE6noneWED7noneTHU8noneFRI9noneSAT10noneSUN11noneMON12so far
follows that day (left axis) what each one cost (right axis) $0.87 lifetime averageLast 14 days shown; full history is in the Day by day section. Weekday and date under each pair; daily spend is in the Day by day section

Does the day of the week explain it?

Closed. Sunday Sept 27 did not deliver at all because every ad set is paused, so it is not a reading and is not added. The record stays at one agreement against six contradictions. The panel closed on Sept 13 and every repeat reading since has been recorded rather than acted on. MONDAY IS THE SIXTH WEEKDAY TO BE READ TWICE AND IT BEHAVES LIKE THE OTHER FIVE. Sept 7 bought four registrations at $8.51; Sept 21 bought two at $19.41, a factor of 2.3 on almost the same money, 97 percent of budget against 85. Nothing about the calendar changed between them. That takes the record to ONE agreement, Tuesday, against SIX contradictions: Wednesday, Friday, Saturday, Thursday, Friday again and now Monday. Every weekday this account has read twice has disagreed with itself except one. A panel that disagrees with itself six times out of seven is measuring noise, and the Thursday pair remains the cleanest demonstration: $19.01 on Sept 10 against $4.98 on Sept 17, a factor of nearly four on the same weekday and almost the same money. Friday is still the only weekday read three times, at $4.06, $9.53 and $12.54, and the third is not comparable on money because Sept 18 spent 157 percent of budget where the other two spent about 95. A panel that was already retired does not get resurrected by a reading it cannot control, and the rows are recorded rather than read. Sept 22 is a Tuesday and it does not join the panel. It bought no registration, so it has no price, and it stopped at 9:02pm when the owner paused the ad set, so it is not a full day of delivery either. The Tuesday row keeps Sept 15 and Sept 8, the one agreement on record. The panel stays on the page as the record of a killed hypothesis rather than a live one. Its value now is that it is the falsification, not the finding.

MONSep 21
$19.412 registrationsFollows no readSep 7: $8.51 on 4 (Monday's second reading, and on a retired panel it is a record rather than a finding. Sept 21 bought two registrations at $19.41 against Sept 7's four at $8.51, a factor of 2.3 on almost the same money, 97 percent of budget against 85. Page Likes was paused, so there is no follow figure. The panel stays retired and this row makes it six contradictions against one agreement)
TUESep 15
$5.666 registrationsFollows $0.95 on 38Sep 8: $3.88 on 10
WEDSep 16
$7.733 registrationsFollows $1.01 on 10Sep 9: $4.65 on 9
THUSep 17
$4.988 registrationsFollows $1.20 on 33Sep 10: $19.01 on 2 (Thursday's third reading. Its own earlier one, Sept 3 at $23.40, was learning phase and was carried but never counted)
FRISep 18
$12.545 registrationsFollows $1.31 on 19Sep 11: $9.53 on 4 (Friday's third reading, and its first on money that is not comparable: Sept 18 spent 157 percent of budget where the other two spent about 95. Its own earliest reading, Sept 4 at $4.06, is the cheapest Friday on record. Read the three together only as a spread)
SATSep 12
$9.244 registrationsFollows $0.61 on 36Sep 5: $4.47 on 6
SUNSep 20
$51.911 registrationFollows no readSep 6: $8.97 on 5 (Sunday's second reading, and on a retired panel it is a record rather than a finding. Sept 20 spent 130 percent of budget for one registration at $51.91, its dearest priced day, against Sept 6 at $8.97 for five; the two are not comparable and Page Likes was paused, so there is no follow figure. The panel stays retired)

Read it as a hypothesis. This panel is kept as a record rather than as a tool, and the repeat readings are why. A cut with one observation per bucket cannot fail, so it read as a finding for three mornings while it was only a shape. Sept 13 added that a complete day is not the same thing as a day with data in it. Sept 14 added the version of that with no outage to blame: the campaign delivered $23.38, served 477 impressions and earned 10 link clicks, and still produced no price, because a cost per registration needs a registration. Sept 15 added the opposite failure mode, a confirming reading arriving at a cut that had already failed twice. Sept 16 adds the one that should have been obvious from the start: a bucket labelled WED holds whatever happened that day, including a day whose delivery died out after lunch, and the label gives no way to tell the difference. Sept 18 adds the last one it had left: a bucket labelled FRI also holds whatever budget the day ran at, and a day that spent 157 percent of budget is not the same measurement as one that spent 95, however neatly it sorts into the same column.

What to do about it. Do not weight any budget by weekday. Six weekdays out of seven have contradicted their own first reading, and the panel has nothing to add while the account is paused. The one live question on this account is no longer about the calendar or the creative, and as of 9:02pm on Sept 22 it is no longer even about pacing. It is whether and when the owner restarts the last ad set now that the CMS 2027 angle has decayed, on Oct 1. If it restarts, the budget question comes back with it: four of the last five closed days ran 157, 170, 130 and 97 percent of a $40 budget, and the trailing week reads 112 percent of the weekly one.

What the next two weeks should produce

Rebuilt on the delivering days between Sept 10 and Sept 16, and this window is in worse shape than any before it. Sept 13 is excluded because the account was disabled that day and bought nothing anywhere, and this sentence is the label on that filter. Sept 16 is included and it is the reason every central figure below fell: the account delivered for about nine hours that day and spent $86.02 of $209 committed, and dropping it would have propped all three cards up at exactly the moment that would have been most convenient. So these numbers rest on a seven day window holding one dead day and one half delivered day, and the honest expectation is that they are too low rather than too high. Three cards rather than two, because a second CMS campaign exists now, and its card is still a placeholder rather than a forecast, with a range set deliberately at half to one and a half times its central figure. Neither Agency Ceiling campaign is forecast: both stopped on Sept 17 and they closed on 5 registrations across $255.15, which is $51.03 each.

CMS 2027 Final Rule, Florida

$40 / day nominal, and PAUSED at ad set level by the owner since 9:02pm Sept 22. Nothing on the account is committed while it stays off

Basis 27 registrations on $314.22 across the seven delivering days from Sept 16 to Sept 22, which is $11.64 each. Lifetime is 89 on $759.38, or $8.53. Expected delivery $0 while paused. On a restart, $40 / day nominal, which meant $68.07, $51.91, $38.82 and $29.65 on its last four delivering days, the last cut short by the pause, which is 0% on every full day since the pause, Sept 23 to Oct 11. Its last seven delivering days, Sept 16 to Sept 22, ran 112% of a weekly budget. 89 registrations to date so far.

One day, IF restarted today (the old horizon ended Sept 30)conditional
10 registrationsrange 4 to 17
on $0 while paused. A restart at the nominal $40 is $40 against about $311 left, and about $45 at the rate the last seven delivering days actually ran of spend

THIS CARD PRICES A DECISION NOBODY HAS MADE. The owner paused the last live ad set at 9:02pm on Sept 22, so the account's real forecast is zero spend and zero registrations until it restarts, and the page does not know whether it will. The figures above are what one day at the nominal $40 would buy at the seven delivering days' own rate of $11.64 a registration, with the low end at the mean of the three dearest priced days in that window and the high end at the mean of the three cheapest. Two things come back with a restart and neither is priced here. The money: about $311 of the roughly $500 is unspent, so a restart has room at the nominal $40 and at the 170 percent the budget reached on its worst day. An account level spending limit would cap the total whatever the daily rate does, and that is a billing action only the owner takes. And the frequency: the ad sits 0.11 below its 3.5 fatigue threshold with no second creative in the ad set, so a restart crosses it inside a day or two. The CMS 2027 angle decayed on Oct 1, so the days already gone cannot be bought on it.

A note on what this card cannot seeconditional
the Oct 1 decayrange n/a to n/a
on not applicable of spend

The CMS 2027 angle decayed on Oct 1, the day after the old twelve day horizon ended on Sept 30, so every day inside that horizon was worth more than any day after it. Whether the roughly $500 is a willingness to spend or hard cash decides whether a hard cap would have helped, and this page cannot tell which and does not guess. It is also why the card prices one day and not a month: a longer horizon would price days of an angle that has expired.

Spend, honestly. Sept 17 closed at $108.98 against the $116 then committed, 94 percent, delivered across the whole day, which settled the question Sept 16 opened: that day was an event and not a new level. Sept 18 opened as the fastest start the account has recorded, $62.22 by 9am, and then changed shape at midday when the owner paused two of the three ad sets to conserve budget. HOW IT WAS PAUSED IS THE THING TO CARRY FORWARD. `CMS 2027 | SE7 | Broad` and `Page Likes | FL | Interests` were paused AT AD SET LEVEL. Both parent campaigns still read ACTIVE and every ad under them still reads ACTIVE; only the ad set says otherwise. A campaign-level read of this account now reports two live campaigns that cannot spend a cent. That is the third distinct way in one week that something here has read as on while not running, after a disabled account and a paused ad the page called active. Billing cadence stays a first class signal because it is the only thing that has ever explained a delivery fade here: eleven charges on Sept 15, two on Sept 16 with a 21 hour gap and a fade from 9am, five on Sept 17, three by 8:39am today. Every charge reads Paid, none failed since Sept 13, and the threshold keeps moving, so read the cadence rather than the level. SEPT 18 CLOSED AND IT BROKE THE PLANNING ASSUMPTION. The account finished at $117.29 against the $116 committed at midnight, which reads as an ordinary 101 percent day and is nothing of the sort: two of the three ad sets were switched off at 11:58am, and the Florida campaign ran all twenty four hours to $62.71 on a $40 budget, 157 percent. The hourly rows sum to exactly that figure with every hour present, and impressions and reach rose with the money, so it is real spend rather than a rendering fault. Through 11:59am all three campaigns were pacing between 140 and 157 percent of their own budgets, which makes it a property of the day rather than of one campaign. Billing cadence stays a first class signal: five charges on Sept 17, eight on Sept 18 with the threshold stepping down from $25 to $10 during the day, two at $17 so far today. Every charge reads Paid and none has failed since Sept 13, so nothing here is a payment problem. SEPT 19 AND SEPT 20 CLOSED AND LOOKED LIKE A SETTLED REGIME. The Florida campaign ran $68.07 and $51.91 on its $40 budget, 170 and 130 percent, so with Sept 18 that is three straight days over budget and the overspend is a regime rather than a one-off. The trailing seven days spent $302.98 against the $280 that seven days at $40 commits, 108 percent of the weekly budget, which kills the catch-up reading that had been parked as a benign explanation. Billing stayed clean throughout: four charges on Sept 19, three on Sept 20, the threshold now at $17, and nothing failed since Sept 13, so none of this is a payment problem. SEPT 21 CLOSED INSIDE BUDGET AND IT IS THE FIRST DAY IN FOUR THAT DID. The Florida campaign ran $38.67 on its $40 budget, 97 percent, across a full twenty four hours whose rows sum to exactly that figure with every hour present. The dated instrument assertion written on Sept 21 said the day would come in at or under $48 or the overspend had persisted into a fourth day; it grades RIGHT on its number and RIGHT on its reason. Billing stayed clean: two charges on Sept 21 and one at 12:38am on Sept 22, the threshold holding at $17, nothing failed since Sept 13, and the activity log carries no owner action and no budget change since Sept 20, so neither the overspend nor its pause is an edit. ONE DAY DOES NOT END THE REGIME AND THE WEEKLY NUMBER IS WHY. The trailing seven days, Sept 15 to Sept 21, spent $318.35 against the $280 that seven days at $40 commits, 114 percent of the weekly budget and HIGHER than the 108 percent reported a day ago, because a cheap day rolled out as this one rolled in. Four closed days now read 157, 170, 130 and 97 percent. For planning: committed spend is $40 a day nominal, all of it Florida, against about $341 left for the nine days to Sept 30. Nine days at the nominal $40 is $360, which still overshoots, and at the rate the last three days ran it is about $476. Nine days like Sept 21 would be $348. The floor still overshoots, so an account level spending limit is still the only instrument that makes the month real, and the case for it is now tight rather than overwhelming. SEPT 22 CLOSED AT $29.60 AND THEN THE OWNER STOPPED THE ACCOUNT. The Florida campaign ran to 9:02pm and the activity log records the owner setting its ad set from Active to Inactive in Power Editor at that minute; the twenty two hourly rows sum to exactly $29.60 and the 21:00 hour carries five cents. Billing stayed clean with two charges on Sept 22, $17.00 at 12:38am and $25.00 at 7:39pm, the threshold stepping up from $17 to $25, and nothing failed since Sept 13. For planning: committed spend is now ZERO while the ad set stays paused, against about $311 left. A restart at the nominal $40 would need eight days of $320 to reach Sept 30, which slightly overshoots, so the spending limit recommendation returns with any restart. SEPT 23 SPENT NOTHING, AS IT SHOULD HAVE. Every unit closed at $0.00, there were no charges, and the activity log shows no owner action after 9:02pm on Sept 22. Meta restated the two last delivering days upward by twenty cents in all, so about $311 still remains. With seven days left, a restart at the nominal $40 is $280 and fits; at the rate those last seven delivering days ran it is about $314 and does not. SEPT 24 SPENT NOTHING EITHER, AND THIS TIME NOTHING WAS RESTATED. Every unit closed at $0.00, no charge, no owner action in the log. With six days left, a restart at the nominal $40 is $240 and at the recent actual rate about $269, so both fit inside about $311 for the first time; six days at the worst multiple on record, 170 percent, would be about $408, which is why the spending limit still belongs in front of any restart. SEPT 25 SPENT NOTHING AND NOTHING WAS RESTATED. With five days left, a restart at the nominal $40 is $200 and at the recent actual rate about $224; five days at the worst multiple on record would be about $340, still above the roughly $311 left. SEPT 26 SPENT NOTHING AND NOTHING WAS RESTATED. With four days left, a restart at the nominal $40 is $160 and at the recent actual rate about $180; four days at the worst multiple on record would be about $272, which for the first time fits inside the roughly $311 left. SEPT 27 SPENT NOTHING AND NOTHING WAS RESTATED. With three days left, a restart at the nominal $40 is $120 and at the recent actual rate about $135; three days at the worst multiple on record would be about $204, inside the roughly $311 left. AS OF OCT 6 NOTHING HAS SPENT SINCE SEPT 22, so those day counts are history; the live figure is about $311 unspent against a calendar that has moved on to October.

Method. THE METHOD CHANGED AT MIDDAY ON SEPT 18 AND THE REASON IS WORTH STATING. Until today these cards answered 'how many results will the current pace buy', which is a question about efficiency. The owner has now capped the month at about $500 and paused two of the three ad sets, so the binding question is 'how far does the money go', which is a question about arithmetic. The horizon is therefore the CALENDAR, Sept 19 to Sept 30, twelve days, rather than a rolling seven and fourteen. Efficiency is still results per dollar across the delivering days in the trailing seven day window, Sept 11 to Sept 17, with Sept 13 excluded because the ad account was disabled for non-payment and bought nothing anywhere. Excluding it is a filter and this sentence is the label on it. Sept 16 stays in, on the same reasoning it has always stayed in: it was a real funded day that bought real results, and dropping a short day would flatter the card. The low end is the money at the mean of the three dearest priced days in the window and the high end is the mean of the three cheapest. Nothing here assumes a new creative, a targeting change, or a budget change; a throttle to $36 a day is under discussion with the owner and is NOT priced in. ONE ASSUMPTION THIS CARD USED TO MAKE SILENTLY IS NOW BROKEN AND IS STATED INSTEAD. It assumed a $40 daily budget produces about $40 of spend. On Sept 18 the Florida campaign spent $62.71 on that budget, 157 percent, across a full twenty four hours, and the other two campaigns were pacing to 150 and 138 percent when they were paused at midday. So the twelve day figure is printed as a RANGE bounded below by the nominal budget rather than as a central estimate around it. The seven state campaign and Page Likes carry no forecast: both were paused at ad set level at midday and their closing figures are on their cards. Both Agency Ceiling campaigns closed on Sept 16. THE CALENDAR HORIZON CLOSED ON SEPT 30. While the account stays paused this card prices one restart day and nothing longer, because a longer horizon would price days of an angle that has expired.

Rolled forward on Oct 12, the twentieth morning with every ad set paused. While it stays paused the forecast is zero; the card below prices a one day restart, because the old calendar horizon closed on Sept 30 and only the owner can reopen it.

How the calls are holding up

Two ways of holding this account, and the process running it, to account. The decisions table grades recommendations that have already resolved. The projections table holds every dated call open until its date, then writes what actually happened beside what was projected. As the dates below arrive the pending rows fill in, so a week from now this reads as a record of what was expected against what came true rather than a fresh set of confident guesses.

Decisions, graded

DateThe callWhat happenedVerdict
Sep 22ownerPause the last live ad set, CMS 2027 | FL | Leads. The owner's own action at 9:02pm, recorded here rather than recommended by this pageACTED ON by the owner in Power Editor at 9:02pm, per the activity log, at ad set level, so the campaign and its ad still read ACTIVE while nothing can spend. It stops the overspend question by stopping the spend, with about $311 of the roughly $500 left. The log records who and when and never why, so this page does not know whether the pause is a hard stop for the month, a hold, or a reset before a restart, and it does not guess. It stays ungraded until the owner's next action says which: an outcome needs a stated intent to be measured against, and none is on the record yet.Pending
Sep 21processSet an account level spending limit. A throttle is no longer an equal option, because three straight days proved the budget is not a ceilingOVERTAKEN ON SEPT 22, NOT ANSWERED. The owner paused the last live ad set at 9:02pm, which caps spend absolutely for as long as it lasts, so this recommendation has nothing to act on while the account is off. It is left open deliberately rather than closed, because it returns in full with any restart: the budget has behaved as a rate with a spread, and eight days at the nominal $40 is $320 against about $311 left. Earlier reasoning follows. Open with the owner, and Sept 20 removed the second option rather than just re-weighting it. The Sept 19 row already recommended a limit over a throttle; this row records that a throttle is now off the table on its own. The reason is that the overspend is a multiple, not a level: Florida closed at 157, 170 and 130 percent of its $40 budget on Sept 18, 19 and 20, and a throttle to $36 lowers the nominal number while the multiple keeps applying, so a 170 percent day on $36 is still $61. Only an account level spending limit caps the total whatever the daily rate does, and it is a billing setting the owner alone can change; this page will not touch it. The month is now the binding number: about $380 left for ten days to Sept 30, ten days at even the nominal $40 is $400, and at the observed $60.87 a day it is about $609. The counter-argument is unchanged and not dismissed: the CMS 2027 angle decays Oct 1, so if the $500 is a willingness to spend rather than hard cash, the honest move is to raise the limit rather than leave delivery to halt mid-horizon.Pending
Sep 19processSet an account level spending limit at $500. Throttling to $36 a day is now the weaker of the two options, not the equal one. SUPERSEDED by the Sept 21 row above, which removes the throttle entirelyOpen with the owner, and Sept 18 changed which half of yesterday's either-or to recommend. That day the Florida campaign closed at $62.71 on a $40 budget, 157 percent, across a full twenty four hours, with the hourly rows summing exactly and impressions and reach rising with the money. A throttle scales the nominal number: $36 a day makes the floor $432 instead of $480. It does nothing about the multiple, so if 157 percent recurs a $36 budget still produces a $56 day and the month still overruns. A spending limit caps the total whatever the daily rate does, which is the only mechanism that makes $500 real rather than estimated. It is a billing setting and an owner action; this page will not touch it. The argument against capping at all is unchanged and is not dismissed: the CMS 2027 angle decays Oct 1, so days inside this horizon are worth more than days after it, and a limit that halts delivery on Sept 28 costs registrations at the only moment they are worth buying. If that is the owner's read, the honest version is to raise the $500 rather than to leave a cap that is not enforced.Pending
Sep 18processThrottle Florida to $36 a day so the month's $500 has real margin, or set an account spending limit instead. SUPERSEDED by the Sept 19 row aboveOpen with the owner, and it is arithmetic rather than judgement. With the seven state and Page Likes ad sets paused, Florida at $40 a day is the account's entire commitment. Sept 19 to Sept 30 is twelve days, so $480, plus about $10 left in today: roughly $490 against about $500. That fits with two percent of margin, and two percent is not margin, because Meta can run a daily budget about a quarter over on a given day while holding the weekly average and this account has already delivered 100 and 110 percent of budget days. $36 a day spends about $442 and leaves real headroom, at a cost of roughly four registrations. The alternative, and the only one that makes the cap real rather than estimated, is an account level spending limit set to $500, which is a billing setting and an owner action this page will not touch. The argument against throttling at all is on the record too: the CMS 2027 angle decays Oct 1, so every day inside this horizon is worth more than any day after it, which favours spending the full amount if the $500 is a willingness to spend rather than a hard cash limit.Pending
Sep 18processPut the Page Likes budget on the cheaper creative, or say why not. Switching Service Fire back on is the specific ask. ACTED ON by the owner the same dayOpen with the owner. The case is a lifetime price comparison at comparable spend rather than a claim about what Meta is doing, which is the form this argument should have taken a week ago. Brand Ad takes all but a sliver of the campaign and buys follows at $0.93 over $156.59, the dearest of the seven ads this campaign has run. Page Likes | Service Fire | FL is paused and reached $0.82 over $220.48, more money than Brand Ad has ever had, including $90.57 across Sept 8 to Sept 12 at $0.83. Three other live ads are also cheaper on thinner records. This page has been wrong about this ad twice in opposite directions inside a week, which is a reason to state the recommendation narrowly rather than to withhold it: switch one paused ad back on, at no extra budget, and read it for three funded days. THIS WAS RECORDED AS WITHDRAWN AND THAT WAS WRONG, corrected on Sept 19 from the activity log. The owner ACTED ON IT: at 11:55am on Sept 18 he switched `Page Likes | Service Fire | FL` back to Active, and at 11:58am, three minutes later, he paused the ad set to conserve budget. The ad now reads status ACTIVE with effective_status ADSET_PAUSED. So it is armed rather than moot, it took $0.00 on its first nominal day because its ad set is off, and it will deliver the moment the campaign restarts with no further action. The finding under it does not expire and is the first thing to read if this campaign is ever restarted. Worth noting how this was found: the previous run had already established that the activity log does NOT carry ad-level pauses, so the log was being treated as unreliable for ad status. It does carry ad-level ACTIVATIONS, and reading it is what caught this.Pending
Aug 31 to Sep 6processThe constraint is the Florida audience ceiling, so scale is limitedSept 8 bought ten registrations at $3.88 on the heaviest sane spend of the week, and five days sorted by money show no relationship between spend and price. The ceiling was a weekday effect plus noise.Wrong
Sep 6 to Sep 9processVerify the registrations against WebinarJam before scalingThe owner checked on Sept 9. They are real. It is now the basis for the second raise, which is exactly what the caution was for.Right
Sep 7processHold CMS at $33, do not raiseThe owner overrode and raised to $36. Sept 8 then answered the test at $3.88, so the raise was right and the hold was wrong.Wrong
Sep 7ownerRaise both budgets 10 percentSept 8 delivered the best finished day on the account. Vindicated.Right
Sep 8processCut CMS V1 and CMS V2Switched off. Nine days live, 627 people reached between them, zero registrations.Right
Sep 8processCut Page Likes Image B OwnershipRecommended three mornings running, then withdrawn on Sept 9 when it came to par at $0.89 and bought follows at $0.69. Meta had already starved it. The cut was never justified.Wrong
Sep 9ownerRaise both budgets a second 10 percent, to $40 and $36Three finished days on the new budgets bought 15 registrations for $117.94, which is $7.86 each, against $5.29 across the five days before the raise. Page Likes was untouched by it and stayed in its band. The read is mixed rather than bad, and the reason is that the window was never clean: the ad set lost its second unit inside it and the winning creative's daily click-through settled at about half its first week. Volume held and price did not, and the raise cannot be separated from the wear.Mixed
Sep 9processLeave Legacy pausedThirteen days without delivery. The gap to CMS is $35.52 a registration against $7.17. The comparison that was briefly offered against this pause has now closed: both Agency Ceiling campaigns finished dearer than Legacy, $43.47 on the broad one and $81.27 on the licensee one. Two campaigns priced above the campaign this pause is questioned over is the strongest version of the case so far, and it is now an argument from finished campaigns rather than from partial days.Right
Sep 10processHold both budgets at $40 and $36, change nothing todayThe two days that followed were the two dearest on the account, $19.01 and $9.53, so adding money would have bought the worst registrations of the run. Right, and right for a reason this process did not give: it held to protect a test window, not because it had seen the price turn.Right
Sep 10processMove the geo re-render off the critical path, target Sept 20 rather than Sept 17Reversed by this process within twenty four hours. The reprieve rested on one 0.07 frequency increment; the next reading was 0.16 and the click-through rule tripped the same morning, which put a fresh hook back on the critical path. Corrected Sept 17: the asset that eventually shipped was not a fresh hook, so this lever was never actually pulled. The date it argued about was never the reason the build mattered.Wrong
Sep 10processKeep CMS Social B running, on notice until Sept 13The owner switched it off on Sept 10 rather than waiting for the date. It had produced nothing on three consecutive funded days, so the days the deadline would have bought it would have bought nothing. This row should have been graded on Sept 11 and was not, which is recorded below rather than quietly fixed.Wrong
Sep 11ownerSwitch CMS Social B offFour registrations at $8.78 over its life and nothing on any of its three funded days. Nothing since has argued for keeping it, and the cost of being right is that the ad set has no second unit.Right
Sep 11ownerLaunch The Agency Ceiling campaign at $43 a day into its Sept 17 webinarClosed. It finished on 4 registrations across $173.88, a price of $43.47, with nothing bought after Sept 12 and four complete funded days spent proving it. The campaign does work in the sense that matters first, which is that it converts at all, and it converts at six times what the Florida CMS campaign pays. Whether that is acceptable is not a question this page can answer, because it does not know what an agency owner registration is worth to HPM and will not assume a number, so this is graded mixed rather than wrong. What is not ambiguous is the shape of the failure: the campaign bought three of its four registrations in its first two days and then spent $173.88 minus those days without buying a fifth.Mixed
Sep 11processHold all three budgets, change nothingFriday finished dearer than every day before Thursday, so money added that morning would have bought registrations at $9.53. The hold was right on the day it covered.Right
Sep 11processBuild a fresh CMS hook, as the geo re-render, and treat it as the critical pathDone, on Sept 14, and by the owner rather than by anything on this page. The Same Day script was locked and shipped as Same Day A | Know It Cold into a new broad seven state campaign, which was recorded at the time as the fresh hook and the geo re-render in one build. Corrected Sept 17: it is the geo re-render only. Its locked script carries the same CMS deadline claim and nearly the same payoff line as the ad it replaced, and it was never registered in the content engine. It bought 2 registrations at $5.13 on its first part day while the Florida ad bought none on more than twice the money. The call is graded right on the action and it was wrong about the mechanism: it argued for five mornings from a falling click-through, and the new creative's day level click-through is 2.15% against the old one's 2.10%, which is the same number. The new hook is converting better, not clicking better, and this page did not predict that.Right
Sep 12processRetire the weekday panel as a live hypothesis and stop weighting anything by daySaturday gave the panel its second repeat reading a day after Friday gave it the first, and it failed the same way: $4.47 on Sept 5 against $9.24 on Sept 12. Two weekdays read twice, two moves from the cheap group to the dear one, both on similar money. The retirement was right and it was right a day sooner than the date it named.Right
Sep 12processRead The Agency Ceiling campaign as a video cut that converts and statics that do notThe static offer card bought a registration on Sept 12 at $15.94, its first, the morning after this page recorded that the campaign's two statics had spent $18 between them and bought nothing. The claim rested on two funded days with one observation per creative, which is the same instrument that carried the weekday panel for three days. The format lesson stands on the CMS campaign, where four creatives ran for nine days. It does not stand here yet.Wrong
Sep 13ownerSwitch AC | You Lead offClosed, and the cut was right. The ad was switched off after three funded days and $15.63 with no registration, and the timing looked uncomfortable because the static it most resembles had converted the day before. The final prices settle it: the campaign bought nothing at all after Sept 12, the offer card it resembled never converted again and its lifetime spend has not moved since, and the 42 second cut spent $89.11 across the four days that followed for nothing. The cut removed an ad from a set that had stopped working rather than one that was about to start.Right
Sep 13processWatch Page Likes on delivery rather than on price, and downgrade its forecastAnswered on the first complete day after restoration: Sept 14 spent $37.65, which is 105 percent of budget and the campaign's heaviest day in a week, so the five day fall was a dip and the downgrade attached to this call was wrong. The method was right and the conclusion was not, which is why this grades mixed. It is also worth what it found on the way: on that same day the follow price read $1.02, over a dollar for the first time, because Brand Ad took 90 percent of the money at $0.99 while the volume leader took nine impressions. The watch should now be on allocation, which neither the price rule nor the delivery rule covers.Mixed
Sep 13processHold all three budgets, change nothing todayRight, and right for none of the reasons it gave. It argued from the CMS price, the new campaign's overspend and the Page Likes underdelivery. What actually happened is that Meta failed to charge the card three times that same day and disabled the account, so a budget raise made on Sept 13 would have raised a number attached to campaigns that then spent $1.54 between them. The hold was correct and the process had no idea why.Right
Sep 14processPay the $19.10 balance and restore the ad account before anything else is consideredPaid, and the account is Active again. Every live campaign reads Active rather than Payment error, the balance is $8.78, and there has been no failed charge since Sept 13: two charges cleared on Sept 14 and eight on Sept 15, all on the same card ending 5235, though the billing threshold has moved off $18 to $21 and $10 amounts. Delivery resumed on Sept 14 and the account spent $120.37 that day. This was the only thing on the page that mattered and it was an owner action throughout.Right
Sep 14processVoid the two dated calls whose evidence the outage destroyed rather than grading themBoth halves closed and neither date was ever moved outward. The Page Likes delivery call was re-dated from Sept 14 to the first two complete days after restoration and graded right on Sept 15, killing the forecast downgrade attached to it. The step-or-slide call was re-dated from Sept 19 to Sept 16 and graded wrong on Sept 16, on a day that came in under its own stated floor. Two re-datings, both moving earlier, both closing against the argument attached to them. A process re-dating in order to dodge does not produce that pattern, so the move is recorded as legitimate on its own evidence rather than on its own say-so.Right
Sep 14processAdd a delivery assertion to the consistency checkerIn place and it passed, which is the weakest kind of pass: the account ran on Sept 14, so the assertion never had to fire. It has not been exercised in the failing direction and should not be counted as proven until it is. What today did test is a gap the same family of checks still had, and two more assertions were added for it: the closed day panel's campaign rows must sum to its stated total and its budgets to its stated commitment, and the account wide CMS spend column must equal the two CMS campaign series added together. The account went from three live campaigns to five overnight and nothing on this page would have noticed a whole campaign being left out of the closed day.Right
Sep 12processDo not scale The Agency Ceiling campaign on its first registrationFour funded days in, and the caution has paid twice over in opposite directions. The second day halved the price to $21.48, which would have made a Sept 12 scaling decision look wrong by 60 percent inside a day. Then Sept 14 and Sept 15 spent $53.33 between them and bought nothing at all, taking the lifetime price to $34.81 on a count still frozen at 4. Scaling on either of the first two readings would have put money into a campaign that has now gone two funded days without a registration and stops on Sept 17.Right
Sep 15processPause the licensee Agency Ceiling campaign and let the broad one run to its Sept 17 stopClosed, and the campaign it named was the weaker one by a wide margin. Final prices are $81.27 on the licensee campaign for its single registration against $43.47 on the broad one for four. The recommendation identified the right target on the evidence available on Sept 15, which is what it is graded on. It was never acted on, and it was withdrawn a day later on separate grounds that are graded in their own row. The one fact that cuts against it stays on the record: the registration the licensee campaign did buy cost $6.58 at ad level, which is the cheapest the whole Agency Ceiling buy produced.Right
Sep 15processTreat the two CMS campaigns as a creative test rather than as a replacementGraded WRONG, and the paired structure still earned its keep, which is why the grade is on the label rather than the design. The paired arrangement absorbed the Sept 16 delivery shock that ruined every time series on the page, which was real value. But the CALL was to treat the two as a CREATIVE test, and that framing was falsified on Sept 17 (F5): both arms carried the same CMS deadline claim and the same belief, so nothing here ever tested creative. The arm was then paused at ad set level on Sept 18, closing any remaining read as destroyed evidence (lens 6g). A call that is right about its mechanism and wrong about what it measures is graded wrong.Wrong
Sep 15processReconcile the 29 unverified registrations in WebinarJam before any scaling decisionDone. The owner confirmed on Sept 16 that the registrations are verified, which covers the 29 this row was about and the six added after it. The account's output is not inflated and no campaign on this page is priced off an unchecked number. The row is graded right on the recommendation and it is worth noting what it cost to be right: it was raised on six consecutive mornings and the share it was about grew on every one of them.Right
Sep 15processPublish or discard the two unpublished drafts sitting in Ads ManagerCleared inside a day. Ads Manager now shows no draft count at all and the Review and publish control is inactive, and Same Day B | Ready Client is live and in the learning phase on $1.63 and 25 people reached, so the locked A/B has both arms for the first time. The edit that was sitting unpublished on the live Same Day A is also gone from the queue. This check does not touch drafts and did not touch these; the owner cleared them.Right
Sep 16processHold both CMS budgets through Sept 17, the comparison's third complete dayHeld. No budget was touched, and the second complete day went the same way as the first: 3 registrations at $7.73 against 1 at $11.71, on a day whose delivery faded out on both of them together. The Florida campaign has now won both days on count and on price, its lifetime price improved to $7.17 while the seven state campaign's worsened to $9.02, and the gap between them widened from 24 cents to $1.85. Sept 17 is the third complete day and it is the first clean one, because the Agency Ceiling campaigns are gone and the account is running normally this morning. Resolves Sept 18.Right
Sep 16processWithdraw yesterday's recommendation to pause the licensee Agency Ceiling campaignClosed and the withdrawal was right, on the arithmetic it was made on. The campaign spent $20.82 on Sept 16 and nothing on Sept 17, so a pause executed on Sept 16 would have saved $20.82, not the $150 the original argument assumed, and it would have cost the registration that came in at $6.58 at ad level, the cheapest the Agency Ceiling buy ever produced. The withdrawal reasoned from the calendar rather than from the campaign getting better, and the calendar is what actually settled it.Right
Sep 16processStop arguing creative wear from day level link click-through on this accountStanding, and the follow-up reading is more interesting than the correction. The two CMS ads read 3.73% and 3.30% on Sept 15, 3.77% and 3.03% on Sept 16, and 3.47% and 2.48% so far today. The gap between them has widened from 0.43 to 0.74 to 0.99 points on three consecutive reads while both sit far above the old band. So they are no longer moving in perfect lockstep, and the dated call on exactly this resolves Sept 18 at a one point bar it is now touching. The correction stands either way: what was falsified was arguing wear from one ad's number without checking the others, and that check is what is producing this reading.Right
Sep 16processFund Service Fire deliberately for three days or drop the starvation argumentWrong, because the ask was built on a false picture of the ad. It is PAUSED and has been since Sept 13, so no budget floor was ever available to set, and it had already been funded properly: $220.48 across its life for 268 follows at $0.82, including $90.57 across Sept 8 to Sept 12 alone. That is the largest spend of any ad in the set and the second cheapest price in it. The recommendation should have been to look at what the ad had already done, which took one query, rather than to ask for three days of new money. What replaces it is a different and much cheaper ask, carried below: the campaign's money now sits on Brand Ad at $0.93 lifetime, the dearest of the set, while the ad at $0.82 is switched off.Wrong
Sep 16processReconcile the 35 unverified registrations in WebinarJam, sixth morning of askingAnswered the same day it was raised. The owner confirmed the registrations are verified, so all 76 are checked and the 46 percent unverified share closes to nothing. Every price on this page, the Florida against seven state comparison included, now rests on a count that has been looked at. What replaces the caveat is a boundary rather than nothing: a verification is true on the date it was made, and this account has now watched the unverified share regrow from zero to 46 percent in seven days without anyone deciding to let it. The standing instruction is changed accordingly, from raise it every morning to raise it when the share passes about a third or a scaling decision is on the table.Right
Sep 17processReport the Sept 16 delivery collapse and change nothing on the accountThe account spent $86.02 of $209 committed on Sept 16 and delivery faded out during the day, and every diagnostic this page can reach says the account was healthy: all five campaigns read Active, no charge failed, the balance is $10.80 and there is no payment error anywhere. Delivery is normal again this morning. There is a real temptation on a morning like this to adjust something, and there is nothing to adjust: no budget, ad or objective was changed by this check, and the finding is handed over as a question for the owner rather than as an action. The first version of this row said delivery stopped dead at 9am; that was a misread of a truncating grid and is corrected in its own row below. Resolves Sept 18 on whether Sept 17 finishes normally.Right
Sep 17processAdd a delivery collapse assertion to the checker rather than loosen the one that did not fireThe Sept 14 assertion fails the page when a closed day spends under a fifth of what was committed and the page does not say why. Sept 16 spent 41 percent, so it passed silently on the worst delivery day since the outage. The tempting fix is to raise that threshold on the morning it would have caught something, which is the move this page has a standing rule against. Instead a second and independent assertion was added: a closed day whose spend falls by more than half against the previous complete day must be named on the page. The Sept 14 threshold is left exactly where it was, and whether to raise it is an owner call rather than a quiet edit.Right
Sep 17processKeep Sept 16 inside the forecast window rather than excluding it as an outage daySept 13 is excluded from every forecast basis because the account was disabled and bought nothing. Sept 16 delivered for about half a day, bought 5 registrations and 10 follows at ordinary prices, and dragged all three central figures down: CMS Florida from 29 to 22, Page Likes from 304 to 256. Excluding it would have held those figures up and would have been indefensible, because the same argument was refused on Sept 14 for a day that was worse. It is included, and the method note says in plain terms that these numbers are probably too low rather than too high.Right
Sep 17processRead the hourly breakdown as showing no delivery after 9am on Sept 16Wrong, and the owner caught it within hours of publication. Ads Manager's hourly grid renders about nine rows and will not scroll further until its own vertical scrollbar is dragged; the mouse wheel does nothing and the document reports no overflow. This check read the nine rows it was given and published an account that stopped dead at 9am. Dragging the scrollbar shows the Florida campaign delivering to 1pm, the seven state one to 11am and Page Likes to 2pm, with thirteen Florida rows summing to exactly its $23.18 day. The control that would have caught it in one pull was never run: Sept 15, a full day that delivered until 11pm, shows the identical nine rows ending at the identical hour. The underlying event survives in weaker form, a fade rather than a stop, and the reasoning that produced it does not. Every surface carrying the original claim was corrected the same day rather than quietly edited.Wrong
Sep 17processMove the whole data path onto the Meta Ads API connector and demote the browserThe facebook-ads MCP connector authenticated against 70137393 on the evening of Sept 17, ending a thirteen day failure. It returns any window at any level in one call, returns the complete hourly breakdown for every campaign with no row cap, exposes actor_name on every account change, and reaches the public Ad Library. It answered in three calls what the browser could not answer in thirteen days, including the cause of the Sept 16 fade. The morning check now pulls from it and uses Chrome only for visual confirmation. The trap that produced this morning's wrong finding is gone with the tool; the lesson it taught is kept as a standing lens.Right
Sep 17processTreat the Sept 16 fade as billing velocity, report it, and still change nothingAccount billed events per day: eleven on Sept 15 supporting $181.58, two on Sept 16 with the last at 7:32am and then a 21 hour gap, five on Sept 17 supporting the $108.98 it finally closed at. Delivery faded ninety minutes after that last Sept 16 charge and recovered when charges resumed. The hypothesis is that Meta throttles delivery when it cannot take the next threshold charge, and nothing reads as failed because the charge is never attempted. Three days of correlation with a mechanism, not proof, and the falsifier is a standing check rather than a one-off. No budget, ad or objective was touched, and the recommendation to do nothing on Sept 16 is now graded correct by the Sept 17 recovery.Right
Sep 17processKeep every write capability the API unlocks behind the same owner approval as beforeThe connector exposes campaign, ad set, ad and creative creation, media upload, budget and status edits, audience management and experiment setup. Until today the prohibition on publishing, pausing, editing, budgeting and spending was enforced partly by how awkward the browser made it. That friction is gone and the rule is not: everything outward or financial still waits for the owner, and the only thing that changed is that breaking the rule got easier. Recorded here so the record shows the decision was made deliberately on the day the capability arrived, rather than assumed.Right
Sep 15 to Sep 17processReport the Florida against seven state gap as a creative result, worn hook beaten by fresh hookPublished for three consecutive mornings across the dossier, the State section and the briefs, and it was never a creative comparison. Both arms carry the same CMS deadline claim and the same belief, the seven state script says in its own purpose line that it replaces the earlier copy with the same payoff, and that asset was never registered in the content engine, so it had no declared belief to compare on. A cold external reviewer asked the question this page never asked its own test. The result survives as a campaign finding about geography, maturity and allocation; the creative verdict does not survive at all.Wrong

28 of 41 graded calls right owner 3 of 5 · this process 25 of 36 The owner's calls held without exception until today, and today one of them came back mixed. The Agency Ceiling campaign was launched into a dated webinar at $43 a day and it finished at $43.47 a registration, six times what the Florida CMS campaign pays. It is graded mixed rather than wrong for a reason worth stating plainly: this page does not know what an agency owner registration is worth to HPM and will not invent a figure to grade a call with. This automated process is behind on its own, and on Sept 17 it added a new kind of error to the record. Its previous failures were all of one shape, reading a pattern into a series too short to carry one. This one was different and worse: it read a tool that had stopped drawing rows as an account that had stopped delivering, published it as fact across four surfaces, and was corrected by the owner rather than by itself. The check that would have caught it costs one pull. Weight everything below accordingly. A third shape arrived the same week and it is the subtlest of the three. For three mornings this page ran what it called a controlled creative test and published a verdict from it. The two arms carried the same claim and the same belief, so the verdict was never available from the data. Nothing in the numbers was wrong; the label on top of them was. It took a cold outside reviewer to ask what the arms were testing, which is a question the content engine already exists to force and which this page never put to its own comparison. The older shape is still the common one: it reads a pattern into a series too short to carry one, then reverses itself. It invented an audience ceiling that was not there. It wanted to hold the budget on Sept 7 when the owner was right to raise it. It moved the re-render off the critical path on a single quiet frequency reading and put it back the next morning. It decided the new campaign's statics did not convert after two funded days, and one of them converted the next day. It downgraded the Page Likes forecast on a five day fall that reversed on the first day delivery resumed. Against that, it was right to insist on verifying the registrations, right to cut the two dead CMS cells, right repeatedly to hold the budget through the dearest days on the account, right to retire the weekday panel a day before its own date, right to refuse to scale the Agency Ceiling campaign on its early price, right to name the licensee campaign as the weaker of the pair, and right for five mornings that a fresh CMS hook was the lever worth pulling. That last entry has now gone through three stages and it is the most instructive thing in the table. On Sept 15 it was right about the action and wrong about the reason. On Sept 16 the reason got worse, because both creatives' click-through doubled on the same day, so the number it argued from was tracking the calendar. Today the seven state campaign has lost both complete days and its lifetime price has moved from 24 cents behind the Florida campaign to $1.85 behind it. The recommendation is now the only part of that argument still standing, and it is standing on the fact that a second campaign exists to compare against rather than on the creative inside it being better. A fourth stage was added on Sept 17: the asset that shipped was never a fresh hook at all. Its locked script carries the same claim and nearly the same payoff line as the ad it replaced, and it was never registered in the content engine, so the lever this table spent five mornings recommending was never actually pulled. A fourth shape arrived on Sept 18 and it is the one that should change how a reader weights everything above. The first three shapes are all errors of inference: a pattern read into too short a series, a tool mistaken for the world, a label put on a comparison it did not fit. This one is an error of measurement, and it is worse because the numbers are real and the arithmetic on them is correct. Twice in a week this page has read a window that begins after the thing it is describing has stopped, and then described the silence. It reported an ad as starved by Meta for four mornings when that ad had been the heaviest funded and cheapest in its set for the five days before the window opened, and had then been switched off. It reported a frequency series reversing when what changed was which entity the number was read from. In both cases the cure is the same and it costs one query: pull the series, not the point, and say which unit the series is in. Read this table as saying: weight its cut recommendations heavily, weight its refusals to act heavily, discount anything it infers from fewer than about five readings per unit, and treat its explanations far more sceptically than its recommendations, because the record now contains a case where the recommendation survived, the mechanism was falsified, the instrument behind the mechanism turned out to be measuring something else, and the thing recommended then lost on the merits.

Projected against actual

Each row is a call with a number and a date. It stays pending until the date arrives, then the actual is written beside the projection. This is the feedback loop: come back after the weekend, after one week, after two, and read what was expected against what happened.

Whether a paused account stays at zero, an instrument assertion on delivery against statusRight
ProjectedSept 23 closes at $0.00 on every unit on the account. If the activity log shows the owner restarting an ad set, spend begins no earlier than the logged restart hour and nothing else spends
Actual$0.00 on every campaign, ad set and ad, with no impressions and no charge. The activity log carries no event after the 9:02pm Sept 22 pause, so there was no restart hour to check against

GRADED RIGHT ON BOTH BITS. The number matched and the reason holds: status said nothing could deliver and nothing did. It is not banked as a forecast, because it forecast nothing; it is a check that the reading and the account agree, and on a day when they did it is worth one line and no more. From the closed list: delivery zero and spend by hour against committed. It exists because this account has read as one thing while doing another four times in two weeks, a disabled account, a paused ad reported as active, two ad set pauses under active campaigns, and now a whole account whose three campaigns all read ACTIVE while every ad set is off. Here status and delivery should agree, and this row checks that they do rather than assuming it. It needs no conversion to resolve, and it can only convict the reading, never excuse it. It is not a forecast of what the owner will do.

called Sep 23 · resolved Sep 24
Whether the budget overspend persists into a fourth day, an instrument assertion on spend against committedRight
ProjectedThe Florida campaign's Sept 21 closed day comes in at or under $48, which is 120 percent of the $40 committed. Above $48 is a fourth consecutive day over budget
Actual$38.67, which is 97 percent of the $40 committed and the first closed day inside budget in four. The twenty four hourly rows sum to exactly $38.67 with every hour present and the impressions to exactly 754, so the day is complete as read

GRADED RIGHT ON BOTH BITS. The number cleared at $38.67 against a $48 bar, and the reason holds: the row asked only whether the number repeats a fourth time, and it did not. Two things are worth saying so the win is not over-read. First, this row is the successor to the Sept 19 row that graded WRONG on the same instrument, and the pair together are more useful than either alone: they say the overspend is real and not every day. Second, the leading read published against it a day early, a same-hour projection of $40 to $44, landed ABOVE the actual because Sept 21's own close-to-hour-08 multiple was 2.68 against the 2.85 and 3.15 the comparison days ran. The projection was never graded and never should have been, per lens 6aa; it is recorded here as a calibration note on the multiple, which varies by about 18 percent across four days. What this row does NOT license is the conclusion that the overspend is over. The trailing seven days read 114 percent of the weekly budget, higher than the day before, and that is the number the successor row is written against.

called Sep 21 · resolved Sep 22
Whether the budget overspend resumes after one day inside budget, an instrument assertion on spend against committedRight
ProjectedThe Florida campaign's Sept 22 closed day comes in at or under $48, which is 120 percent of the $40 committed. Above $48 is a return to the overspend after a single day inside budget
Actual$29.60, 74 percent of the $40 committed. The day stopped at 9:02pm when the owner paused the ad set; the twenty two hourly rows sum to exactly $29.60. At the day's own dearest hour, $3.16, the three removed hours could have added at most $9.48, so the bar was out of reach with or without the pause

An instrument assertion from the closed list, spend against committed, needing no conversions to resolve. It is written at the same bar as the row above deliberately, so the two are comparable rather than a moving target, and it is the third time this account has asked this question. Its purpose is narrow and it is the owner's live decision: four closed days now read 157, 170, 130 and 97 percent, which is a spread around a rate rather than a settled regime OR a settled recovery, and the weekly figure is still 114 percent. Two consecutive days at or under the bar would be the first evidence that the daily budget means something; one more day above it says the spread is the regime and the spending limit is the only instrument left. It is not a causal claim, it does not ask why, and it is not the unit-consistency or delivery-form change that remains open with the owner and has not been adopted.

called Sep 22 · resolved Sep 23
Whether a $40 daily budget means $40, an instrument assertion on spend against committedWrong
ProjectedThe Florida campaign's Sept 19 closed day comes in at or under $48, which is 120 percent of the $40 committed to it on Sept 19. Above $48 and the Sept 18 overspend was not a one-off
Actual$68.07, which is 170 percent of the $40 committed and a higher multiple than Sept 18. Sept 20 then closed at $51.84, 130 percent, a third straight day over budget

Graded WRONG on both bits, and it is the most useful wrong call this scorecard has recorded, because it converts a suspicion into a settled fact. The number missed: $68.07 against a $48 bar. The reason it was written to test, that the Sept 18 overspend might be a one-off, is falsified: three consecutive closed days ran 157, 170 and 130 percent of budget. The competing benign reason was killed in the same pass rather than left as an escape hatch: the trailing seven days spent $302.98 against the $280 that seven days at $40 commits, so Meta is running 108 percent of the weekly budget, not recovering toward it. This is an instrument assertion from the closed list doing exactly its job, and it resolves the month planning question without needing a single conversion. The denominator was named in the row deliberately and it held, unlike the Sept 18 delivery assertion whose denominator moved four hours after it was written.

called Sep 19 · resolved Sep 20
The budget test, first full day at the raised budgetRight
ProjectedUnder $6 a registration means the raise was right; over $7 means the audience is the cap
Actual$3.88 on $38.79 spent

The one resolved projection so far, and it resolved cleanly. This is the loop working: a call with a number and a date, scored the day the date arrived.

called Sep 7 · resolved Sep 8
The weekday pattern holdsWrong
ProjectedThat Sunday and Monday come in above $7 while the days around them stay near $4
ActualSaturday Sept 12 came in at $9.24 and Friday Sept 11 at $9.53, so the days around the weekend are not near $4

Graded on its first date rather than its second, because half of it is already falsified and no Sunday reading can repair that half. The projection had two clauses: the weekend dear, and the days around it near $4. The second clause is gone. Sunday Sept 13 will almost certainly finish dear and it will prove nothing, because a wearing creative predicts exactly that. Both weekdays this panel has read twice moved from its cheap group to its dear group.

called Sep 9 · resolved Sep 13 to Sep 14
CMS registrations, first 7 days on the new budgetWrong
Projectedabout 48, range 35 to 57
Actual25 registrations across Sept 9 to Sept 15, on $213.00 of spend

Graded on its date and it misses the low end by ten. Two of its seven days produced nothing for entirely unrelated reasons, one billing and one creative, and a third produced six at $5.66, the cheapest complete day since the window opened. The failure is not a drift, it is two holes: Sept 13 with the account disabled and Sept 14 with the traffic arriving and not converting. A forecast built on a daily rate has no way to price the probability of a day disappearing, and this row is the clearest argument yet for the low end of every horizon on this page being set by day count rather than by price.

called Sep 9 · resolved Sep 16
Page Likes follows, first 7 days on the new budgetWrong
Projectedabout 370, range 349 to 388
Actual262 follows across Sept 9 to Sept 15, on $213.99 of spend

Misses the low end by 87. The reason is now well understood and it is two things, not one. One day was lost to the outage, which costs about 50 follows at the window's rate. The rest is price: this row was written when the campaign bought follows at $0.75 and it bought them at $0.82 across the window, with two of the last three days at $0.95 and $1.02. The delivery worry that hung over this row for two mornings was the wrong worry and is closed.

called Sep 9 · resolved Sep 16
The winning ad's frequency crosses 3.5Wrong
ProjectedFatigue threshold reached around Sept 17 at the current climb
Actual2.83 on Sept 16, needing 0.67 more in a single day against a largest ever step of 0.21

Graded a day early because it is arithmetically unreachable rather than merely unlikely, and grading it on Sept 17 would only be waiting for the calendar to agree with what the numbers already say. Written on Sept 9 when the series was stepping 0.13 to 0.21 a day, the projection assumed that pace continuing for eight days. It did not: the steps since are 0.07, 0.16, 0.08, 0.04, minus 0.08, 0.21 and 0.05. The lesson is not that the climb slowed, it is that this page fitted a line to a series whose own measurement noise is the size of the steps.

called Sep 9 · resolved Sep 17
CMS registrations, 14 daysWrong
Projectedabout 96, range 69 to 115, conditional on the re-render landing in week two
Actual52 registrations across Sept 9 to Sept 22 on $527.02, pulled for the Florida campaign over exactly that window. Under the low end by 17, and about half the central figure

GRADED WRONG ON THE NUMBER, AND THE REASON FAILED TOO. The window is read as the fourteen days Sept 9 to Sept 22 and this sentence is the label on that choice. The row assumed a price near the early run's, and the account then produced the dearest stretch in its life: an outage on Sept 13, a funded day with nothing on Sept 14, three overspend days that bought at $8.51 to $51.91, and a final day cut short by an owner pause. Only the last three hours of the window are destroyed evidence, and they could not have closed a gap of 17. Earlier note follows. The condition this row was written on, a re-render landing inside week two, has now been met: the Same Day hook shipped on Sept 14 as the seven state campaign. It does not save the number, because the re-render landed in a new campaign rather than in this one, and this row counts only the Florida campaign's registrations. Seven complete days have produced 22 against the 56 the central figure needs by now, and one of those seven only half delivered. It comes in under the low end.

called Sep 9 · resolved Sep 23
Page Likes follows, 14 daysWrong
Projectedabout 740, range 698 to 775
Actual324 follows across Sept 9 to Sept 22 on $288.42, pulled for the Page Likes campaign over exactly that window. Under half the low end

GRADED WRONG, and not rescued by the pause. The owner paused this ad set at midday on Sept 18, which removed five of the fourteen days, but on the nine days before it the campaign bought 305 follows, about 34 a day, where the central figure needed about 53 a day; had it run all fourteen at that pace it would have finished near 475, still far under 698. So the number failed on the days that existed, and the removed days are declared rather than used as cover. Earlier note follows. A row written on price, exposed first to a fall in volume that reversed, then to an outage, and now to a second delivery interruption that is not the campaign's fault at all. Sept 16 bought 10 follows on $10.06 because delivery across the whole account faded out during the day. Across the fourteen days this row covers, two have been lost to events outside the campaign, which is the same failure that took every Sept 9 horizon graded so far. It stays pending and unedited to Sept 23.

called Sep 9 · resolved Sep 23
Actual spend against committed, averaged over the first week at the new budgetsWrong
Projectedabout $88 a day against $76 committed
Actualon the two campaigns this row was written about: $60.89 a day across Sept 9 to Sept 15 against $76 committed. Account wide, including three campaigns that did not exist when it was written: $97.57 a day

Graded on the basis it was written on, which is the two campaigns that existed at the time against the $76 they committed, and on that basis it misses low by 31 percent. The account wide figure of $97.57 a day clears the projection comfortably and means nothing, because three of the five campaigns in it did not exist when this was written. Both numbers are printed so the choice of denominator is visible rather than convenient. The row is a good argument for stating the denominator inside the projection when it is written, which the Sept 14 restoration row now does.

called Sep 9 · resolved Sep 16
The winning ad's frequency on Sept 17, restatedMixed
Projectedabout 2.7 to 2.9, below the 3.5 threshold, because the climb is decelerating rather than linear
Actual2.91 on a reach of 2,564 on Sept 17, one hundredth above the top of its stated range and well below the threshold

The claim that mattered, that the threshold would not be reached, held with room to spare. The range missed by a hundredth, which is close enough that calling it right would be generous and calling it wrong would be pedantic, so it is graded mixed and the arithmetic is printed rather than argued. The reasoning underneath it gets no credit either way. The four steps between the call and its date are minus 0.08, an outage artefact, then plus 0.21, plus 0.05 and plus 0.08, and two of those days were not full delivery days. A decelerating climb was the stated mechanism and what actually happened is a series interrupted twice. Landing inside a range by way of an outage and a nine hour day is being carried to the answer rather than reasoning to it.

called Sep 10 · resolved Sep 17
The plan's click-through fatigue rule, on the winning adRight
Projectedlifetime link click-through falls below 3.08%, a 25 percent fall from its 4.11% week one, by Sept 12
Actual3.00% on Sept 11, a day before the date

It read 3.14% when this was written and 3.00% the next morning, a 27.0 percent fall from the 4.11% of its first week against a rule that trips at 25. The fatigue rule that tripped first is click-through, not frequency, which changes what the re-render is for: refreshing a tiring creative rather than escaping a spent audience. It also arrived on the morning the ad set lost its only other ad.

called Sep 10 · resolved Sep 12
CMS Social B, whether it is a second unit or dead weightRight
Projectedat least one registration by Sept 13, or it should be switched off
Actualswitched off by the owner on Sept 10, with no further registration

The substance was right and the date was the wrong instrument. It produced nothing on a third funded day and came off before Sept 13 arrived, which is the outcome this row projected, reached by the owner acting rather than by the deadline expiring.

called Sep 10 · resolved Sep 13
Whether Sept 10 was an outlier or a new levelWrong
ProjectedFriday Sept 11 finishes under $7 a registration
Actual$9.53 on $38.10, four registrations

Wrong on its own threshold and instructive in how it missed. It offered two branches, under $7 or a second double-digit day, and Friday landed between them. So Thursday was not a new level and Friday was not a return to the old one. Read with the two days before it the series is drifting upward rather than bouncing, which is the reading neither branch allowed for, and it is the reading the click-through data supports.

called Sep 11 · resolved Sep 12
The Agency Ceiling campaign converts at allRight
Projectedat least one registration by Sept 13 on a campaign spending $43 a day
Actual1 registration at $34.44 on Sept 11, two days early

Right, and the answer immediately raised a better question. It converts, which rules out a broken creative and a broken registration page. It converted at $34.44 on its first funded day, which is Legacy's price rather than the CMS campaign's, and one ad of the four bought it while the other three spent $21.64 between them and bought nothing.

called Sep 11 · resolved Sep 13
The winning ad's frequency, graded sooner than Sept 17Wrong
Projectedbetween 2.75 and 3.00 on Sept 14
Actual2.57 on a reach of 2,258, below the range, and the ad served 14 impressions in three days

Wrong, and worth more than the two Sept 17 rows above it precisely because it was close enough to its evidence to be graded at all. It missed low for a reason no version of this call could have anticipated: the account was disabled for non-payment on Sept 13, so frequency stopped climbing because the ad stopped serving. It then went down, which the series had never done. The fall is not even a fact about the audience. Impressions held at 5,793 while Meta revised its reach estimate from 2,185 to 2,258, and on this same morning two report windows covering identical delivery returned 2.65 and 2.57 for this ad. The measurement noise on this series is the size of a daily step, which retrospectively makes every crossing estimate this page has published unfalsifiable.

called Sep 11 · resolved Sep 14
CMS registrations, the seven days from Sept 11Wrong
Projectedabout 48, range 30 to 57
Actual25 registrations across Sept 11 to Sept 17, against a central figure of 48 and a low end of 30

Wrong on both bits. The number missed the low end of its own range by five, and the reason under it failed too: it was written on a trailing price of $5.76 that never returned, and two of its seven days bought nothing at all, one of those being the payment outage. The useful part is what it says about range setting on this account. A seven day horizon written from a five day trailing price has now missed three times, and every miss has been low, because the horizon cannot price in the days on which the account simply does not run. Horizons written from a price will keep failing until they are written from a price and a delivery assumption.

called Sep 11 · resolved Sep 18
Trend or weekday, the discriminating testRight
ProjectedSaturday Sept 12 finishes above $7 a registration, against the $4.47 the last Saturday bought
Actual$9.24 on $36.94, four registrations, against the $4.47 the last Saturday bought

The cleanest call this page has made, because the two stories predicted different things and only one of them could survive. Saturday came in at $9.24, two cents a registration off Friday's $9.53 and more than double its own previous reading on similar money. The weekday map is finished. What the call did not anticipate is how close the two days would land: a slide would be expected to keep sliding, and two readings at the same level look more like a step that has already happened.

called Sep 12 · resolved Sep 13
The Agency Ceiling campaign's registration price over its first four funded daysRight
Projectedabove $15 a registration, more than twice the CMS campaign's lifetime price
Actual$34.81 across four funded days, on $139.25 and a count still frozen at 4

It got its four funded days after all, and it came in right by a wider margin than when it was written. The third and fourth funded days, Sept 14 and Sept 15, spent $53.33 between them and bought nothing, so the price went from $21.48 to $34.81 rather than falling through the $15 line it was threatening. The call was made as a caution against scaling on an improving number, and the number stopped improving the moment it was tested on more days. Read alongside the licensee copy of the same campaign, which has spent $47.04 for nothing, the whole Agency Ceiling buy prices where Legacy priced.

called Sep 12 · resolved Sep 15
Whether the CMS price has stepped to a new level or is still climbing, Florida campaignWrong
ProjectedThe first two complete days of restored delivery both finish between $8 and $12, rather than above $15 or back under $6
ActualSept 15, the first day of the pair to produce a price at all, finished at $5.66, under the $6 floor the call itself named as a fail

Graded wrong and the thesis under it is dead, which is the more useful half. The call said the price had stepped to a new $8 to $12 level rather than continuing to slide, and named under $6 as a fail. Sept 15 came in at $5.66. A campaign whose three dearest days were its three most recent, which was the whole basis for reading a step, then produced its cheapest complete day in a week without anything changing in it. Neither the step reading nor the slide reading survives; what the nine priced days actually show is a spread, from $3.88 to $19.01, with no direction. The row was re-dated twice under the destroyed evidence rule and both moves were earlier rather than later. The scope is also stated explicitly, to the Florida campaign and the creative it was written about, because a second CMS campaign launched on Sept 14 at a different price and this test was never about it. Sept 14 is a genuine problem for the test rather than for the question: a day with no registration is outside the test's whole vocabulary, being neither inside the band nor above $15 nor under $6. It is not being counted as a pass. If Sept 15 and Sept 16 do not both land between $8 and $12, this row is graded wrong on Sept 17 and not re-dated again.

called Sep 13 · resolved Sep 16
Page Likes delivery, not priceRight
Projectedat least one of the first two complete days of restored delivery finishes above $30 of spend
Actual$37.65 on Sept 14, the first complete day of restored delivery, which is 105 percent of a $36 budget

Answered on the first of the two days rather than the second, and answered against the worry that produced it. The five day fall from 62 follows to 36 on halving spend was a dip, not a decline, and the forecast downgrade that travelled with this call is wrong. Two things are worth keeping. The first is that this row was re-dated on Sept 14 because its evidence had been destroyed, and it has now closed on terms that embarrass the argument it was attached to, which is the only real evidence that a re-dating was honest rather than convenient. The second is what the delivery watch found on its way past: on the same day the campaign finally spent its budget, the follows cost $1.02 each, over a dollar for the first time, because Brand Ad took $33.75 of $37.65 at $0.99 while the volume leader took nine impressions. Neither a price watch nor a delivery watch sees an allocation problem.

called Sep 13 · resolved Sep 15
Whether the Agency Ceiling static was a one-offWrong
ProjectedAC | Offer card buys at least one more registration before the campaign stops
ActualIt did not. The broad campaign closed on the same 4 registrations it held on Sept 12, and the offer card's lifetime spend never moved after that date

Graded wrong, and the honest reading is that it was never a fair test. This row asked whether a single registration on Sept 13 was a one-off, and the way to find out was to give the ad money. Meta gave it none: its broad copy's lifetime spend has not moved since Sept 12 while AC | Snippet 42s took another $89.11 and bought nothing with it. Its licensee copy did get funded, $6.79 on the campaign's last day and one link click on 66 impressions, and bought nothing. So the call closes wrong on an ad that was starved in one campaign and beaten in the other, and the useful residue is the second half of that sentence rather than the verdict.

called Sep 13 · resolved Sep 17
The winning ad's link click-through read on the day rather than on the lifetime averageWrong
Projectedstays between 1.7% and 2.2% rather than continuing to fall
Actual3.73%, 3.77% and 3.47% across Sept 15 to Sept 17, and 8.58% by 9am on Sept 18, all far outside the 1.7% to 2.2% band this row projected

Held open to its own date so it can take its pill, and it grades wrong tomorrow by a wide margin. Five readings between 1.83% and 2.15% looked like a creative that had worn to a level and settled there. It then read 3.73%, 3.77% and 3.47% on the three days since, on the same creative with nothing changed in the campaign, and the seven state ad moved with it. The instrument, not the conclusion, is what this row killed, and it is the single most useful wrong answer in this table: a band that holds for five readings and then doubles was never measuring the thing it was being read for.

called Sep 12 · resolved Sep 18
What the outage costs the Agency Ceiling campaign, the only campaign with a deadlineRight
ProjectedIt finishes its life on 4 registrations, having bought none after Sept 12
ActualIt finished on exactly 4 registrations at $43.47, with nothing bought after Sept 12

Right on the number and wrong on every word of the reason, which is the third time in three days this table has produced that combination. The row was written on the premise that the outage would take the campaign's remaining days. It got every one of them back: three complete funded days plus a partial, $73.58 spent after the call was made, and not one registration out of it. So the campaign did not finish on 4 because it ran out of days. It finished on 4 because it stopped converting on Sept 12 and the outage hid the first two days of that. A prediction that survives the destruction of its own premise is a coincidence, not a calibration, and it is recorded here as one.

called Sep 14 · resolved Sep 17
Whether restored delivery comes back at the rate it stopped atWrong
ProjectedThe first two complete days after restoration spend at least 80 percent of committed budget
Actual77 percent on Sept 14 and 87 percent on Sept 15, so the first two complete days did not both clear 80 percent. The larger question it grew into has answered itself in the opposite direction: delivery is now OVERSHOOTING, at 157, 170 and 130 percent of budget on Sept 18 to Sept 20

Graded WRONG on its letter, because the first of its two named days came in at 77 percent against an 80 percent floor. It is graded rather than left pending because its resolve date has now arrived and the question it grew into has resolved too, in a direction nobody expected. It was written to ask whether restored delivery would return to its prior rate or come back weak, and the worry all along was a shortfall. What actually happened is the reverse: after Sept 16's one soft 41 percent day, delivery did not just recover, it began overspending, three straight days at 157, 170 and 130 percent. So the underlying concern is closed, delivery is emphatically stable, and the new problem is the mirror image of the one this row was watching for. The denominator fixed on Sept 15, committed budget meaning campaigns live the whole day, held throughout.

called Sep 14 · resolved Sep 21
Whether the frequency series survives being read from one windowMixed
ProjectedTwo windows covering identical delivery return the same lifetime frequency for the winning ad to within 0.02
Actualnot re-testable, and a weaker version of the same defect observed instead: on Sept 16, within one window and a few minutes, this ad's reach read 2,476 and then 2,478 on unchanged delivery

Closed as mixed rather than re-dated, and the reason is worth stating because it is not the usual one. The test needs two report windows covering identical delivery, and identical delivery only exists when the account is not delivering. It has delivered every day since Sept 14, so the test cannot be run again and will not become runnable. The single measurement it ever got, on Sept 14, failed it by four times its tolerance: 2.65 on a reach of 2,185 against 2.57 on a reach of 2,258, same ad, same 5,793 impressions, same morning. That is one observation, which is why this is mixed rather than wrong. What replaced it is cheaper and points the same way: reach is a modelled figure and it drifted by 2 inside a single window while this morning pull was being taken.

called Sep 14 · resolved Sep 16
Whether the new Same Day hook holds its price once it has complete daysRight
ProjectedSept 15 and Sept 16 together finish under $10 a registration on the seven state campaign
Actual5 registrations on $44.20 across the two days, which is $8.84 each, under the $10 bar

Graded right, and it is the least useful right answer this table holds, because the bar it cleared was the wrong bar. The call asked whether the new hook holds under $10 and it does, at $8.84. What it did not ask is the only question that matters, which is how it compares with the ad it was built to replace, and on the same two days the Florida campaign bought 9 registrations at $6.35 against this campaign's 5 at $8.84. An absolute threshold looked rigorous when it was written and turned out to be a bar the loser of a paired comparison can clear comfortably. Sept 16 also came in at $11.71, which is under the $12 breaking reading by 29 cents on a day whose delivery faded out by late morning. Write the comparison into the call next time, not the level.

called Sep 15 · resolved Sep 17
Whether the Florida campaign's blank day was a gap or a stepRight
ProjectedSept 15 finishes with at least 2 registrations on the Florida CMS campaign
Actual6 registrations at $5.66 on $33.93, its cheapest complete day since Sept 8

Right, and by three times the bar rather than by a nose, which makes the blank Monday a gap and nothing more. Nothing upstream of the register page failed, which is why this is worth a dated call rather than a shrug: the traffic arrived and did not convert. Three registrations by 8:40am on Sept 15 make a gap much more likely than a step, so this call is close to its evidence and should be easy. It earns its place by being the sort of call that would look obvious in hindsight and would be quietly forgotten if it went the other way.

called Sep 15 · resolved Sep 16
Whether the Page Likes price staying over a dollar is a restart artefact or the new levelWrong
ProjectedSept 15 finishes under $0.90 a follow
Actual$0.95 on $36.10 and 38 follows, under a dollar but above the bar

Sept 14 read $1.02, the campaign's first complete day over a dollar in a lifetime price band of $0.60 to $0.92. Two readings are available for it and they point opposite ways. The restart reading is that a day on which delivery resumed is not a normal day. The allocation reading is that Brand Ad took 90 percent of the money at $0.99 while Service Fire took nine impressions, and that if Meta keeps the budget there the campaign simply buys follows at a dollar now. By 8:40am on Sept 15 it reads $0.98, which is inside neither answer and closer to the second.

called Sep 15 · resolved Sep 16
What the two Agency Ceiling campaigns finish onRight
ProjectedFewer than 7 registrations between them, at above $25 each
Actual5 registrations on $255.15 between the two campaigns, which is $51.03 each

Both campaigns are off and the numbers are final: 4 registrations at $43.47 on the broad campaign, 1 at $81.27 on the licensee one, $255.15 spent for 5. The call was written as a deliberately low bar so that clearing it would mean something, and it was not cleared by a distance: the price came in at twice the $25 floor and the count at five against a ceiling of seven. The last two days added $41.07 and one registration. For the record the cheapest registration in the whole buy was $6.58 at ad level, in the campaign with the worst campaign level price, which is the arithmetic of allocation rather than of creative.

called Sep 15 · resolved Sep 17
Whether the frequency series produces two usable increments in a rowWrong
ProjectedThe next two Maximum window increments both land between 0.10 and 0.30
Actualplus 0.21 then plus 0.05, so the second falls outside the range

Deliberately a call about the instrument rather than about the curve, because every curve this page has fitted to this series has been revised within days. Today's step is plus 0.21 and it is the first in three days whose inputs actually moved: impressions went from 5,793 to 6,551 rather than reach being revised underneath a static numerator. Two more steps in that range would mean the series is readable again and a crossing date can be argued. Anything outside it, in either direction, and the runway chart should be treated as decoration until the two window test on Sept 16 says otherwise.

called Sep 15 · resolved Sep 17
Florida against seven state, across three complete days eachRight
ProjectedThe Florida campaign finishes cheaper than the seven state campaign on at least two of the three days Sept 15, Sept 16 and Sept 17
ActualAll three complete days went to Florida: $5.66 against $8.12, $7.73 against $11.71, and $4.98 against $14.80

Two of the three days are in and both went to Florida, so the call is already decided and it resolves tomorrow on the third. The second day is the one worth reading carefully. Delivery across the account faded out during Sept 16, which wrecked every time series on this page, and the paired comparison came through it intact, because both arms were cut short on the same curve from the same budget. A shared shock is exactly what a paired design absorbs. What it also revealed is an allocation fact the design was not built to show: in the hours the account did run, Meta gave the Florida campaign $23.18 and the seven state one $11.71 from identical $40 budgets. The caveats still stand, four days old and inside a learning phase, but volume is no longer one of them. Corrected Sept 17: this row was written and read as a creative comparison and it is not one. Both arms carry the same CMS deadline claim and the same belief, so what it actually measures is geography, campaign age and allocation. The call itself is unaffected, because it only ever named two campaigns and a price.

called Sep 16 · resolved Sep 18
Whether the click-through jump belongs to the day or to the creativeWrong
ProjectedOn Sept 16 and Sept 17 the two CMS ads' day level link click-through stay within 1.0 point of each other rather than separating
ActualSept 16 finished at 3.77% and 3.03%, a gap of 0.74 points. Sept 17 closed at 2.79% and 1.63%, a gap of 1.16, which is outside the bar

Graded WRONG on the closed Sept 17 figures, and the wrong answer is the useful one. The gap ran 0.43, 0.74 and then 1.16 points, widening every time and finishing outside the 1.0 bar. So the click-through number carries BOTH a day term and an ad term, and this page spent five mornings reading the sum as if it were the second one. Two cautions on what that licenses. It is an AD level signal, not a hook one: both ads carry the same claim, so nothing here says anything about copy. And the whole level moved down on the closed day, 2.79% and 1.63% against the 3.47% and 2.48% read at 8:25am, which is another instance of an intraday reading on this account running high. The lesson recorded is the one about the instrument, not a new belief about creative.

called Sep 16 · resolved Sep 18
Whether the Page Likes engagement leader is actually cheap when it is fundedWrong
ProjectedOn any of the next three complete days where Service Fire takes more than $5, its cost per follow comes in above the campaign's cost per follow for that day
ActualCLOSED UNRUNNABLE, and the premise underneath it was false when it was written. The ad is PAUSED and has been since Sept 13

This row asked whether Service Fire is dear when it is funded, on the assumption that it was an active ad Meta was refusing to fund. It was not active. The ad stopped delivering after Sept 12 and reads PAUSED, so no amount of waiting could have produced a funded day and the row could never have resolved. Worse, the question was already answered in data this page had never pulled: read day by day, Page Likes | Service Fire | FL spent $90.57 between Sept 8 and Sept 12 and bought 109 follows at $0.83, against Brand Ad at $1.01 over the trailing week. It was the heaviest funded ad in the set and the cheapest. The $1.24 quoted against it for three mornings was its final $3.72 on the way down, and a single decaying day was allowed to stand in for five heavy ones because the page only ever read the current day and a window that began after the ad had stopped. Graded wrong rather than closed clean, because a call built on a false premise is a failure of the check that wrote it and not a scheduling accident.

called Sep 16 · resolved Sep 19
Whether the locked A/B actually runs as an A/BWrong
ProjectedSame Day B | Ready Client takes less than 15 percent of its ad set's spend across Sept 16 and Sept 17
Actual$5.80 of the ad set's $41.31 across the two days, which is 14.0 percent, under the 15 percent bar. But the two days split 3 percent and 18.4 percent

The number cleared its bar and the reason under it did not, so under the two bit rule this is recorded wrong rather than right, and it is the fifth time on this scorecard that a call has been correct for a mechanism that turned out not to be operating. The stated mechanism was that Meta concentrates on an incumbent with a head start and a conversion history, so the B arm would never accumulate a share. What actually happened is that B went from 3 percent on Sept 16 to 18.4 percent on Sept 17, above the bar on the only clean day inside the window, and the average only came in under 15 percent because Sept 16 was a near dead account day that crushed both arms. The window contained one real day and one artefact, and the artefact decided the verdict. Today, with A switched off, B has taken all $23.49 of the ad set by 9am, which says nothing about concentration either way and is recorded so that nobody reads it as the answer.

called Sep 16 · resolved Sep 18
Whether the Sept 16 delivery collapse was an event or a new levelRight
ProjectedSept 17 finishes above $95 of spend against the $116 now committed, which is above 80 percent
ActualClosed at $108.98, 94 percent of committed, delivered across the whole day rather than front-loaded into the morning

The most consequential unknown on the account and the one with the least evidence behind it. On Sept 16 the account spent $86.02 of $209 and delivery faded out during the day, normal to 9am and gone by 2pm, with every campaign reading Active, no failed charge and no payment error. There is no explanation available from inside Ads Manager, so this call does not offer one; it just names the number that tells the difference. Above 80 percent and Sept 16 was an event, the forecasts on this page are too low, and the right response is to have done nothing. Below 60 percent and this is a delivery regime rather than an incident. It cleared the bar by early evening with hours still to run, so Sept 16 was an event and doing nothing was correct. The Meta API connector went live the same day and supplied a cause the browser never could: Sept 15 took eleven Account billed events on $181.58 of spend, Sept 16 took two with a 21 hour gap after 7:32am, and Sept 17 took five. Delivery faded ninety minutes after that last Sept 16 charge. Billing velocity, not a spending limit and not an outage, and counting charges per day is now a standing check.

called Sep 17 · resolved Sep 18
The frequency crossing date's own volatility, tested against itselfWrong
ProjectedThe crossing date printed tomorrow differs from today's about Sept 26 by more than two days
ActualAbout Sept 26, the same date, once the series is read at the unit it is built from. This row was graded right on Sept 18 and is REGRADED WRONG on Sept 18 after the input it was graded on turned out to be a different measurement

This row was graded right in the small hours of Sept 18 on the strength of a withdrawn crossing date, and the withdrawal was an instrument fault. The point appended to the series that morning, 2.65 on a reach of 3,329, was the CAMPAIGN reading; every earlier point is the winning AD. Read at the series unit the ad went 2.91 to 2.97 and the crossing stayed at about Sept 26, which is a move of zero days against a bar of more than two. The row is therefore wrong on the number, and the reason recorded for the right grade, that the series had moved again harder than ever, describes something that did not happen. The regrade is the finding and it is left visible on purpose. A scorecard that grades itself from the same pull that produced the error will confirm the error, and this row is the proof: the call was aimed squarely at the instrument, it was the best designed row on the table, and it still came back confirming a fault instead of catching one, because the grader and the faulty input were the same morning's work. What does catch it is a quantity that cannot physically move as far as the data says it moved. A reach jump of 765 in a day, on an ad reaching about five hundred people a day into a saturated audience, is not a reading. It is a different ruler.

called Sep 17 · resolved Sep 18
Whether the seven state campaign closes the lifetime gap on FloridaPending
ProjectedOn Sept 20 the seven state campaign's lifetime cost per registration is still above the Florida campaign's
ActualCLOSED AS DESTROYED EVIDENCE, not graded. The owner paused the seven state ad set at midday on Sept 18 to conserve budget, so its lifetime price is frozen at $10.31 against Florida's $6.90 and Sept 20 will find it above, for a reason the row was not asking about

Written because the three day comparison resolves tomorrow on a sample of three days and that is not enough to move a budget on. It is also not enough to retire a creative, and after the Sept 17 correction it could not do that anyway: both arms carry the same claim, so nothing here licenses a conclusion about copy. This is the slower version of the same question and it is deliberately set against the outcome this page originally wanted. Three days ago the two campaigns were within 24 cents of each other and the seven state one was expected to pull ahead; it has now lost both complete days and the gap has widened sevenfold. What would falsify this row is the seven state campaign having two cheap days in a row, which is exactly what it was launched to do and has not yet done once. Its B arm taking a real share of the ad set, 20 percent this morning against 3 percent yesterday, was the most plausible route to it and it never got the days. CLOSED SEPT 18 AS DESTROYED EVIDENCE. Per lens 6g this distinction is the whole point and it is declared here rather than left for a reader to infer: on Sept 20 this row would read RIGHT, and it would be worthless, because the campaign stopped rather than the question resolving. Banking a correct-looking outcome that an owner budget decision handed to it is exactly the coincidence this table exists to refuse. The row stays pending and unresolved on the record; it is not graded right, and no conclusion about the seven state geography is drawn from its ending.

called Sep 17 · resolves Sep 20
Unit consistency of the frequency series, an instrument assertionRight
ProjectedTomorrow the winning ad reads above 2.97 on a reach above 2,681, both from the AD level Maximum window, and the two figures move by less than a day of that ad's own delivery
Actual3.09 on a reach of 2,894, pulled at ad level against an explicit ad id. Both bounds clear, and the reach step of 188 sits well inside a day in which the ad reached 724 people, so the movement bound holds too

This is not a forecast about the account and it is deliberately not one. It asserts that the instrument reads the same thing tomorrow that it read today. Frequency on a Maximum window cannot fall while an ad delivers, and reach cannot rise by more than the ad reaches in a day, so any breach is a measurement fault rather than a market event and there is no story available to explain it away. It exists because that exact fault shipped to this page yesterday and the scorecard row written to catch instrument drift graded it right instead. One thing about this row should be said plainly rather than left for a reader to notice. The closed list of instrument assertions this process is allowed to write covers whether the account ran, whether it spent, and whether the rows add up. Unit consistency is not on that list, and adding it here is a widening of the list by the same process that is supposed to be constrained by it. It is flagged to the owner in today's brief as a proposed extension rather than slipped in, and it is written so that it can only ever convict this page, never excuse it.

called Sep 18 · resolved Sep 19
Whether today's fast start holds, an instrument assertion on deliveryPending
ProjectedSept 18 closes at or above $98, which is 90 percent of the $108.98 Sept 17 actually spent, rather than against the $116 committed
ActualCLOSED AS DESTROYED EVIDENCE, declared, and deliberately NOT banked as a win although its number cleared. The day finished at $117.29, above the $98 bar, so on the letter it reads right. It is not scored, because it cleared for a reason opposite to everything it asserted and opposite to its own revised expectation of about $93: half the account was switched off at midday and the one campaign left ran 157 percent of its budget. This is the two-bit rule doing exactly the job it was written for, and the row earned its keep by making that number visible rather than by grading

Written at 9am relative to yesterday rather than to the budget, which is the lesson Sept 16 taught. It was killed at midday by an owner budget decision, and the way it died is a real limitation of the form rather than bad luck. An assertion pegged to yesterday's spend assumes the denominator is stable, and on this account the denominator is a human decision that can change at any hour: committed spend has moved $209 to $116 to $40 inside three days. The repair is not to go back to pegging against committed budget, which Sept 16 showed is worse. It is that a delivery assertion must carry the committed figure it was written against, so a later reader can tell a delivery fault from a budget change. That is a cheap fix and it is proposed to the owner rather than made unilaterally, because it is a change to the assertion form on the same day the assertion failed, and lens 6k exists for exactly that temptation. Closed, not graded.

called Sep 18 · resolves Sep 19

17 of 40 dated calls right 2 still open The calls that set two outcomes against each other come in. The calls that name an absolute threshold come in too, and today the table shows why that is not the same as being useful. The Same Day price call asked whether the new hook holds under $10 a registration, it does at $8.84, and it grades right while the campaign it was defending lost both complete days to a campaign buying at $6.35 over the same two days. A bar the loser clears comfortably is a bar in the wrong place, and the fix is to write the comparison into the call rather than the level. The pattern that keeps repeating is graded-right-for-the-wrong-reason, and it has now happened three days running. The Agency Ceiling outage call predicted the campaign would finish on four registrations because the outage would take its days; it got every day back, spent $73.58 across them, bought nothing, and finished on four. The frequency restatement landed one hundredth outside its range having been carried there by an outage and a half delivered day rather than by the decelerating climb it argued for. A prediction that survives the destruction of its own premise is a coincidence and is recorded as one. SEPT 22 IS THE COUNTER-EXAMPLE AND IT IS WORTH AS MUCH AS THE FAILURES. The instrument assertion written on Sept 21 named a number, a date and a bar, cleared the number at $38.67 against $48, and cleared its reason too, because the thing it asked about, a fourth consecutive day over budget, did not happen. It is the second half of a matched pair: the same instrument graded WRONG on Sept 19 and RIGHT on Sept 22, and the pair says something neither row says alone, that the overspend is real and is not every day. That is what the instrument assertions were adopted for, and it is the first time one of them has earned its keep in both directions. The re-dated rows are closed and the record on them is clean. Both were re-dated when the outage removed their evidence, both moved earlier rather than later, and both closed against the argument attached to them. The Service Fire row is closed, and how it closed matters more than that it did. It was carried for three mornings as a call waiting on somebody to fund an ad. The ad was paused the whole time, so the row could never have resolved, and the question it asked had already been answered in data this page had not pulled: that ad spent $90.57 across five days and bought follows at $0.83, cheaper than the ad Meta funds instead. It is graded wrong rather than closed clean, because a call whose premise is false is a failure of the check that wrote it. The hardest thing on this table is the row that had to be graded twice. A call written specifically to test whether this page's own frequency instrument means anything was graded right in the small hours of Sept 18 and regraded wrong the same morning, because the reading it was graded against turned out to be taken from a different entity than the rest of its series. That is the best designed row here and it still confirmed a fault instead of catching one, for a reason that generalises: the grader and the faulty input were the same morning's work. An instrument check that runs inside the instrument is not independent. What caught it was a physical impossibility in the number, a reach jump larger than the ad can reach in a day, and that kind of sanity bound is worth more here than another dated call. Today's two new rows are both instrument assertions rather than market forecasts, which is the only class this process is now allowed to open on its own, and both are written so that they can only convict this page rather than excuse it. SEPT 23 GRADED THE TWO OLDEST OPEN FORECASTS AND BOTH ARE WRONG. The fourteen day registration and follow forecasts written on Sept 9, the last market forecasts of the retired kind, closed at roughly half of what they projected. Both are graded on the days that existed, and the days the owner's pauses removed are declared on each row rather than used as cover, because neither gap could have been closed by them. They are the strongest argument on this table for the Sept 17 decision to stop writing that class of call. Sept 24 graded the paused-account assertion right and did not replace it. No new row was written, because a daily repeat of the same zero check adds a line without adding a test, and the morning check reads delivery against status every run whether or not a row asks it to. Sept 25 to Oct 2 had nothing due and wrote nothing, for the same reason.

Day by day

Every day since the registration campaigns went live, so the account reads as a trend rather than a single morning. Read the spend bar first on this page rather than last: on Sept 16 it is a third of the day before it, because delivery across the whole account faded out during that day, and every price on that row still reads normally. Each row carries its weekday, kept as a label rather than as an explanation: the weekday panel below was closed on Sept 13 and three of the four weekdays read twice have now contradicted their own first readings. The registration count is every registration the account bought that day, across all campaigns, not the CMS campaigns alone. The registration price column is deliberately blank from Sept 14, when a second CMS campaign launched at a different price, because one number across two campaigns buying the same event at different prices is not a price anyone can act on. The per-campaign prices are in the two charts below.

CMS 2027 Page Likes Legacy
  1. WEDSep 2
    $20.480 registrationsnone5 follows$1.17 each

    Launch day. The registration campaigns went live late and barely delivered.

  2. THUSep 3
    $121.584 registrations$21.05 each23 follows$1.63 each

    Full delivery across three campaigns, and only four registrations for it.

  3. FRISep 4
    $106.5310 registrations$6.00 each54 follows$0.86 each

    The turn. All ten on CMS at $4.06. Legacy paused mid day, Page Likes expanded to seven states.

  4. SATSep 5
    $37.526 registrations$4.47 each18 follows$0.60 each

    Both live campaigns underspent and still produced the cheapest finished day.

  5. SUNSep 6
    $91.285 registrations$8.97 each52 follows$0.89 each

    The heaviest day on the account. Both campaigns ran well past budget and the registration price doubled.

  6. MONSep 7
    $77.364 registrations$8.51 each62 follows$0.70 each

    The first finished day on the raised budgets. CMS stayed under its new $36 and still paid $8.51; Page Likes went over and bought its cheapest follows yet.

  7. TUESep 8
    $83.9610 registrations$3.88 each54 follows$0.84 each

    The best finished day on the account. Ten registrations at $3.88 on $38.79 of CMS spend, which settled the budget question in favour of the raise.

  8. WEDSep 9
    $85.109 registrations$4.65 each53 follows$0.82 each

    The first finished day at the raised budgets. CMS ran to $41.83 and still bought nine registrations at $4.65, so two of the three cheapest days on the account are now the two most recent.

  9. THUSep 10
    $76.992 registrations$19.01 each51 follows$0.76 each

    The break in the run. CMS spent close to its budget and bought two registrations at $19.01, more than four times the day before. Page Likes did not notice, and finished at $0.76.

  10. FRISep 11
    $107.924 registrations$9.53 each47 follows$0.75 each

    The first day all three campaigns delivered, $107.92 against $119 committed. CMS came in at $9.53, between Thursday's $19.01 and the $4 run before it, and the Agency Ceiling campaign bought its first registration at $34.44.

  11. SATSep 12
    $109.504 registrations$9.24 each36 follows$0.61 each

    The Agency Ceiling campaign outspent both established ones, $50.75 against a $43 budget, and bought three registrations at $16.92. CMS came in at $9.24, its second day near $9.40. Page Likes spent $21.81 of $36.

  12. SUNSep 13
    $1.540 registrationsnone0 followsnone

    The account was disabled for non-payment. Three card charges failed on this day, delivery stopped in the morning, and the finished total is $1.54 against $119 committed with no registration and no follow anywhere on the account.

  13. MONSep 14
    $120.372 registrationsnone37 follows$1.02 each

    The account came back and the shape of it changed. The balance was paid, delivery resumed, and two new campaigns launched: a seven state CMS campaign on a new hook and a second Agency Ceiling campaign on a licensee audience, taking committed spend from $119 to $209. Both registrations came from the new CMS campaign. The two established registration campaigns spent $53.88 between them and bought nothing.

  14. TUESep 15
    $181.5810 registrationsnone38 follows$0.95 each

    The best day the account has finished. $181.58 against $209 committed, 87 percent, with every campaign delivering and 10 registrations bought. Both CMS campaigns converted, the Florida one at $5.66 and the seven state one at $8.12, and the Florida campaign beat the seven state one on the first complete day they have both run. The two Agency Ceiling campaigns took $79.06 of the money and bought nothing for the third complete day running.

  15. WEDSep 16
    $86.025 registrationsnone10 follows$1.01 each

    Delivery decayed from about 9am and had stopped entirely by early afternoon. $86.02 against $209 committed, 41 percent, and $77.63 of that was already spent by 8:30am, so the whole of the rest of the day added $8.39 across five campaigns. Hour by hour in the ad account time zone, the three live campaigns ran normally to 9am, then in pennies, and their last delivering hours were 11am on the seven state campaign, 1pm in Florida and 2pm on Page Likes. The day before, the Florida campaign delivered until 11pm. Nothing in the account's own reporting says why, no charge failed and no campaign showed a payment error. Two of the five campaigns were the Agency Ceiling pair, which the owner switched off early. Every price on the day still reads normally, which is the part worth carrying forward.

  16. THUSep 17
    $108.9810 registrationsnone33 follows$1.20 each

    Closed at $108.98 against the $116 now committed, 94 percent, and it settles the question Sept 16 opened: that day was an event, not a new level. Ten registrations, eight of them to the Florida campaign at $4.98, its best complete day since Sept 8. The seven state campaign bought two at $14.80, and its A arm was switched off by the owner during the evening. Page Likes took $39.51 for 33 follows at $1.20, dearer than its band, with Brand Ad taking 70 percent of the money.

  17. FRISep 18
    $117.297 registrations$13.21 each19 follows$1.31 each

    The last row that mixes three campaigns, and the most misleading total in the series unless it is read with its denominator. $117.29 against the $116 committed at midnight, which reads as a normal 101 percent day; but two of the three ad sets were paused at 11:58am, so most of this was bought by one campaign running 157 percent of its own budget. Florida alone took $62.71 of a $40 budget across a full twenty four hours. From here the account commits $40 a day rather than $116.

  18. SATSep 19
    $68.078 registrations$8.51 each0 followsnone

    The first complete day of the one ad set account, and it closed at $68.07 against $40 committed, 170 percent. That is higher than Sept 18's 157 percent, so the overspend is not a one-off. Eight registrations at $8.51 on the money, which is the best output of the three overspending days.

  19. SUNSep 20
    $51.911 registration$51.91 each0 followsnone

    Third consecutive day over budget, $51.91 against $40, 130 percent. One registration on the money, which is the dearest priced day this account has recorded, and the count can still rise under seven day click attribution because the day closed only hours ago. Read the level beside the ratio: one registration prices nothing reliably.

  20. MONSep 21
    $38.822 registrations$19.41 each0 followsnone

    97 percent of the $40 committed, the first closed day inside budget after three at 157, 170 and 130 percent. Two registrations at $19.34. The twenty four hourly rows summed to exactly $38.67 and 754 impressions on the Sept 22 pull; Meta restated the day to $38.82 and 755 on the Sept 24 pull, ordinary backfill recorded rather than smoothed over.

  21. TUESep 22
    $29.650 registrationsnone0 followsnone

    74 percent of the $40 committed, and the day stopped at 9:02pm when the owner paused the last live ad set. No registration on the money, a funded day with no result, and the count can still rise under seven day click attribution. The twenty two hourly rows summed to exactly $29.60 on the Sept 23 pull; Meta restated it to $29.65 and 577 impressions on Sept 24.

  22. WEDSep 23
    $0.000 registrationsnone0 followsnone

    No delivery anywhere, the first full day with every ad set paused. The activity log attributes the pause to the owner at 9:02pm on Sept 22 and records no action since, so zero is the expected reading and not a failure.

  23. THUSep 24
    $0.000 registrationsnone0 followsnone

    The second full day with every ad set paused. No delivery, no charge, no owner action in the log, and no restatement of any earlier day.

  24. FRISep 25
    $0.000 registrationsnone0 followsnone

    The third full day with every ad set paused. No delivery, no charge, no owner action in the log, and no restatement of any earlier day.

  25. SATSep 26
    $0.000 registrationsnone0 followsnone

    The fourth full day with every ad set paused. No delivery, no charge, no owner action in the log, and no restatement of any earlier day.

  26. SUNSep 27
    $0.000 registrationsnone0 followsnone

    The fifth full day with every ad set paused. No delivery, no charge, no owner action in the log, and no restatement of any earlier day.

  27. MONSep 28
    $0.000 registrationsnone0 followsnone

    The sixth full day with every ad set paused. No delivery, no charge, no owner action in the log, and no restatement of any earlier day.

  28. TUESep 29
    $0.000 registrationsnone0 followsnone

    The seventh full day with every ad set paused. No delivery, no charge, no owner action in the log, and no restatement of any earlier day.

  29. WEDSep 30
    $0.000 registrationsnone0 followsnone

    The eighth full day with every ad set paused. No delivery, no owner action in the log, and no restatement of any earlier day. A Meta generated custom audience was created at 6:16pm; it is not delivery.

  30. THUOct 1
    $0.000 registrationsnone0 followsnone

    The ninth full day with every ad set paused. No delivery, no owner action in the log, no new charge, and no restatement of any earlier day.

  31. FRIOct 2
    $0.000 registrationsnone0 followsnone

    The tenth full day with every ad set paused. No delivery, no owner action in the log, no new charge, and no restatement of any earlier day.

  32. SATOct 3
    $0.000 registrationsnone0 followsnone

    The eleventh full day with every ad set paused. No delivery, no owner action in the log, no new charge, and no restatement of any earlier day.

  33. SUNOct 4
    $0.000 registrationsnone0 followsnone

    The twelfth full day with every ad set paused. No delivery, no owner action in the log, no new charge, and no restatement of any earlier day.

  34. MONOct 5
    $0.000 registrationsnone0 followsnone

    The thirteenth full day with every ad set paused. No delivery, no owner action in the log, no new charge, and no restatement of any earlier day.

  35. TUEOct 6
    $0.000 registrationsnone0 followsnone

    The fourteenth full day with every ad set paused. No delivery, no owner action in the log, no new charge, and no restatement of any earlier day that this check could see.

  36. WEDOct 7
    $0.000 registrationsnone0 followsnone

    The fifteenth full day with every ad set paused. No delivery, no owner action in the log, no new charge, and no restatement of any earlier day that this check could see.

  37. THUOct 8
    $0.000 registrationsnone0 followsnone

    The sixteenth full day with every ad set paused. No delivery, no owner action in the log, no new charge, and no restatement of any earlier day that this check could see. The log's only lines are ten custom audiences Meta itself created at 10:55am.

  38. FRIOct 9
    $0.000 registrationsnone0 followsnone

    The seventeenth full day with every ad set paused. No delivery, no owner action in the log, no new charge, no new log line of any kind, and no restatement of any earlier day that this check could see.

  39. SATOct 10
    $0.000 registrationsnone0 followsnone

    The eighteenth full day with every ad set paused. No delivery, no owner action in the log, no new charge, no new log line of any kind, and no restatement of any earlier day that this check could see.

  40. SUNOct 11
    $0.000 registrationsnone0 followsnone

    The nineteenth full day with every ad set paused. No delivery, no owner action in the log, no new charge, no new log line of any kind, and no restatement of any earlier day that this check could see.

  41. MONOct 12so far
    $0.000 registrationsnone0 followsnone

    Open day, read at the morning run. Zero because every ad set is still paused and the activity log shows no restart and no new charge.

The board

Campaigns are collapsed to their headline. Open one to see its creative, and click any ad for the full detail.

Yesterday $29.74 for two registrations at $14.87 before the ad set was paused at midday. Its last dayToday so far No delivery. $0.00

Yesterday $0.00 and no delivery. Oct 11 was the nineteenth full day with its ad set pausedToday so far No delivery. $0.00

Yesterday $24.84 for 19 follows at $1.31 before the ad set was paused at midday. Its last dayToday so far No delivery. $0.00

Yesterday No delivery. $0.00Today so far No delivery. $0.00

Yesterday No deliveryToday so far No delivery

By status

The same ads again, grouped by where each one stands in Meta right now. 0 live, 0 in rotation, 0 pending, 11 upcoming, 30 paused.

By category

Legacy / your book9

No delivery Oct 11
No delivery yet today

Page Likes / follows16

No delivery Oct 11
No delivery yet today

Hybrid / sell anywhere3

No delivery Oct 11
No delivery yet today

Agency builder7

No delivery Oct 11
No delivery yet today

CMS 2027 rule6

No delivery Oct 11
No delivery yet today

Content engine

Brief queue

Corpus review

What we found out

A daily budget is a rate, not a ceiling, and a month planned on it is planned on an assumption nobody stated.

On Sept 18 the Florida campaign spent $62.71 on a $40 daily budget, 157 percent, across a full twenty four hours. Meta documents roughly 25 percent of daily flexibility against a weekly average; this was more than twice that. The month plan on this page, twelve days at $40 for $480 against about $500, had been quietly treating the budget as a cap, and the sentence doing the reassuring even said so: Meta can run about a quarter over. It ran 57 percent over the next day. Three checks separate this from the instrument faults that have cost this page so much. The twenty four hourly rows sum to exactly $62.71 with every hour present, which rules out a truncated render. Impressions and reach rose with the money, 956 and 724 against a series near 650 and 520, which rules out a unit switch. The activity log carries no budget change, which rules out a human. And it was not this campaign's property, which is the part that matters. Through 11:59am all three campaigns were pacing between 140 and 157 percent of their own budgets. Three independent units moving together is a property of the day, and that is the same check that killed the wear hypothesis, applied before reaching for a story rather than after. The planning consequence is the whole finding: a floor is not an estimate. CONFIRMED SEPT 20: this was not a one-off. The next two closed days ran 170 and 130 percent, the Sept 19 instrument assertion that would have cleared it at 120 percent graded wrong, and the catch-up hypothesis died when the trailing seven days came in at 108 percent of the weekly budget rather than recovering toward it. SHARPENED SEPT 22, and the sharpening is the useful part rather than a retreat. Sept 21 closed at $38.67, 97 percent, and the instrument assertion written against it graded RIGHT on both bits. Four closed days now read 157, 170, 130 and 97 percent. So the title is exactly right and the tempting stronger version is wrong: the budget is not a ceiling, and it is also not a reliable multiple of one. It is a rate with a spread, and a spread is harder to plan against than a consistent overshoot because no single number describes it. The trailing seven days still read $318.35 against $280, 114 percent of the WEEKLY budget and higher than the day before, which is the number that keeps this card live. The only instrument that caps a total whatever the daily rate does is an account level spending limit; throttling the daily number scales the floor while leaving the multiple alone, so it is still not an equal option. OVERTAKEN SEPT 22, and the lesson stands. The owner paused the last live ad set at 9:02pm, which caps the month more firmly than any limit, for as long as it lasts. The card stays because the property it describes belongs to the budget rather than to the week, and it returns with any restart.

A revival counted from creation dates is not a revival, because a page that refreshes a live concept looks identical.

On Sept 23 this page reported that a tier-1 competitor page had revived four concepts after 15 to 64 days idle, and treated it as the strongest signal the archive can give. On Sept 24 the claim was checked against ad ids and it was wrong. All four concepts had been live in every pull from Sept 19 to Sept 22, including two complete ones, with the same ids each day. What had been idle was the page's ad creation, not the concept: the diff measured the gap since the concept's last ad was made, and a page that replaces old copies of a running concept with fresh ones produces exactly that gap. The fix is the definition rather than a new threshold. A revival now needs the concept to have been absent from a previous pull that could prove absence, meaning complete and not empty; a concept that was live the day before is a refresh and is reported as one. The same morning a second page refreshed a concept on a complete pull and the new rule named it correctly. This is the fourth archive fault in a week and it has the same shape as the other three: the numbers were right and the word laid on top of them was not. Every one was caught by asking the platform's ids rather than the diff's summary.

A zero is a reading, not a fact, and it is the one result whose completeness cannot be checked.

On Sept 21 the Ad Library archive reported its first real disappearance: a tier-1 competitor page went from seven active ads to zero. It was written up carefully. It was checked against the one guard that existed, truncation, and it passed, because the pull reported an estimated total of 0 and returned 0, which is what a complete and empty page looks like. A cell in the signal bank was flagged to retire on the next pull. On Sept 22 the same page returned the IDENTICAL seven ad ids, every one created Sept 8. Seven ads pausing together for exactly one day and restarting together is not what happened. The index returned an empty result. THE SHAPE OF THE FAULT IS THE LESSON AND IT GENERALISES WELL BEYOND THIS TOOL. This archive already guarded both directions of a truncated window: an ad cannot be reported as gone from a page whose pull hit the 50 cap, and since Sept 21 it cannot be reported as new on one either. A zero slipped through both, because zero looks like the most complete answer a query can give. Every other suspicious result announces its own incompleteness; this one announces the opposite. The guard added today treats a zero page as NO COVERAGE rather than as complete and empty, which blocks the disappearance it appears to create and the reappearance that follows it. On the re-run it suppressed all seven false new ads. The wider version, worth carrying to every instrument on this account: when a query returns nothing, the next question is whether the thing stopped or the query did, and the cheapest way to tell them apart is to ask again on a different day and compare ids. This is the same family as the Sept 17 failure that read a grid which had stopped drawing rows as an account that had stopped delivering. Absence of rendered data is not absence of data, and absence of returned data is not absence either.

The archive can manufacture a competitor signal out of its own transcription, and the guard is ad ids rather than titles.

The Ad Library diff reported NEW CONCEPTS on a tier-1 competitor page this morning, which is one of the three things that opens a cell in the signal bank. Checked against ad ids, two of the flagged ads were the same two ad ids as yesterday. Yesterday's snapshot had recorded their title without the emoji it ends with and today's recorded it with, so the diff, which matches concepts on title strings across files written by different runs, saw a page full of new concepts. Nothing the competitor did. This is not an inference error and it is not a truncation error, which are the two classes this project had guards for. It is an error in the instrument's own record keeping, and it has a specific shape worth naming: a longitudinal archive built by successive runs is only as consistent as the transcription those runs happen to perform, so any field a run normalises differently becomes a false signal in every comparison that uses it. The cheap guard is that a concept level claim gets checked against ad ids before it is reported, because ids are assigned by the platform and cannot drift between runs. What is genuinely new on that page is one ad id, a third copy of a concept it already ran twice, which is mild scaling rather than a new angle. Changing how the diff matches concepts is a separate question and is raised with the owner rather than done on the morning it would make this report tidier.

The archive invents an appearance the same way it invents a disappearance, and the guard is the same guard mirrored.

The diff already refused to report DISAPPEARANCES on a page whose pull hit the 50 result cap, because an ad dropping out of the newest fifty proves nothing. It had no such guard for APPEARANCES, and this run it cost a false signal: six ads read as new on a truncated competitor page, and checked against ad ids four of them were created days before the previous pull. A refreshed delivery start had simply pushed old ads back up into the newest fifty, where a two day gap between runs made them look brand new. The mirror is exact. Absence of evidence in a moving window and presence in a moving window are the same failure wearing opposite signs, and a tool that guards one and not the other is only half built. The guard added this run is symmetric: on a page truncated in the previous pull, an ad counts as new only if it was created after that pull ran. It suppressed the six and left the one genuinely new concept standing. The general lesson is that a longitudinal archive has to be as suspicious of what enters a capped window as of what leaves it, because the window moves under both.

An instrument that stops rendering looks exactly like a world that stopped happening.

This is the worst reasoning error this page has made and the owner caught it within hours. Ads Manager's hourly breakdown renders about nine rows and will not scroll to the rest until you drag the grid's own vertical scrollbar; the mouse wheel does nothing and the document reports no overflow at all. The morning check read the nine rows it was given, saw that they ran midnight to 9am, and wrote up an account that stopped delivering at 9am. The rows after 9am existed the whole time, and the real picture is a slow fade: normal to 9am, pennies through the late morning, nothing after about 1pm. Two things made it stick rather than getting caught. The nine rows summed to 95 percent of the day's spend, which looked like corroboration and was only a consequence of a day that really was front loaded. And the check never ran the same query against a day it already understood: Sept 15 shows the identical nine rows ending at the identical hour, which would have exposed the cap in a single pull. The rule generalises past this account. ABSENCE OF RENDERED DATA IS NOT ABSENCE OF DATA. Before reading a gap as a fact, run the same query against a case whose answer you already know. A tool that truncates identically on every input is worthless for an absolute claim and still perfectly good for comparing two inputs, which is how the corrected finding was eventually built.

A threshold set from one failure gets calibrated to that failure's severity.

The assertion written on Sept 14 fails this page when a closed day spends under a fifth of what was committed and the page does not say why. Sept 16 came in at 41 percent and it stayed silent, on the worst delivery day since the outage, while every ratio read normally: $7.73 a registration in Florida, $11.71 on the seven state hook, $1.01 a follow. The Sept 14 failure was total, so the Sept 14 instrument was built for total, and partial failures are both more common and invisible in ratios. The fix was a second and independent assertion, relative rather than absolute: a closed day whose spend halves against the previous complete day must be named on the page. It fired on its first run. The original threshold was deliberately left alone rather than widened on the morning widening it would have looked clever, and raising it is an owner call.

A paired test survives a shock that a time series cannot.

Sept 16 destroyed the usefulness of almost everything on this page. The trailing seven day forecast window now holds one dead day and one half delivered day, the weekday panel gained a Wednesday bought on $23.18, and the frequency step was earned on partial impressions. One section came through it intact. The two CMS campaigns run the same objective, the same conversion event and the same $40 budget, so when delivery faded they were cut short on the same curve, and the comparison between them is unaffected by the thing that ruined every measurement taken over time. This is the argument for paired designs stated in the only way that ever convinces anyone, which is after the shock rather than before it. It also turned up something the design was not built for: on identical budgets and in the same fading day, Meta gave the Florida campaign $23.18 and the seven state one $11.71, which is an allocation reading that no single campaign's own history could have produced.

Repeating an ask is not escalating it, and a standing item that never changes shape stops being read.

The registration verification was raised on six consecutive mornings in almost identical words, each time with a larger unverified share attached: 29, then 35, then 46 percent of output. It closed in one sentence the moment it was raised in conversation instead. The point is not that anyone was slow. It is that this page had one escalation mechanism, saying the same thing again with a bigger number, and that mechanism does not work, because an item that appears every morning in the same position reads as furniture. What would have worked is what now replaces it: a threshold that says when the item becomes urgent, so its appearance carries information rather than persistence. Applied generally: if this page has raised something three times without the situation changing, the problem is the format of the ask, not the frequency of it.

A number that moves in lockstep across independent units is measuring the day, not the unit.

This is the sharpest correction this page has had to make and it retires an instrument rather than a conclusion. For five mornings the case for a fresh CMS creative rested on one reading: the winning ad's day level link click-through had settled into a band of 1.83% to 2.15%, roughly half its first week, so the creative was worn. On Sept 15 that ad read 3.73% and on Sept 16 3.87%. The new creative, a different ad in a different campaign targeting seven different states, moved with it: 2.15%, then 3.30%, then 3.13%. Two independent units doubling on the same day and holding on the next is not two creatives recovering. It is the day. Which means the band was never a wear curve, and five mornings of argument were built on a quantity that varies with something nobody on this page was tracking. The general rule is cheap and should have been applied a week ago: before attributing a movement to a unit, check whether the other units moved the same way at the same time. A control was available the whole time in the Page Likes campaign and in the Agency Ceiling one; nobody looked.

The recommendation survived, the mechanism was falsified, and the instrument turned out to be measuring something else.

Three stages, three mornings, one call. On Sept 14 the owner shipped the fresh CMS hook this page had asked for on five consecutive mornings, and it bought registrations, so the recommendation graded right. On Sept 15 the reason graded wrong: the new creative's click-through matched the Florida ad's almost exactly, so the new creative had fixed conversion rather than clicks. On Sept 16 the instrument itself failed: both creatives' click-through roughly doubled together, so the number the argument was made from tracks the calendar. The seven state campaign then lost the first complete day the two ran side by side, $8.12 against $5.66. On Sept 17 a fourth stage arrived and it is worse than the other three: the asset that shipped was never a fresh hook. Its locked script carries the same claim and nearly the same payoff line as the ad it replaced. The lever this page asked for five times was never pulled. A scorecard with one verdict per row shows none of this. The practical rule: a right call is not evidence that the reasoning behind it works, and a process that keeps being right for wrong reasons will eventually make the same wrong argument in a case where the luck runs out.

A window that opens after the thing stopped will show you silence and call it a finding.

This page spent a week on one ad in the Page Likes set and got it wrong twice in opposite directions. First it said Meta was starving Service Fire. Then, when a single funded day came in at $1.24, it said the starvation claim was dead and the ad was dear. Then it said the question could not be tested at all because the ad never got money, and it repeated that for four mornings while describing the ad as active. The ad is paused, and pulling its day by day series, which takes one query and was never run, settles everything the page argued about. It spent $16.17, $18.39, $23.96, $23.13 and $8.92 across Sept 8 to Sept 12, buying 109 follows at $0.83, and $220.48 over its life for 268 at $0.82. That is the largest spend of any ad in the set. It was not starved, it was not dear, and the $1.24 was its last $3.72 on the way down. The mechanism is worth naming because it is not an inference error, it is a query error, and inference errors are the only kind this page had been looking for. Every reading was taken from the current day or a trailing window, and both of those begin after the ad stopped. A quantity that is zero for the whole of your window looks like a quantity that has never been anything else. Before describing an absence, pull the series and find the edge of it.

The comparison this page called controlled was never a creative test, and it took three days and an outside reviewer to notice.

From Sept 15 this page described a controlled test: two campaigns, same objective, same conversion event, same $40 budget, different creative in different geographies. Three mornings were written on that basis and the verdict published each time was that worn creative was beating a fresh hook. On Sept 17 a cold reviewer asked the one question the page had never asked its own comparison: do the two arms cite the same belief? They do. The Florida ad maps to a registered content engine hub with a declared belief target. The seven state ad is not in the ledger at all, and its locked script states in its own purpose line that it replaces the earlier copy and carries the same payoff, the same regulatory fact, in nearly the same words. What actually differs between the arms is geography, campaign age, learning phase, a two arm budget split on one side only, and production format. Every one of those is confounded with the creative. What survives is real and worth having: from identical budgets Meta gave Florida roughly twice the delivery, kept it running hours longer, and it bought registrations more cheaply on all three days. That is a finding about geography, maturity and allocation, and it is enough to move a budget on. It is not a finding about hooks and it never was. The check that would have caught this on day one is the check the content engine already exists to enforce: what belief does this asset claim to test? The seven state asset could not answer, because nobody made it register.

An asset that skips the engine cannot be compared on anything the engine measures.

The seven state creative was built, gated, rendered and shipped without ever entering the content engine's ledger. No hub, no belief key, no hypothesis, no gate record. Nothing about it was careless in production terms, and the ad itself is fine. The cost landed somewhere else entirely: three days of published verdicts rested on a comparison that could not be checked, because one side of it had never declared what it was testing. Registration is not paperwork here. It is the thing that makes two ads comparable at all. The rule this produces is narrow and cheap: an asset that will be compared against a registered asset must itself be registered before it runs, and if it is not, the comparison is reported as a campaign result and never as a creative one.

A funded day that buys nothing is a different failure from a day that does not run.

Sept 13 and Sept 14 both produced no CMS registration and they have almost nothing else in common. On Sept 13 the ad account was disabled and the campaign served 14 impressions. On Sept 14 it spent $23.38, served 477 impressions, earned 10 link clicks at 2.10%, which is the top of its recent band, and sent 5 people to the landing page, and still bought nothing. The first is an absence of delivery. The second is a conversion failure with the whole funnel above it behaving normally, and it is the first one this campaign has ever had. Both appear on this page as a day with a null price, which is why the note on each row has to carry what actually happened rather than letting the null speak.

The level came back and the ratio broke, which is yesterday's lesson upside down.

On Sept 13 this page recorded that a cost per result is a quotient and a quotient can hold while both of its terms collapse: Page Likes held its price for ten days while its volume fell 42 percent and its spend halved. Sept 14 ran the same trick in reverse. The campaign spent 105 percent of its budget, its heaviest day in a week, which answers the delivery question in the direction of a dip, and the follows cost $1.02 each, over a dollar for the first time in the campaign's life. The cause is visible only at ad level: Brand Ad took $33.75 of $37.65 and bought 34 of the 37 follows at $0.99, while Service Fire, which has the highest all clicks rate in the set at 14.71%, got nine impressions. A price watch would have missed the shrinking campaign. A delivery watch would have missed the dearer follows. Neither sees which creative the budget is sitting on, and that is the thing that moved.

Retired: two campaigns buying the same event was never a creative test, and now there is only one campaign left.

Until Sept 14 the CMS campaign ran one ad, so every argument about whether its price was the creative or the audience or the calendar had to be settled by looking at the same ad over time, which is how this page talked itself into an audience ceiling and then a weekday effect and then a wear curve. There are now two CMS campaigns with the same objective, the same daily budget and the same conversion event, running different creative in different geographies. That is two variables rather than one, so it is not a controlled test, but it was the closest thing to a control the account ever had. Two corrections have overtaken this card and both are kept on it. The first, on Sept 17: the two arms carry the same claim and the same belief, and the seven state asset was never registered in the content engine, so the comparison was never a creative test and the word does not belong in the title. The second, on Sept 18: the owner paused the seven state ad set, so there is now one campaign again. What that costs is worth stating plainly, because it is easy to file the pause as purely a budget decision. The second campaign was the only other unit on the account buying the same conversion event, which made it the control that could tell a bad day apart from a bad creative. Without it, the lockstep check that killed the wear hypothesis has nothing left to check against, and every reading on the Florida campaign is uncontrolled again. Sept 18 is the first day that bit: its link click-through fell while its spend rose 57 percent, and there is no longer any way to tell whether that is the extra volume or just the day.

An outage can hide a campaign failing on its own.

For two mornings this page called the Agency Ceiling campaign the expensive part of the outage, on the grounds that it was the only campaign with a deadline and it was improving fastest, from $34.44 after one funded day to $21.48 after two. It got its days back on Sept 14. It has had three complete funded days since, spent $89.11, and bought nothing on any of them, which takes its lifetime price to $43.14 on a count still frozen at 4. The campaign was not robbed of registrations by a billing system; it stopped converting on Sept 12 and the outage covered the first two days of it. A loss attributed to a known interruption is the easiest loss in the world to stop investigating. The coda is worth keeping too: its licensee sibling, written off here yesterday, bought a registration at $5.53 on its final morning, which is the cheapest the Agency Ceiling buy has ever produced.

A dashboard of efficiency measures is silent about existence, and on Sept 16 it proved it.

Written on Sept 14, when this page would have reconciled against itself perfectly and printed a pass thirty hours after the ad account was disabled, because every metric on it is a ratio and a quotient whose inputs go to zero reports the last thing it knew rather than zero. It stopped being a hypothetical on Sept 16. The account delivered for nine hours out of twenty four and every price on this page read normally, and the assertion written for this exact failure stayed silent because it fires under a fifth of committed spend and the day landed at 41 percent. The lesson has therefore been paid for twice and is worth stating once more in its sharpest form: the question of whether the account ran is not a harder version of the question of how well it ran, it is a different question, and it needs its own assertion, its own threshold and its own row on the page rather than an inference from the ratios.

Destroyed evidence is not contrary evidence, and today is the first test of whether this page means it.

On Sept 14 two dated calls were re-dated rather than graded, because the outage removed their evidence instead of contradicting it, and the note beside them said plainly that the move is indistinguishable from dodging an inconvenient result. One of the two closed today on the first day of restored delivery, and it closed against the argument attached to it: Page Likes spent 105 percent of its budget, so the five day decline was a dip and the forecast downgrade that travelled with the call is graded wrong. The other has been moved again, from Sept 19 to Sept 16, and that move is earlier. A re-dating that shortens the wait and a re-dating that extends it are not the same act. Keep reading this page on whether the dates it moves ever drift outward.

A ratio can hold while the thing underneath it falls away.

For a week this page called Page Likes the steadiest campaign on the account, and the evidence was always the same: cost per follow inside $0.60 to $0.92 on every finished day since the Sept 3 prune. What nobody was reading is the level. Follows fell on five consecutive days, 62, 54, 53, 51, 47 and then 36, and the money that bought them went from $43.33 to $21.81 against an unchanged $36 budget. The campaign was buying less of everything at the same price, which a cost-per-result metric is constitutionally unable to show. Two days later the same blindness cost more: the account stopped spending altogether and every ratio on this page carried on reading normally. The rule from Sept 12 was to read a ratio on the day rather than on the total. The rule from Sept 13 was to read the level beside the ratio, every time. The rule from Sept 14 is that the level can be zero for reasons that have nothing to do with the market, and a page of quotients will be the last thing to tell you.

One observation per bucket is an instrument that cannot fail, and it failed twice in two days.

The weekday panel carried seven rows, one reading each, and read as a finding for three mornings. Friday came round again on Sept 11 at $9.53 against $4.06. Saturday came round on Sept 12 at $9.24 against $4.47. Both weekdays sat in the cheap group on their first reading and both landed in the dear group on their second, on similar money each time. Two repeats are worth more than the other five rows together. The same instrument produced the claim on Sept 12 that the new campaign's statics do not convert, made on two funded days with one observation per creative, and the static converted the next morning. When a cut has one observation per bucket, say what reading would break it and date the day that reading arrives.

Sorted by date, the series says something the weekday cut hides.

The nine complete CMS readings, in order: $4.06, $4.47, $8.97, $8.51, $3.88, $4.65, $19.01, $9.53, $9.24. The three dearest are the three most recent, and they sit either side of the morning the ad set lost its second creative. Cut by weekday, the same data produced a story about Sundays that both of its repeat readings then contradicted. Cut by date it produces a story about wear that also explains the click-through fall, the Thursday outlier and both disagreements. Prefer the cut that has to explain more.

Retired: the step that had already happened. It was a spread, and both instruments behind it have since failed.

The reading was that Friday's $9.53 and Saturday's $9.24, two cents apart on similar money, showed a creative that had worn to a new level and stopped, confirmed by a daily click-through flat near 2% for four days. A dated call was written on it and graded wrong on Sept 16: Sept 15 came in at $5.66, under the $6 floor the call itself named as a fail, with nothing changed in the campaign. Both instruments have now failed. The price series runs $3.88, $4.65, $19.01, $9.53, $9.24, no price, $5.66, which is a spread and not a level. The click-through band doubled across two creatives at once, so it was reading the day. What survives is only the negative: this campaign's cost per registration has no demonstrated direction, and every attempt to give it one, by audience, by weekday, by wear, has been falsified within a week of being written.

One increment is not a curve, and neither is one average.

The winning ad's frequency crossing was estimated at Sept 17, Sept 21, Sept 19, Sept 20, and then at a spread running from Sept 17 to past Oct 1 depending on which steps were used. The ad never changed. The increments ran 0.21, 0.18, 0.16, 0.13, 0.07, 0.16, 0.08 and 0.04, and every revision of the date moved in the direction of the two most recent readings. Sept 14 ends the argument in the least satisfying way available: the tenth reading is negative, and the two windows this page can read the ad in disagree with each other by 0.08 on the same morning, which is larger than four of the eight increments that were being interpreted. There was never enough signal here to date anything. The Sept 16 adds the cleanest statement of the problem the series has produced. The quantity moved 0.05, from 2.78 to 2.83, and the crossing date it implies moved five days, from about Sept 26 to about Sept 21. That is the sixth revision in six mornings and the first one where the input and the output can be compared directly: the derived date is more volatile than the thing it is derived from. The two window test that would have settled the measurement question is now closed as untestable, because it needs two windows over identical delivery and identical delivery only exists when the account is switched off. The standing correction is unchanged and firmer: state the spread before naming a date, and treat the date as the least informative thing on the chart.

An ad set with one ad has no shock absorber.

CMS Social B bought four registrations at $8.78 against the winner's $6.66 and produced nothing on its last three funded days, so switching it off was right. The cost of being right is that the campaign runs on a single creative, and the three dearest days it has ever had all landed after. On Sept 10 it paid $19.01, on Sept 11 $9.53 and on Sept 12 $9.24, with nothing else in the ad set for Meta to move the money to on any of them. Cutting the last alternative and building the next one are one decision, and this account did the first half five days before the second. The second half arrived on Sept 14 and it did not arrive here: the Same Day hook was launched as a separate campaign rather than as a second ad in this ad set. So the account now has a spare creative and this ad set still does not, and on Sept 14 that showed. The campaign spent $23.38 on its one ad and bought nothing, with nowhere for Meta to move the money. It showed again on Sept 22, its last day before the owner paused it: $29.60 for nothing, with the ad 0.11 below its fatigue threshold and still no second creative in the set.

Cost per registration still does not track spend, and the spread keeps growing.

Nine finished days, ordered by money: $26.79 bought registrations at $4.47, $34.03 at $8.51, $36.94 at $9.24, $38.01 at $19.01, $38.10 at $9.53, $38.79 at $3.88, $40.57 at $4.06, $41.83 at $4.65, $44.86 at $8.97. There is still no slope, and the audience-ceiling story stays dead: the heaviest day is not the dearest and the two cheapest registrations came on the third and fourth heaviest days. Four of the days sit between $36.94 and $38.79 and bought registrations at $9.24, $19.01, $9.53 and $3.88, a five-fold range at one level of spend. Whatever moves this price, it is not the size of the cheque. Sept 14 adds the sharpest point on the same chart and it cannot be plotted: $23.38 bought no registration at all, which is not a high price but the absence of one.

A single day's price on a few dollars of spend is not an allocation argument.

For three mornings this page said the Page Likes budget was misallocated, because the ad taking most of the money kept buying the dearest follows. On Sept 10 Brand Ad bought nine follows at $0.41 and Service Fire 23 at $1.04. On Sept 11 Brand Ad bought one at $2.32 and Service Fire 32 at $0.72. On Sept 12 Brand Ad bought four at $0.64, exactly its lifetime price. Three days, three different stories, all on two to three dollars a day. On lifetime the case survives in a much milder form, and Sept 14 turned the mild version into a real one from the other direction. Brand Ad took $33.75 of the campaign's $37.65 that day and bought 34 follows at $0.99, which is no longer a three dollar sample and is no longer cheap: its lifetime price has gone from $0.65 to $0.93 while it scaled, and the campaign broke a dollar a follow for the first time on the same day. The allocation argument was worth making on lifetime and worth making against Brand Ad rather than for it, and on Sept 18 the lifetime figures finally made it cleanly. Brand Ad is the DEAREST of the seven ads this campaign has run, $0.93 on $156.59, and it takes all of the money. The ad that bought follows at $0.82 did so on $220.48, more money than Brand Ad has ever had, so this is not a scraps against scale comparison and the usual caveat does not rescue it. What kept this argument muddy for a week was making it from single days of two or three dollars. Made from lifetime prices at comparable spend it is short and it holds.

The registrations are verified, and a verification is true on a date rather than forever.

The account read for four mornings as though it might be inflated, because the registration event can fire a second time when an existing registrant opens the webinar room in a fresh browser. The owner reconciled the list against WebinarJam on Sept 9, and confirmed on Sept 16 that all 76 are verified. The account's output is real and no price on this page rests on an unchecked number. The durable lesson is in the shape of what happened between those two dates. The Sept 9 check covered the 41 that existed then, and by Sept 16 the unverified share had regrown to 46 percent of output, with two campaigns launched and priced against it in the meantime. Nobody decided to let that happen; it happened because a verification reads like a permanent property of the data and is actually a measurement with a date on it. So the standing instruction is no longer to raise this every morning, which produced six identical asks and a share that grew on each one. It is to report the verified count and its date, report what has been added since, and raise it again when the unverified share passes about a third of output or a scaling decision is on the table.

The format claim holds where it was earned and nowhere else.

On the CMS campaign, across nine days and four creatives, the finding is solid: once the buy optimized for completed registrations rather than clicks, a voiced social motion hook bought almost everything and the plate videos beside it barely delivered. On Sept 12 this page exported that finding to a campaign two days old, wrote that its video cut converts and its statics do not, and the static offer card bought a registration the next morning at $15.94. A lesson earned on nine days of four creatives is not evidence about two days of four different ones. The Agency Ceiling campaign now reads three registrations on the 42 second cut and one on a static, which is a campaign with two working creatives and, after four funded days and $139.25, no third registration from either of them.

The creative is the targeting.

With broad targeting the ad itself has to call out the right agent. That is why the answer to a stalling campaign is usually another hook, not another setting. The Agency Ceiling principle got its real test on Sept 14, when the CMS creative finally left Florida. The winning ad named the state in caption, on screen text and voiceover, which is why the campaign could not be widened without a re-render; the Same Day script was written off Florida entirely and launched across seven states, and on its first part day it bought 2 registrations at $5.13 while the Florida ad bought none on twice the money. The Agency Ceiling campaign is the counterexample that keeps this honest: also broad, also seven states, four creatives aimed at agency principals, and after four funded days and $139.25 it has 4 registrations at $34.81 and has bought nothing since Sept 12. Broad targeting puts the whole weight on the creative, which cuts both ways.

Ad test creatives

New creative built for testing lives on its own page, so this one stays a read of what is actually running.

New media

Fresh creative, before it enters a campaign.

Two rounds of value stories: the original six, plus a Round 2 owner series built on the evolved creative formula.

Timeline

  1. Aug 25First four Meta ad sets launched: Legacy v1/v2/v3 and Page Likes Interests.
  2. Aug 27Registration tracking fixed across all five webinar configs; Legacy links moved to the fbclid-safe register URLs; Google and Microsoft switched off, Meta stays live.
  3. Aug 31Legacy consolidated to one funded ad set (v1 at $30 a day, v2 and v3 paused); CMS V1, CMS V2, and Hybrid built and published; two new Page Likes ads shipped.
  4. Sep 1Round two creative library staged (four new hooks). Morning pull: Legacy 773 views at $0.14, Page Likes 139 follows at $0.83, frequency 1.5 to 1.7, still zero attributed registrations.
  5. Sep 2The objective switch. The Legacy traffic buy is retired and two registration campaigns go live on the fixed pixel, optimizing for completed sign-ups instead of landing page views. Budgets settle at about $30 a day per group, and the round two statics and social motion hooks all reach the auction by that night.
  6. Sep 3The registration column moves off zero and the first four hold up in WebinarJam. The owner prunes four Page Likes experiments that had pushed cost per follow up, and switches the older Brand Ad back on.
  7. Sep 4The day the account changed shape. CMS Social A starts converting and the owner verifies the registrations against the WebinarJam list. Legacy is paused on the evidence, 2 registrations at $33.15 against CMS at $8.14 on nearly identical spend, and its budget moves to CMS, a deliberate 10 percent step that did not reset the learning phase. Page Likes expands from Florida to seven southeastern states, which CMS cannot copy because its winning ad names Florida three ways.
  8. Sep 5Nothing was changed and the campaign got cheaper anyway. Both live campaigns underspent their budgets and still produced the cheapest finished day so far. Grow Your Book and the 9:16 motion cut go off, leaving Page Likes on three ads.
  9. Sep 6The same pattern, plus the first real constraint. The winning ad's frequency climbs from 1.62 to 1.83 in a day against a reach of 825 in one state, so the geo re-render moves from a nice-to-have to the item with a clock on it. CMS Social B converts again on almost no delivery. Image B Ownership drops to a Below average engagement ranking. The account activity log was unreachable, so nothing here is attributed to a person. Later the same morning the owner raised both live campaigns 10 percent on that evidence, CMS from $33 to $36 and Page Likes from $30 to $33, taking committed spend from $63 a day to $69. Both campaigns were read back Active after the write, so the silent pause that followed a budget change on Sep 4 did not recur.
  10. Sep 7The first day the numbers argue against the pending budget increase. Yesterday the CMS campaign ran to $44.86 on a $33 budget, roughly the spend the increase was asking for, and bought five registrations at $8.97 where the smaller day before it bought six at $4.47. The winner's frequency reached 2.01 on a reach of 1,098, still inside Florida. Four wave two Page Likes motion cuts cleared review and are delivering, the Brand Ad is switched off, and the account activity log was unreachable for a third day, so nothing here is attributed to a person.
  11. Sep 8The first finished day on the raised budget, and it did not settle the question. CMS spent $34.03 of its new $36 and bought four registrations at $8.51, a second expensive day after Sep 6's $8.97, on less money rather than more. Then this morning opened at four registrations for $15.08, $3.77 each, the cheapest start the account has recorded, and the lifetime price improved from $6.88 to $6.72 as attribution caught up. The winner's frequency reached 2.17 on a reach of 1,269, still inside Florida. Page Likes bought 62 follows at $0.70, its cheapest finished day, and the Brand Ad is switched back on and delivering. The account activity log was unreachable for a fourth day, so nothing here is attributed to a person.
  12. Sep 9The judgement date, answered twice over. Sept 8 finished at $38.79 of CMS spend and bought ten registrations at $3.88, the best finished day the account has recorded on both volume and price, which breaks the tie the two expensive days created. Across five finished days the cost per registration does not track spend, so the $8.97 and $8.51 run reads as a wobble rather than a ceiling. The owner also reconciled the registrant list against WebinarJam and the registrations are real, which closes a caveat that had been carried for four mornings. On that pair of answers both budgets were raised another ten percent, CMS from $36 to $40 and Page Likes from $33 to $36, taking committed spend from $69 a day to $76; both campaigns were read back Active after the write, the fourth clean budget change in a row. CMS V1 and CMS V2 are switched off, leaving the ad set on its two working hooks, and the cut recommended three mornings running on Image B Ownership is withdrawn because at $0.89 against a campaign $0.85 it is at par. The winner's frequency reached 2.30 on a reach of 1,428. The geo re-render is deliberately on hold: the creative does not exist yet, so the account is buying volume now and will meet the frequency threshold without a wider audience ready.
  13. Sep 10The first finished day at the raised budgets came in and it held: $41.83 of CMS spend, nine registrations at $4.65, the second cheapest day on the account, which puts two of the three cheapest days in the last two days. Page Likes bought 53 follows at $0.82, a seventh straight day inside its band. Wednesday finished and joined the cheap weekday group, so the split is now four cheap days against two dear ones with no overlap. The reading that changes the plan is the frequency curve: the winner went 2.30 to 2.37, an increment of seven hundredths against 0.13, 0.16, 0.18 and 0.21 before it, while its reach grew 296 in a day, the largest single-day gain of the run. The climb is decelerating, so the Sept 17 threshold date is revised to about Sept 21 and the geo re-render moves from critical path to insurance. What is tightening instead is the winner's click-through, 3.14% lifetime against 4.11% in week one, a 23.6 percent fall that is close to the plan's 25 percent rule. CMS Social B took its two largest days of delivery and produced nothing, moving its lifetime price to $8.69. Nothing was published, paused, edited or budgeted, and the Meta reporting connector failed authentication for a sixth day, so nothing here is attributed to a person.
  14. Sep 11The account grew a third campaign and the CMS half got thinner in the same twenty four hours. The Agency Ceiling campaign, built and switched on by the owner, started delivering this morning: $43 a day, four ads in one broad ad set across seven southeastern states, a hard stop on Sept 17 when its webinar runs, and $7.07 spent with no registration yet. Committed spend goes from $76 a day to $119. Against that, Sept 10 finished as the CMS campaign's worst day since its learning phase, $38.01 for two registrations at $19.01, and the owner switched CMS Social B off, which leaves the ad set on a single creative. That creative tripped the plan's click-through fatigue rule this morning at 3.00% against a 4.11% first week, a 27.0 percent fall, which grades yesterday's dated call right a day early. Frequency contradicted yesterday rather than confirming it: the increment came in at 0.16 after the 0.07 that had looked like deceleration, so the threshold sits near Sept 19 and the step is noisy rather than bending. Page Likes did none of this, 51 follows at $0.76. Nothing was published, paused, edited or budgeted by this check, and the Meta reporting connector failed authentication for a seventh day, so nothing here is attributed to a person.
  15. Sep 12The day the weekday story broke and the new campaign answered its question. Friday finished at $9.53 a registration on $38.10, which is neither Thursday's $19.01 nor a return to the $4 run before it, so the outlier call this page made yesterday is graded wrong and the middle outcome is the informative one. Friday is also the first weekday this panel has read twice: $4.06 on Sept 4 against $9.53 on Sept 11, on almost identical money, a gap wider than the one the panel was built to explain. Sorted by date the two dearest complete days on the account are the two most recent, which is the shape of a creative wearing rather than a calendar. The Agency Ceiling campaign bought its first registration on Sept 11 at $34.44, two days ahead of its dated call, with one of its four ads buying it and the other three spending $21.64 between them for nothing. A method correction goes with all of it: the click-through rule tripped on Sept 11 against a cumulative lifetime average, which falls by construction once current days sit below the historical mean, so the daily rate is the honest instrument and it has been flat near 1.9% for three days at about half the first week. Nothing was published, paused, edited or budgeted by this check, and the Meta reporting connector failed authentication for an eighth day, so nothing here is attributed to a person.
  16. Sep 13Saturday answered the discriminating call and the account grew a second problem while it did. CMS finished at $9.24 a registration on $36.94, above the $7 line, so the trend reading beat the weekday reading and the panel is retired for good: Saturday is the second weekday to be read twice and, like Friday, it moved from the cheap group to the dear one on similar money. The three dearest of the campaign's nine complete days are its three most recent, and the last two sit two cents apart, which is the shape of a step rather than a slide. The Agency Ceiling campaign had its second funded day and tripled its output: three registrations at $16.92, taking it to four at $21.48 lifetime, and one of them was bought by the static offer card that this page had recorded the previous morning as part of a pair that bought nothing. The owner switched AC | You Lead off after three funded days and $15.63 with no registration, the only ad-level change on the account since Sept 10. The finding nobody was looking for is in the steady campaign: Page Likes follows have fallen on five consecutive days, 62, 54, 53, 51, 47 and then 36, on spend that went from $43.33 to $21.81 against an unchanged $36 budget, while the cost per follow stayed inside the band it has held for ten days. A ratio held while the thing under it shrank. Nothing was published, paused, edited or budgeted by this check, and the Meta reporting connector failed authentication for a ninth day, so nothing here is attributed to a person.
  17. Sep 14The account stopped. Meta attempted to charge the card ending 5235 three times on Sept 13, for $18.00, $2.33 and $2.33, and all three failed, the day after six charges of $18.00 on the same card all cleared. The ad account is disabled, every live campaign shows Payment error in place of a delivery status, and the balance due is $19.10. Sept 13 finished at $1.54 of spend against $119 committed with no registration and no follow anywhere on the account, and Sept 14 has bought nothing at all. Two dated calls this page was holding open, on whether the CMS price had stepped to a new level and on whether Page Likes had a delivery problem, named Sept 13 and Sept 14 as their evidence; both are re-dated rather than graded, because the evidence was removed rather than contradicted. The winning ad's frequency fell for the first time in the series, 2.65 to 2.57, and the fall is an artefact twice over: the ad served 14 impressions in three days, and two report windows covering identical delivery returned 2.65 on a reach of 2,185 and 2.57 on a reach of 2,258 on this one morning. Nothing was published, paused, edited or budgeted by this check, no payment was made or attempted by it, and the Meta reporting connector failed authentication for a tenth day.
  18. Sep 15The account came back and arrived with two more campaigns than it left with. The balance was paid, every campaign reads Active, the current balance is $8.78 and no charge has failed since Sept 13, though the billing threshold has moved off $18 to $21 and $10 amounts. Delivery resumed on Sept 14 and the day finished at $120.37 against $209 committed. The shape change is the owner's: the Same Day script was locked on Sept 14 and shipped as a new campaign, HPM | CMS 2027 Final Rule | Leads | SE7 at $40 a day running Same Day A | Know It Cold across a broad seven state ad set, recorded at the time as the fresh hook and the geo re-render in one build, and corrected on Sept 17 to the geo re-render only, because its locked script carries the same claim as the ad it replaced; and a second Agency Ceiling campaign at $50 a day runs the same ads against a licensee audience. Committed spend goes from $119 a day to $209. The new campaign bought both of the day's registrations, 2 at $5.13, while the Florida ad spent $23.38 and bought none, its first funded day without a registration, on a day its click-through read 2.10% and five people reached the landing page. The two Agency Ceiling campaigns spent $49.09 between them and bought nothing, which takes the broad one's lifetime price from $21.48 to $34.81 on a count frozen at 4. Page Likes spent 105 percent of its budget, which answers the delivery question opened on Sept 13 in the direction of a dip, and cost $1.02 a follow doing it, the first time it has been over a dollar, because Brand Ad took $33.75 of $37.65 at $0.99 while Service Fire took nine impressions. Nothing was published, paused, edited or budgeted by this check, no payment was made or attempted by it, and the Meta reporting connector failed authentication for an eleventh day.
  19. Sep 16The best finished day the account has had, and the morning its own reasoning came apart. Sept 15 spent $181.58 against $209 committed, 87 percent, with every live campaign delivering and 10 registrations bought. The two CMS campaigns ran side by side on identical $40 budgets for the first complete day and the Florida one won both ways: 6 registrations at $5.66 against the seven state campaign's 4 at $8.12, and 3.73% link click-through against 3.30%. This entry originally called that a creative result and it is not one; both arms carry the same claim, and the correction was made on Sept 17. The click-through reading is the one that matters beyond this account. This page argued for five mornings that the winner was worn because its day level click-through had settled near half its first week, in a band of 1.83% to 2.15% across five readings. Yesterday it read 3.73% and the new creative read 3.30%, both roughly double the day before, and this morning they read 3.87% and 3.13%. Two different creatives in two different geographies moved together, so the band was measuring the day and not the wear. Page Likes came back under a dollar at $0.95 as Brand Ad's share fell from 90 percent to 72, and Service Fire, the ad this page has called starved rather than tested, was given $3.72 and bought follows at $1.24, dearer than the Brand Ad it was being compared against. The two Agency Ceiling campaigns took $79.06 and bought nothing for a third complete day; the licensee one then bought its first registration this morning at $5.53 at ad level, and both stop tomorrow. The two unpublished drafts are cleared and Same Day B | Ready Client is live on $1.63, so the locked A/B has both arms for the first time. Nothing was published, paused, edited or budgeted by this check, no payment was made or attempted by it, and the Meta reporting connector failed authentication for a twelfth day.
  20. Sep 17Delivery across the account faded out during Sept 16 and the day finished at $86.02 against $209 committed, 41 percent, having spent $77.63 of it before 8:30am. The remaining fifteen and a half hours added $8.39 across five campaigns. The hourly breakdown in the ad account time zone shows all three live campaigns delivering normally to about 9am, then in pennies, and stopping completely between 11am and 2pm; the Florida campaign ran to 1pm and its thirteen hourly rows sum to exactly its day, against a Sept 15 that delivered until 11pm. That shared curve across three campaigns makes it an account level event rather than a campaign level one. The first version of this entry said delivery stopped dead at 9am; that was read off a grid that renders only nine rows until its own scrollbar is dragged, and it was corrected the same day. Nothing in Ads Manager explains it: every campaign read Active, no charge failed, there is no payment error, the balance is $10.80 and the threshold has taken $33.00 and two $15.00 charges since. Delivery is normal again this morning, $52.06 by 8:25am against the $116 now committed. Every price on the short day read normally, which is the finding: a page built out of ratios had nothing to say about whether the account ran. Inside it the paired comparison held, because both arms were truncated at the same hour on the same budget: the Florida ad bought 3 at $7.73 against the seven state ad's 1 at $11.71, and it took $23.18 against $11.71 from identical $40 budgets. Lifetime the two have moved from 24 cents apart to $1.85 apart. Both Agency Ceiling campaigns stopped on schedule and the buy closes at $255.15 for 5 registrations, $51.03 each, taking $93 a day off committed spend. Same Day B took 20 percent of its ad set this morning against 3 percent yesterday. Nothing was published, paused, edited or budgeted by this check, no payment was made or attempted by it, and the Meta reporting connector failed authentication for a thirteenth day.
  21. Sep 18Sept 17 closed normally and settles the question Sept 16 opened: $108.98 against $116 committed, 94 percent, delivered across the whole day rather than front-loaded. Sept 16 was an event, not a regime, and the right response to it was to do nothing, which is what was done. Ten registrations, eight to the Florida campaign at $4.98 on its full budget, its cheapest complete day since Sept 8 and its third win in a row over the seven state campaign. The day inside the seven state campaign is the one that mattered: $29.60 for two registrations at $14.80, split $24.16 to Same Day A for one and $5.44 to Same Day B for one, and the owner switched Same Day A off that evening on exactly that arithmetic. It is the first ad level cut on this account made by the owner rather than proposed by this page. The campaign stays live at $40 a day on Same Day B alone, so committed spend is unchanged at $116, and whether to pull it is an open owner decision. Two dated calls resolved. The three day comparison graded RIGHT, all three days to Florida. The click-through call graded WRONG: the two CMS ads closed 1.16 points apart against a 1.0 bar, so that number carries both a day term and an ad term and this page read the sum as the second one for five mornings. This entry also carried two claims that were corrected later the same day and the corrections are recorded here rather than quietly removed. It said the frequency runway had reversed, from 2.91 to 2.65 on a reach up 765 to 3,329: that figure was read at campaign level and appended to a series built from the winning ad, the ad itself went 2.91 to 2.97 on a reach of 2,564 to 2,681, and the crossing date is reinstated at about Sept 26. It also said Service Fire took nothing for a fourth day, implying an active ad being denied delivery: the ad is PAUSED, and across Sept 8 to Sept 12 it had been the set's heaviest funded and cheapest ad at $90.57 for 109 follows at $0.83. AT MIDDAY THE ACCOUNT CHANGED SHAPE AGAIN, and this one is the owner's: he paused `CMS 2027 | SE7 | Broad` and `Page Likes | FL | Interests` to conserve budget, with about $500 left to the end of the month. He paused them AT AD SET LEVEL, so both campaigns and all their ads still read ACTIVE while neither can spend a cent, which is the third distinct way in one week that something here has read as on while not running. Committed spend falls from $116 a day to $40 and `CMS 2027 | FL | Leads` is the only live ad set left. Both campaigns were recorded here that day as closing on 11 registrations at $10.31 across $113.38 and 746 follows at $0.88 across $652.94; those were partial-day reads taken while the day was still running, and the true closing figures, pulled on Sept 19, are 11 at $10.35 across $113.83 and 748 follows at $0.87 across $653.47. Two dated rows close as DESTROYED EVIDENCE rather than grade, both declared: the Sept 20 seven state comparison, and this morning's own delivery assertion, whose denominator was halved four hours after it was written. The Service Fire recommendation is WITHDRAWN, because its ad set is now off. Nothing was published, paused, edited or budgeted by this check; both account changes today were the owner's.
  22. Sep 19Sept 18 closed and the number that matters is not the account total. The account finished at $117.29 against the $116 committed at midnight, which reads as an ordinary 101 percent day and is nothing of the sort: two of the three ad sets were paused at 11:58am, and the Florida campaign ran all twenty four hours to $62.71 on a $40 daily budget, 157 percent, by far the largest day it has ever spent and well outside the roughly 25 percent a day Meta documents. It is real spend and not a rendering fault, which was checked three ways: the twenty four hourly rows sum to exactly $62.71 with every hour present, impressions and reach rose with the money at 956 and 724 against a series running near 650 and 520, and the activity log carries no budget change. Nor is it one campaign's property. Through 11:59am, the hour the other two were paused, Florida had taken 78 percent of its budget, the seven state campaign 74 percent of its own and Page Likes 69 percent of its own, so all three were pacing between 140 and 157 percent on the same day, which makes it a property of the day. What the extra money bought was worse: 48 percent more impressions than Sept 17, link click-through DOWN from 2.79 to 2.51 percent, cost per link click UP from $2.22 to $2.61, and five registrations at $12.54 where the cheaper day before bought eight at $4.98. That reading is uncontrolled and is labelled so, because the second CMS arm that could have said whether Sept 18 was simply a dearer day was paused at midday; losing the control is a real cost of the pause and it is the first time this page has had to say so. The consequence is arithmetic and it is the day's decision: twelve days at the nominal $40 is $480 against about $500, and twelve days at Sept 18's rate is closer to $750, so the $480 is a floor rather than an estimate. A throttle to $36 scales the floor and not the multiple. The recommendation moves from throttle-or-limit to the limit, and it is a billing action the owner takes. One dated call graded and it graded RIGHT on both bits: the instrument assertion written yesterday to test whether the frequency unit correction held said the series would read above 2.97 on a reach above 2,681 at AD level, and it reads 3.09 on 2,894, with the reach step of 188 well inside a day in which the ad reached 724 people. The crossing moves three days earlier to about Sept 23, and that is the budget rather than the audience. Yesterday's own delivery assertion closes as DESTROYED EVIDENCE and is deliberately not banked although its number cleared: the day passed $98 for a reason opposite to everything it asserted. One thing published here yesterday is corrected. The Service Fire recommendation was recorded as WITHDRAWN; the activity log shows the owner ACTED ON IT, switching the ad back to Active at 11:55am and pausing its ad set at 11:58am, so it is armed rather than moot and will run the moment the campaign restarts. The Ad Library archive produced its first real diff against a like-for-like basis and there is no material change: 179 ads across nine tier-1 pages, one new competitor ad which is a third copy of a concept that page already ran twice. The diff's own NEW CONCEPTS line was checked against ad ids and discarded as an artefact of this archive's title transcription rather than a market event. Nothing was published, paused, edited or budgeted by this check.
  23. Sep 20The Sept 19 instrument assertion resolved and it resolved WRONG, which is the whole finding. It said Sept 19 would close at or under $48, 120 percent of the $40 committed, and that anything above meant the overspend was not a one-off. Sept 19 closed at $68.07, 170 percent, a HIGHER multiple than Sept 18's 157. Then Sept 20 closed at $51.84, 130 percent, a third consecutive day over budget. Three days over budget is a pattern, not a wobble. The benign explanation was checked and killed in the same pass: the parked catch-up idea was that Meta was recovering a trailing weekly average, but the trailing seven days spent $302.98 against the $280 that seven days at $40 commits, which is 108 percent of the weekly budget and not a recovery toward it. What the three days bought splits sharply and is uncontrolled either way: Sept 19 bought eight registrations at $8.51 with link click-through back up at 3.23 percent, Sept 20 bought one at $51.84 at 2.21 percent, the dearest priced day the account has recorded. One registration is not a price, the count can still rise under seven day attribution, and with the seven state arm off there is no second unit to run the lockstep check against, so none of this is read as a verdict on the creative. The money is the decision and it is shorter than it was: Sept 19 and Sept 20 took about $120 of the roughly $500 the owner had, leaving about $380 for ten days, and ten days at even the nominal $40 is $400. The recommendation is unchanged in direction and firmer in degree: an account level spending limit is now the only instrument that fits, because a throttle scales the nominal number while the overspend scales the multiple. It is a billing action and the owner's alone. No run happened on Sept 20, so this entry and the Sept 21 pull cover both days. Nothing was published, paused, edited or budgeted by this check.
  24. Sep 21Two runs on one date: a midnight run covered the closed days Sept 19 and Sept 20, and this morning run re-verified them and read the open day. Sept 20 re-verifies EXACTLY unchanged at $51.84 and one registration, with no attribution rise, and its twenty four hourly rows sum to the day total to the cent. The new reading is that Sept 21 is pacing below all three overspend days, and the cut that shows it is the same hours rather than the budget: through hour 08 it has spent $14.03 against $23.86 on Sept 19 and $16.44 on Sept 20, which on those days' own close-to-hour-08 multiples of 2.85 and 3.15 puts it near $40 to $44. That is a leading read on the assertion resolving tomorrow, not a result, and it does not reopen the settled finding that the overspend is a regime. Billing is clean with the threshold at $17, three charges on Sept 20 and one at 6:12am on Sept 21, none failed, and the activity log carries no owner action and no budget change since Sept 20, so the overspend is not an edit. The frequency panel found a fault in itself: Sept 21 read 3.21 at 00:46 and 3.26 at 09:20, so the sampling hour is worth 0.045 while a real day is worth 0.06 to 0.11, and the series had been carrying an undeclared clock-time index. The morning reading is the convention-consistent one and the crossing moves to about Sept 24 with a two day band. No second Ad Library pull was taken, because the archive is one file per day and an eight hour diff on a capped moving window manufactures exactly the false signals the Sept 21 appearance guard was built to suppress. Nothing was published, paused, edited or budgeted by this check.
  25. Sep 22The overspend stopped at three days. Sept 21 closed at $38.67, 97 percent of its $40 budget, and the instrument assertion written against it grades RIGHT on both bits; its 24 hourly rows sum to exactly $38.67. The trailing week still reads 114 percent of the weekly budget, so the spending-limit recommendation stands. Frequency 3.35 on 3,400, and the crossing held at about Sept 24 for the first time in ten readings. The Ad Library corrected itself: a tier-1 competitor page returned the IDENTICAL seven ad ids it was reported to have lost, so the Sept 21 disappearance was an empty result from the index rather than a page going quiet, and a zero-coverage guard was added to the diff tool. Next: grade the Sept 22 closed day against the $48 bar, and watch the winner cross 3.5 with no second creative behind it.
  26. Sep 23The owner paused the last live ad set, CMS 2027 | FL | Leads, at 9:02pm on Sept 22, per the activity log, so the account has no delivery anywhere while all three campaigns still read ACTIVE. Sept 22 closed at $29.60 with no registration, and its instrument assertion graded RIGHT on both bits; the pause removed at most $9.48 of possible spend and did not decide the grade. The two fourteen day forecasts written on Sept 9 graded WRONG, 52 registrations against a low end of 69 and 324 follows against 698. Frequency froze at 3.39. One tier-1 competitor page built 45 ads across eleven concepts in one afternoon, four of them revivals. CORRECTED SEPT 24: those four were not revivals. Every one had been running throughout; the page refreshed them with new ad ids. Nothing was published, paused, edited or budgeted by this check.
  27. Sep 24Sept 23 closed at $0.00 on every unit on the account, the first full day with every ad set paused, and the instrument assertion that a paused account stays at zero graded RIGHT; the activity log shows no owner action since 9:02pm Sept 22. Meta restated Sept 21 and Sept 22 upward by twenty cents in all, so the Florida lifetime reads $759.38. Frequency read 3.39 again. Yesterday's report of four competitor revivals is withdrawn: checked against ad ids, the four concepts had been live in every pull since Sept 19, so the diff was reading a gap in creation dates as a gap in running, and it now separates a refresh from a revival. Nothing was published, paused, edited or budgeted by this check.
  28. Sep 25Sept 24 closed at $0.00 on every unit, the second full day with every ad set paused, with no charge, no owner action in the log and, unlike the day before, no restatement, so the Florida lifetime still reads $759.38. Frequency read 3.39 for a third morning and the page stopped printing a crossing date, because two flat steps take the checker to its undated branch. The Ad Library showed no material change. Nothing was published, paused, edited or budgeted by this check.
  29. Sep 26Sept 25 closed at $0.00 on every unit, the third full day with every ad set paused, with no charge, no owner action in the log and no restatement. Frequency read 3.39 for a fourth morning and the page still prints no crossing date. In the Ad Library, a small tier-1 recruiting page went from two ads to six with one new concept, and a larger one built a third refresh batch of twelve. Nothing was published, paused, edited or budgeted by this check.
  30. Sep 27Sept 26 closed at $0.00 on every unit, the fourth full day with every ad set paused, with no charge, no owner action in the log and no restatement. Frequency read 3.39 for a fifth morning. With four days left, even the worst day on record fits the money, so the spending limit becomes a backstop. The Ad Library showed no material change; four AEP season ads one page dropped are confirmed gone on a second complete pull. Nothing was published, paused, edited or budgeted by this check.
  31. Sep 28Sept 27 closed at $0.00 on every unit, the fifth full day with every ad set paused, with no charge, no owner action in the log and no restatement. Frequency read 3.39 for a sixth morning. Three days are left and every rate on record fits the money. In the Ad Library one tier-1 page refreshed its seven ad Spanish language concept with fresh ids on a complete pull, a refresh and not a revival. Nothing was published, paused, edited or budgeted by this check.
  32. Sep 29Sept 28 closed at $0.00 on every unit, the sixth full day with every ad set paused, with no charge, no owner action in the log and no restatement. Frequency read 3.39 for a seventh morning. Two days are left and every rate on record fits the money. Nothing was published, paused, edited or budgeted by this check.
  33. Sep 30Sept 29 closed at $0.00 on every unit, the seventh full day with every ad set paused, with no owner action in the log and no restatement. The log does carry one Account billed event of $4.40 at 4:07am Sept 30 with no spend behind it, the first charge in eight days, recorded and not explained. Frequency read 3.39 for an eighth morning. Today is the last day of the month with about $311 of the roughly $500 unspent. Nothing was published, paused, edited or budgeted by this check.
  34. Oct 1Sept 30 closed at $0.00 on every unit, the eighth full day with every ad set paused, with no owner action in the log and no restatement. The only new log line is a Meta generated custom audience at 6:16pm, which is not delivery. Frequency read 3.39 for a ninth morning. September ended with about $311 of the roughly $500 unspent. Nothing was published, paused, edited or budgeted by this check.
  35. Oct 2Oct 1 closed at $0.00 on every unit, the ninth full day with every ad set paused, with no owner action in the log, no new charge and no restatement. Frequency read 3.39 for a tenth morning. Nothing was published, paused, edited or budgeted by this check.
  36. Oct 3Oct 2 closed at $0.00 on every unit, the tenth full day with every ad set paused, with no owner action in the log, no new charge and no restatement. Frequency read 3.39 for an eleventh morning. Nothing was published, paused, edited or budgeted by this check.
  37. Oct 4Oct 3 closed at $0.00 on every unit, the eleventh full day with every ad set paused, with no owner action in the log, no new charge and no restatement. Frequency read 3.39 for a twelfth morning. Nothing was published, paused, edited or budgeted by this check.
  38. Oct 5Oct 4 closed at $0.00 on every unit, the twelfth full day with every ad set paused, with no owner action in the log, no new charge and no restatement. Frequency read 3.39 for a thirteenth morning. The snapshot headline, direction line and restart tile still carried late September wording (three days left, spend past Sept 30) and were corrected. Nothing was published, paused, edited or budgeted by this check.
  39. Oct 6Oct 5 closed at $0.00 on every unit, the thirteenth full day with every ad set paused, with no owner action in the log, no new charge and no restatement. Frequency read 3.39 for a fourteenth morning. The forecast card still priced three days to Sept 30 and was rewritten as one change, and a stale Oct 1 phrase on the weekday panel was corrected. Nothing was published, paused, edited or budgeted by this check.
  40. Oct 7Oct 6 closed at $0.00 on every unit, the fourteenth full day with every ad set paused, with no owner action in the log, no new charge and no restatement that this check could see. Frequency read 3.39 for a fifteenth morning. Nothing was published, paused, edited or budgeted by this check.
  41. Oct 8Oct 7 closed at $0.00 on every unit, the fifteenth full day with every ad set paused, with no owner action in the log, no new charge and no restatement that this check could see; the three campaign lifetimes were re-read and are unchanged. Frequency read 3.39 for a sixteenth morning. Nothing was published, paused, edited or budgeted by this check.
  42. Oct 9Oct 8 closed at $0.00 on every unit, the sixteenth full day with every ad set paused, with no owner action in the log, no new charge and no restatement that this check could see; the log's only lines were ten custom audiences Meta itself created. Frequency read 3.39 for a seventeenth morning. Nothing was published, paused, edited or budgeted by this check.
  43. Oct 12Oct 11 closed at $0.00 on every unit, the nineteenth full day with every ad set paused, with no owner action in the log, no new charge, no new log line of any kind and no restatement that this check could see. Frequency read 3.39 for a twentieth morning. Nothing was published, paused, edited or budgeted by this check.
  44. Oct 11Oct 10 closed at $0.00 on every unit, the eighteenth full day with every ad set paused, with no owner action in the log, no new charge, no new log line of any kind and no restatement that this check could see. Frequency read 3.39 for a nineteenth morning. Nothing was published, paused, edited or budgeted by this check.
  45. Oct 10Oct 9 closed at $0.00 on every unit, the seventeenth full day with every ad set paused, with no owner action in the log, no new charge, no new log line of any kind and no restatement that this check could see. Frequency read 3.39 for an eighteenth morning. Nothing was published, paused, edited or budgeted by this check.
  46. NextThe account is off by the owner's hand and about $311 remains. The only decision is whether a restart is still wanted now that the CMS 2027 angle has decayed on Oct 1. A restart brings the one creative back as the live question, since it sits 0.11 below its fatigue threshold with nothing behind it. If it restarts, a spending limit at about $310 (an owner only billing action) caps the total whatever the daily rate does. The morning check reads delivery against status every run and will say so the day anything restarts.
  47. Oct 1The CMS 2027 angle decayed here. That deadline was the reason spending into a narrowing Florida audience looked like a reasonable trade: the volume was worth more before this date than the audience is worth after it.

Feedback on this page

Tell us what works and what to change.
It comes straight to Nick.

Optional. Add it and we'll write back when your note changes something.

What’s off? Paste it, link it, or add a file. Rough is fine.

Drag files here, or click to choose.Any type, up to 2 GB each, 10 per note.

Go-live: 9/1/26 · Last updated: 10/1/26