Use case
Scraping with profile isolation
Treat each Multilogin profile as one identity lane. This page is isolation and pacing hygiene — not a guide to bypass site ToS, CAPTCHAs, or access controls you are not allowed to hit.
Ops pattern
- One profile ↔ one sticky proxy ↔ one cookie jar.
- Warm slowly — warmup.
- Start via Launcher, attach Playwright (Pro+), stop when idle — API map.
- Log profile UUID + proxy geo for every failure class.
- Backoff hard when blocked; don’t burn an entire folder on one stupid rate.
Do not
- Blast thousands of cold profiles at once.
- Reuse warmed sessions across unrelated personas.
- Expect “undetectable” outcomes from tools alone.
When tools fail
CDP · Proxy · Token · API errors
Follow target sites’ terms and local law. Affiliate disclosure applies for Multilogin codes.