Every profile can route its traffic through its own proxy. Two profiles open side by side on the same machine can appear to be in two different cities or countries, which is the whole point of running separate identities.
A proxy is a property of a profile. Assign one to your “Acme Client” profile and every browser you open under that profile sends its traffic through it; your “Personal” profile keeps its own, or none. Open ten browsers on the same proxied profile and all ten share that route.
You do not type a raw proxy URL. The dialog gives you structured fields and MetaDock assembles the rest. Choose a type:
| Type | Notes |
|---|---|
| None | Direct connection, no proxy |
| HTTP | Optional username and password |
| HTTPS | Optional username and password |
| SOCKS | No separate credentials in the dialog |
HTTP and HTTPS proxies can carry a username and password. Enter them once in the proxy dialog and MetaDock supplies them automatically whenever the proxy challenges for credentials, so you do not get a login pop-up on every page. Credential fields are shown for HTTP and HTTPS; the SOCKS option does not take separate credentials in the dialog.
Open the profile manager (Manage Profiles). Each profile row has:
Proxies are always set in the context of a specific profile.
If you reuse the same proxies across several profiles, you do not have to retype them. MetaDock keeps a saved-proxy library:
You can surface the proxy a browser is routed through right in its title bar. In the browser's title-bar identity options, turn on the proxy indicator and the title shows the proxy's host, or “Direct connection” when there is none. The profile name can ride along the same way, so a glance at the title tells you both who you are and how you are routed.
See Anti-Fingerprint for how geolocation, timezone, and locale track the proxy.