The Schedule and End Conditions
An acquisition stream runs on a schedule you control. Feeder streams have no schedule — they receive leads only when you move them in.
Schedule fields
Leads Per Day
1–50
optional
The daily volume target. Sits with the stream name rather than in the Schedule section, because it is what the cost estimate multiplies.
Default: 10
Active Days
day toggles
optional
Which days the stream acquires. Weekends are off by default. The number of active days also feeds the monthly volume estimate.
Default: Mon–Fri
Active Hours
time range
optional
The window within each active day during which acquisition runs.
Default: 09:00–17:00
Timezone
timezone
optional
The timezone the active days and hours are interpreted in. Searchable by city, region or offset.
Default: Your member timezone
Start Date
date
optional
The first day the stream may acquire. Set it forward to activate a stream now and have it begin later.
Default: Today
End Condition
never | date | lead_count
optional
What makes the stream stop on its own. See the table below.
Default: Run indefinitely
End conditions
| Option | Also set | Behaviour |
|---|---|---|
| Run indefinitely | Nothing | The stream acquires on every scheduled day until you pause it yourself |
| Stop on date | A date | Acquisition stops after that date. Useful for a campaign tied to an event or a quarter |
| Stop after N leads | A number | Acquisition stops once the stream has acquired that many leads in total. A budget expressed in leads rather than in days |
Info: The lead count for Stop after N leads counts every lead the stream acquired, whether it was pushed to your CRM or quarantined. That is the right basis for a budget: both kinds cost you the acquisition and the qualification.
Tip: Stop after N leads is the safest way to trial a new stream. Set it to a day or two of volume and the stream cannot overspend while you are deciding whether the targeting works. You can lift the condition later by editing the stream.
Warning: Active hours are interpreted in the stream's timezone, not the viewer's. If your team is spread across regions, check the timezone field rather than assuming it matches yours — it defaults to the timezone of whoever created the stream.
