A browser (Operate › Browsers) is one Chrome profile on one engine: its sign-ins (cookies, sessions) and the proxy it goes out through. Campaigns and Studio tests pick a browser per browser name (x, threads, facebook, shopee, default…). Pick the same browser in two campaigns and they share it, each run in a window of its own. Accounts are just data: they never hold a browser.
The page
| Column | What it shows |
|---|---|
| Name | Your name for it. A browser a run made shows <campaign> · <browser name>. |
| Proxy | The server it goes out through (empty: none). |
| Engine | The engine its profile lives on. Only campaigns and flows on that engine can pick it. |
| Used by | The campaigns, and flows' tests ((tests)), that picked it. |
| Now | Running or stopped (one its engine hasn't started yet is stopped; Engine unreachable only when its engine doesn't answer), and who runs in it now. |
- Add browser: a name and an optional proxy (
http://host:portorsocks5://host:port, username, password). It lives on the workspace's engine. - Edit: name and proxy. A new proxy restarts the browser with it once no run works in it. A blank password keeps the saved one.
- Live: starts it if it isn't up and shows it; Take control lets you use it, so you can sign in by hand without a run. Every campaign using it shares that sign-in.
- Delete: its profile and every sign-in in it go. Refused while a campaign or flow test uses it, naming them.
Where browsers come from
- A campaign's run (or a Studio test) needs a browser for each browser name its page nodes act in. A name with no browser picked gets a new one,
<campaign> · <name>, on the campaign's engine, kept as its pick. Every run also saves its browsers on the engine again: a profile the engine dropped (old stopped browsers cleaned up, an engine reset) comes back empty, so you sign in again instead of the run failing. - The campaign's Browsers tab picks per name: one of the browsers on its engine (with who else uses it), or New browser (made on the next run). See .
- Studio › Settings › Test browser picks the same way for the flow's tests, so a test can run in a campaign's signed-in browser.
When it goes
- Deleting a campaign deletes its browsers that no other campaign or flow test uses. A shared one stays for the others.
- Clear data › Browsers on a campaign does the same, and the campaign gets new ones on its next run.
- Moving a campaign or flow to another engine deletes its browsers nobody else uses on the old engine; it gets new ones on the new engine (sign in once there). Shared ones stay where they are.
- Purging a flow from the Trash deletes its test browsers nobody else uses.
FAQ
How do two campaigns use one browser?
In the second campaign's Browsers tab, pick the first campaign's browser for that name (it shows also Facebook Auto Reply). From its next run both work in that browser, each run in its own window (up to 3 at once); sign-ins and posts take turns.
Where do I set the proxy now?
On the browser, here. Accounts hold only their logins, posts-per-hour cap and name.
Can I sign in without running a campaign?
Yes: press Live, tick Take control and sign in. The session stays in the browser's profile for every campaign using it.
Why can't I pick a browser in a campaign?
Only browsers on the campaign's engine are listed. A browser's profile lives on one engine.