Timing a campaign: when to buy views and when to wait

Buyers ask when the algorithm rewards a post, as if there were an hour of the day when a purchase works and an hour when it does not. There is no public answer to that question, and a panel that offers one is guessing. What can be planned is the work: when the content is ready, when the audience sees it, when the order starts, when it finishes, and when you can measure the result.

This guide builds a buying calendar from three clocks that are printed on the service row: the start estimate, the delivery window and the refill window. It then shows when buying early helps, when waiting is the right choice, and how to keep the campaign from turning into a stack of orders with no baseline.

Three clocks

The start estimate is how long the supplier expects to wait before delivery begins. It is an estimate, not a promise. A queue can move faster or slower than the row says, and a supplier top-up can pause it. The number is still useful, because it tells you whether an order placed today can start before the deadline.

The delivery window is how long the delivery takes once it starts. Some rows deliver in one burst, some drip over days. The row may state an average time, and the order page shows the actual progress. Plan with the stated figure and check the order page for the real one.

The refill window is how long the supplier will replace a share of the delivery if it drops. It is measured from the delivery, not from the order, and it is attached to the row. A refill is a second order, so it has its own start estimate and its own wait.

The three clocks are the only timing numbers that belong in a plan. Across the active services in the catalogue, the median start estimate is 5 minutes. 0% of those services carry a refill flag. The averages are a planning reference, not a quote for a specific order.

Count backward from the deadline

A campaign with a deadline is a scheduling problem. Start at the deadline and subtract the clocks in reverse order. The result is the last date on which the order can be placed and still have a measurement day before the next decision.

Suppose the deadline is a launch on a Friday. The order has to be complete by Thursday so the count is visible on the day. The delivery window is on the row; subtract it. The start estimate is on the row; subtract it. The result is the placement date. If the row also has a refill window, add a check at the end of that window, after the launch, because the refill is a second decision and it needs its own slot.

The subtraction is simple, and it is where many campaigns fail. Buyers place the order on the deadline, then discover that the start estimate is longer than the time left. The order arrives after the launch, the count is not there when it was needed, and the campaign has paid for a signal that nobody saw. Counting backward prevents that. It also tells you when a row cannot meet the deadline at all, which is the point at which you choose a different row or a different date.

When to buy early, when to wait

Situation	Buy early	Wait
A launch that needs a visible floor	Yes, with a placement date that clears the start estimate	No, the floor has to be there on the day
A post still in its first distribution	No	Yes, the organic baseline is not complete
A small account testing a format	No	Yes, the content is the variable, not the count
A campaign with a hard end date	Yes, counted backward from the date	No, a late order misses the window
A post that is already performing	Only if you need a specific count for a pitch	Yes, the organic response is the signal
A platform cleanup period	No	Yes, a new delivery can be removed with the rest

A timing guide. It contains no market figures.

The last row is the one buyers cannot see. A cleanup is not announced in advance, and a panel cannot predict it. If the count is dropping across the market, or the platform has just removed a wave of accounts, a new order is exposed to the same event. Waiting a few days costs nothing and gives the platform time to finish. The signal is not a guarantee; it is a reason to pause a large order, not a reason to cancel a campaign.

The first day

The first day of a post is the baseline for every later comparison. If you buy before that day ends, the count you see is a mix of organic and purchased, and you cannot separate them. The result is a campaign that cannot answer its own question: did the post work, or did the order work?

Publish, record the count at a fixed time, and wait until you have a baseline. The fixed time matters more than the length. A count at the same hour on the next day is comparable; a count taken whenever you remember is not. If the campaign has a deadline that forbids waiting, write down that the baseline is compromised before you order. The record is still useful, as long as it is honest about what it contains.

The campaign calendar

Stage	Action	What to record	Decision
Before publish	Choose the variant and the row	Rate, minimum, start estimate, refill window	Can the row meet the deadline
Publish day	Publish, do not order	Count and reach at a fixed hour	Is there a baseline
Day two	Decide whether the work needs a floor	The first day of organic response	Buy, wait or stop
Placement	Place the order at the counted date	Order id, charge, start estimate	Does the order start on time
Delivery	Watch the order page, not the profile	Started, delivered, remains	Is the delivery complete or partial
Day seven	Count and reach again	Count, reach, audience mix	Did the delivery hold
Window end	Check the refill window	Count against the start count	Refill, refund or close

A calendar template. It contains no market figures.

The calendar is not a schedule for every campaign. It is a sequence that keeps the baseline, the order and the measurement in the right order. A campaign that skips the baseline can still be run; it just cannot be read. A campaign that skips the seven-day check can still be judged on the launch; it just cannot tell you whether the delivery held.

Budget pacing

Spread the budget across the campaign instead of spending it at the end. A large order placed on the last day has no time to be measured, no time to be refilled, and no time to recover from a queue. A smaller order placed earlier gives you a reading before the deadline and a reserve for the correction.

Keep a reserve for the refill window. A refill is a second order, and it may need a balance when the first delivery drops. If the wallet is empty at the end of the campaign, the refill is a new deposit and a new decision. A reserve turns it into a routine step.

Set a ceiling for the campaign, not only for a single order. The ceiling is the amount you are willing to spend on the work, and it does not move because the first order looked good. If the campaign needs more, that is a new decision with a new baseline, not an extension of the old one.

Pace by the calendar, not by the mood. A weekly cadence is easier to read than a burst: one order, one measurement, one decision, then the next week. The cadence also keeps the wallet predictable, because each week's spend is a known quantity rather than a reaction to the last count. If a week has no order, that is a valid step in the plan, not a gap to fill.

What to measure

Measure the count and the reach. A count without reach is a number that can rise while the post is shown to fewer people. The pair tells you whether the delivery added a visible signal or replaced an organic one. Saves, shares and comments are slower signals, and they are the ones that survive a cleanup.

Compare the same hour on the same day. A count taken at one hour and a count taken at another are not comparable, because the post has had a different amount of time and a different audience. The fixed hour is a small discipline that makes the record usable.

Platform and category	Services	Avg start	With refill
Instagram Followers	184	3 min	6891%
Instagram Likes	154	2 min	6966%
Spotify Plays	134	4 min	16284%
YouTube Views	94	3 min	13011%
TikTok Followers	86	3 min	10691%
TikTok Likes	69	2 min	11755%
YouTube Likes	69	3 min	20217%
Facebook Page Likes	68	4 min	5091%
Facebook Post Likes	64	4 min	3127%
Instagram Comments	64	4 min	1281%

Read from the Talon catalogue when the page is rendered. Average start is the mean of the start estimates on active services, in minutes. It is a planning reference, not a promise for a specific order.

The table shows where the catalogue has depth and where the start estimates are shorter or longer. It does not tell you which row will deliver on time today. For that, read the service row and the order page. The table is the map; the row is the road.

A five-minute check before you place the order

1. Write the deadline. The date and the hour the count has to be visible.
2. Read the three clocks. Start estimate, delivery window, refill window, from the row you will buy.
3. Subtract backward. Placement date equals deadline minus delivery minus start. If the date has passed, choose another row or date.
4. Record the baseline. Count and reach at a fixed hour, before the order.
5. Place the order at the counted date. Not earlier, not on the deadline.
6. Watch the order page. Started, delivered, remains. The profile is not the order record.
7. Check at seven days and at the window end. Count, reach, refill decision.

The calendar is the part of a campaign that survives a bad week. The content can change, the rate can move and the queue can stretch, but the sequence stays the same: baseline, order, delivery, measurement, decision. That sequence is what turns a purchase into a result you can read.

For the view side of the same question, read YouTube views and high-retention delivery. For the states an order passes through, read the order lifecycle. To plan around a specific row, open services with refill or the public market tables.