Evomi is one of the cheapest reputable ways into residential proxies — $0.49/GB on the 100GB plan, $0.99/GB pay-as-you-go (verified on evomi.com/pricing; re-check before you buy) — which makes it a natural fit for survey work, where bandwidth needs are tiny. This guide walks through the full setup: Evomi dashboard to working BeastBrowser profile, no steps skipped.

Everything here works the same way with other providers too — Floppydata, Decodo, IPRoyal, and the rest all use the same credential-and-session model, just with different dashboards. If you're already on another provider, follow along and translate the dashboard clicks.

What you need before starting

  • An Evomi account with an active residential proxy plan (the pay-as-you-go tier is fine for testing — 15GB minimum).
  • BeastBrowser installed (the free plan is enough to learn this).
  • Five quiet minutes.

Step 1 — Get your proxy credentials

Log into the Evomi dashboard and open the residential proxy section. You'll find three things: the endpoint hostname (Evomi documents this as rp.evomi.com for residential), the port, and your username and password. Copy all three into a note — you'll need them in a minute.

Evomi uses username/password authentication — no IP allowlist to maintain, which is convenient if you work from different machines or networks.

Step 2 — Build your targeted proxy string

Here's where Evomi's model is elegant: targeting and session control are appended to the password, so switching country or holding an IP is a string change, not an endpoint change.

A basic credential looks like: username your-username, password your-password. To target a country and hold a sticky session, you extend the password with parameters — Evomi's docs show the format for country targeting (e.g. US) and session keys. The pattern is:

  • Country targeting: append the country parameter so exits come from the country your survey profile claims.
  • City targeting: append the city parameter for city-level precision — this is what makes your IP city match your profile city (why this matters).
  • Sticky session: append a unique session ID per profile (e.g. session-survey-emma-01). Same session string = same IP for the session duration. Different string per profile = different IP per profile.

Check Evomi's current documentation for the exact parameter names — they document this clearly, and it occasionally gets refined. Don't guess the format; copy it from their docs.

Step 3 — Add it to a BeastBrowser profile

In BeastBrowser, open the profile you want to equip (one profile per survey account — see the structure guide). Go to the profile's proxy settings, select HTTP/HTTPS or SOCKS5 (Evomi supports both; SOCKS5 is the common pick), and paste in:

  • Host: the endpoint hostname
  • Port: the port from your dashboard
  • Username: your Evomi username
  • Password: your full built string from Step 2 (password + targeting + session)

Set the profile's timezone and locale to match the proxy's city — US proxy means America/New_York or Chicago timezone and en-US locale. This two-minute step is what separates working setups from rejected ones.

Step 4 — Verify everything

Launch the profile and run the checks:

  • Open an IP geolocation checker — confirm the city matches what you targeted.
  • Confirm the IP is residential (ASN lookup should show a consumer ISP, not a datacenter).
  • Wait 10–15 minutes, check the IP again — same IP means your sticky session is holding (sticky vs rotating).
  • Confirm the browser timezone matches the IP city.

Step 5 — Repeat per profile (the right way)

Each additional survey profile gets its own session string (new IP) and its own city targeting. Don't clone a profile's proxy config to another profile — that's how two accounts end up sharing one IP, which is exactly what the detection layers are built to catch. New profile = new session string = new IP. Every time.

Troubleshooting

Connection refused: re-check the endpoint and port from the dashboard — copy/paste errors are the #1 cause. Wrong city: verify the city parameter format against Evomi's docs; a malformed parameter is silently ignored and you get a random exit. IP changing mid-survey: your session string isn't being honored — confirm the sticky parameter syntax. Site still flags you: re-read the VPN detection guide — the usual culprit is a timezone or locale mismatch, not the proxy itself.

Evomi offers a free trial on its core products and a 30-day money-back guarantee on plans — use the trial to validate the whole flow before committing bandwidth money.

Stuck on a step? Describe exactly where it breaks (which step, what error) in the comments — "it doesn't work" isn't debuggable, but step numbers are.