Drip delivery lets a destination receive contacts at a steady pace instead of all at once. It is built for warming up a fresh autoresponder account, where feeding new contacts in too fast is how sending reputations get hurt. Set a drip on that destination and WP Sync paces the flow for you, even while you sleep.
How a drip differs from a delay:
A delay holds each contact for a fixed time after it arrives, so a burst of 200 contacts delayed by an hour is still a burst of 200 an hour later. A drip gives each contact the next free slot, so the same 200 contacts arrive one at a time, evenly spaced.
Setting a drip:
- In the bridge builder, open the destination and click Delay / drip.
- On the drip line, choose how many contacts at most to send and the window they are spread across, in minutes, hours or days. For example one contact every 5 minutes, 50 contacts every hour, or 1,000 contacts every hour.
- Save the bridge. The destination step and the bridge row show a small drip tag with the pace, so you can see it at a glance.
Click Remove on the drip line to switch it off. The one dial covers everything from a gentle warm up trickle to serious throughput.
How the pace is kept:
The pace is enforced twice. Contacts are scheduled evenly across the window, and delivery itself never exceeds the rate. Even if your site sat quiet for hours and a backlog built up, catch up still flows at your pace, never as a dump, so the receiving app is protected.
Shared lanes:
Two bridges feeding the same app and list automatically share one lane, because the thing being protected is the receiving account. The pace you set is the pace that app really receives. Different lists and different apps each keep their own lane.
Using a drip with a delay:
The two work together. Wait ten minutes first, then drip one every five.
Controlling a running drip:
- Pause the bridge and the queue simply freezes. Nothing is discarded, and it resumes at your pace when you enable the bridge again.
- Deliver now sends everything that was waiting when you pressed it, ignoring the pace. It is your explicit call, and contacts arriving afterwards keep flowing at the drip pace.
- Discard drops the waiting contacts without sending them. Nothing is lost forever, because a later Backfill can still reach those people.
- Change the pace mid flight. Edit the drip and the contacts already waiting are re spaced to the new rate straight away, so you can speed it up or slow it down whenever you like.
Backfill and drip:
Backfill into a dripped destination schedules every contact onto the drip at your pace. The results window tells you how many are queued to drip out, how many went right away and roughly when the last one lands. It is safe to run twice, because anyone already waiting in the queue is skipped, so the schedule never doubles up.
A helpful nudge:
When a large batch arrives in one sync on a destination without a drip, WP Sync notes it in its log and points you at the drip setting. That is handy when you are warming up a fresh account.
Seeing what is waiting:
Contacts waiting in the queue show as a queued count on the bridge row, and they log as Queued in the Activity Log until they deliver. The Diagnostics support report shows each bridge's delay, drip and queue.