Skip to main content

Ad Traffic is a module inside Botlord Platform. Install and activate the platform first, then configure the engines available to your plan.

Profile strategy and session management

Fresh each run vs reused profiles, warmup, and how sessions are allocated to workers.

1 min read

Profile strategy modes

Lifecycle shows the current profile strategy labels. Fresh each run starts a new browser profile without history. Reuse and automatic strategies retain or select saved state where supported.

Choose the strategy for this campaign, then review its device surface and provider. Built-in saved profiles and managed provider profiles are different sources; check the selected runtime before reusing identities.

Lifecycle profile strategy showing Fresh each run
Lifecycle: Fresh each run starts a new profile without carrying history over. Open image for full size.

Profile warmup

Warmup is an optional task. Add it from Tasks, review its settings and save it before continuing. Profile persistence is a separate Lifecycle choice.

Fresh each run does not preserve profile history. Choose a supported reuse strategy when history must carry between runs.

Antidetect browser profiles

When using AdsPower or MultiLogin, each profile gets its own browser fingerprint, cookies, and local storage. Workers are assigned profiles from a shared pool.

Profile pool orchestration manages which profiles are active vs warming. In full orchestration mode the pool is the source of truth for allocation. Most operators start in read-only mode and upgrade if they need smarter allocation.

Delete after run (fresh mode only) removes the profile when the session ends, keeping disk usage bounded.

← All topics for Ad Traffic