Running several ad and affiliate accounts
Accounts separated by profile, proxies tested before an account depends on them, and one profile kept on a direct connection as a control. The fleet below is the seeded demo workspace.
What the setup looks like
Three ad profiles: two on a shared ISP proxy, one deliberately direct.
| Profile | Connection | Exit | Latency | 2FA seed | Last used |
|---|---|---|---|---|---|
| Ads-US-Main | HTTP isp-us-1.example | US | 236 ms | Stored | 1h ago |
| Ads-US-02 | HTTP isp-us-1.example | US | 236 ms | None | 4d ago |
| Ads-US-Test | Direct connection | Your own address | n/a | None | Never |
- Ad profiles
- 3
- On a direct connection
- 1 (Ads-US-Test)
- Shared ISP proxy
- isp-us-1.example, 236 ms
- Health grade
- A, because it answered under 500 ms
- Blocklist check
- 4 DNS blocklists per proxy
Simulated data. Latency and grades are the seeded check results, not live measurements.
The workflow
- 01
A profile per ad account
Each account sits in its own profile with its own device and its own cookies, so a login, a pixel or a session in one has nothing to do with the next.
- 02
A proxy you have checked, not just bought
Test a proxy before an account uses it: exit IP, country, latency, a lookup against 4 DNS blocklists and a grade from A to F. A proxy that fails keeps its row so you can retest it rather than losing it.
- 03
Keep one profile on a direct connection
Ads-US-Test runs with no proxy at all. It is the control: when something behaves oddly on a proxied profile, you have somewhere to compare it against.
- 04
Look for contradictions before you spend
Leak Check scores a profile out of 100 with a grade from A to F, and a live test reads the real navigator, timezone and WebRTC values out of the running browser. It is cheaper to find a mismatch here than after a rejection.
- 05
Hand the reporting run to a macro
Record the daily pull once and replay it across up to 10 profiles at a time, with per-profile values from a spreadsheet column, and a run console that never carries typed values or credentials.
- 06
Or drive it from your own code
Turn on the local API and start a profile with one request; it returns a DevTools endpoint you attach Puppeteer or Playwright to. It listens on 127.0.0.1 only.
Where it stops
This is the audience most often sold something impossible, so here is the plain version.
Download SoftGlaze Browser
Windows 10 and 11, 64-bit. 7-day trial, no card needed.
The download page lists the SHA-256 checksum for each release and shows what to do when Windows SmartScreen warns about the installer, which is not code-signed yet.