Campaign and track setup

SoundCloud tasks and track configuration

SoundCloud tasks are the task type used in the streaming module. Each task targets a single track URL and plays it to a target play count. The bot opens the track as an anonymous listener, plays it for a randomised duration within your configured range, then waits for the inter-session delay before the next play.

SoundCloud counts a play after a minimum listening duration — the bot is configured to meet this threshold automatically. Sessions that end too early (network timeout, proxy block) do not register as plays.

Add track URLs to your campaign — one per entry. Each entry has its own target play count and min/max delay. The bot cycles through tracks in order and stops each track when its target is reached.

Set min delay to at least 60 seconds, max to 300 seconds or more. Very short gaps between plays from the same IP are a clear signal to SoundCloud's detection layer.

Proxies for streaming

Use residential proxies for SoundCloud play automation. SoundCloud tracks geo-location of plays — a diverse proxy pool produces more natural-looking listener distribution.

Rotate per session. Each play session should come from a different endpoint to distribute the geographic signal.

Schedule windows

Set a start and end hour to control when play sessions run. Spreading plays over a full day looks more natural than batching them in a short window.

Use the campaign start and end dates to pace plays across multiple days — a track reaching its target play count over 3–5 days looks significantly more organic than hitting it in a few hours.

Monitoring in Logs

Logs shows each play session: track URL, play duration, proxy used, and any errors. Watch for 403 errors (IP blocked) and timeout errors (session stalled).

SoundCloud counts a play after the track has played for a minimum duration. If sessions are ending too early, increase the minimum dwell time in session settings.