Affiliates & media buyers
Keep campaign/account sessions separated, assign proxies per Profile and automate repetitive approved browser work.
Open use case →Use cases
Start from the work you need to do, then use Profiles, proxies, automation, Browser API or MCP AI only where they add value.
Use cases
Each use case links to the smallest set of features needed to start.
Keep campaign/account sessions separated, assign proxies per Profile and automate repetitive approved browser work.
Open use case →Use Browser API, User Scripts, Puppeteer and MCP AI while keeping real persistent browser state.
Open use case →Separate client work into persistent Profiles and use repeatable Automation Studio workflows.
Open use case →Keep store/admin sessions organized and automate repetitive checks without mixing Profile state.
Open use case →Organize platform sessions, content workflows and supporting Free/VIP tools separately from the browser plan.
Open use case →Use persistent environments, browser screenshots, automation verification and developer inspection tools.
Open use case →Use controlled Profiles and proxies for legitimate regional price/content monitoring workflows.
Open use case →Connect an MCP-compatible client to a real persistent browser rather than a disposable web session.
Open use case →Pattern
The workflow is consistent even when the business goal changes.
Use one persistent Profile for one account/work context.
Add a proxy or extension only when the workflow needs it.
Use Automation Studio, User Scripts, Browser API or MCP AI.
Confirm important outcomes before increasing concurrency or scheduling.
Deep dives
These pages go deeper into the most important patterns already documented on the site.
Why automation should reuse durable browser state.
Learn more →How isolated Profiles change browser automation design.
Learn more →Keep people in the workflow for review and uncertain outcomes.
Learn more →