Drip-feed: what it does and what it does not
Drip-feed splits one order into several equal runs and spaces them out over time. It is available on 27 of the services in this catalog — it is a property of the individual service, not a switch that works everywhere.
How the split works
You enter the total you want, the number of runs, and the interval between runs in minutes. The panel divides the total by the number of runs and sends each run as its own order.
An example. One thousand units, ten runs, a sixty-minute interval: each run carries a hundred units, one goes out every hour, and the last starts nine hours after the first.
Two things follow from the division, and both surprise people:
- Every run has to clear the service minimum. If a service starts at 100 units, an order of 1,000 cannot be split into more than ten runs. The form caps the run count at the total divided by the minimum — so if you want more runs, you raise the total, not the runs.
- The remainder is dropped. A thousand units in three runs is 333 each: 999 are ordered and 999 are charged. Runs of unequal size do not exist here, and you are not billed for the unit that falls off the end.
What it does not do
It does not spread an order across several posts. One order takes one link. Drip-feed stretches that single order along the time axis; it does not distribute it between publications. Several posts means several orders.
It does not change what arrives. The accounts, the region and the guarantee are exactly what they would be without it. Drip-feed controls arrival times and nothing else.
It does not make an order undetectable. This is the claim you will meet most often, and it is worth separating into the part that can be checked and the part that cannot. Gradual arrival does look different on a public growth chart than a vertical step does — that much is simply true, and a person reading your channel's chart will see it. Whether it changes anything inside a platform's own detection is not something anyone outside that platform can observe, and a service that tells you it does is describing a hope, not a measurement.
When it is worth using
The honest case for drip-feed is the human audience, not the algorithm. If your growth curve is something an advertiser, a client or a partner is going to look at, a slope reads better than a step. If nobody is going to look at the curve, splitting the order buys you nothing and delays the result.
The second case is matching a real event: spreading views across the hours a stream is actually running, or across the days a campaign is actually live, so that the numbers sit next to something that explains them.
Where to find it
The runs and interval fields appear in the order form only for services that support drip-feed; on the rest they are not shown at all. So if gradual delivery matters for a particular target, choose the service first and check that the fields are there before planning around them. Orders placed as a series get their own section in your account, where each run and its result can be seen separately.