Налаштування проксі у Multilogin

What goes into the profile proxy form

Multilogin asks for five fields and nothing else. Residential targeting rides inside the login, so you never need a separate endpoint per country:

Multilogin lets you save the proxy at the profile level or reuse a saved entry across profiles. Save it per profile: shared entries are how two accounts end up on one address by accident.

One session id per profile, forever

The number after _s_ is what ties a profile to an address. Give every profile its own and never reuse one, because two profiles on the same id share an address and that link is the cheapest signal a platform can compute:

Login strings for a fleet

profile_01  ->  login_c_US_s_1_ttl_1h
profile_02  ->  login_c_US_s_2_ttl_1h
profile_03  ->  login_c_GB_s_3_ttl_1h
profile_04  ->  login_c_DE_s_4_ttl_1h

# static address instead of residential:
# host = the IP from your dashboard, port 50100, no suffixes

• One hour is the longest sticky lifetime we offer, and a residential device can drop earlier. For accounts that must never see an address change, buy an ISP address instead and put it in the same form.
• Match the profile timezone, locale and language to the proxy country. An account on a German address reporting a Warsaw timezone contradicts itself.
• Check the address inside the profile before the first login, not from your own browser. What matters is what the profile sees.
• Keep a note of which session id belongs to which profile. Rebuilding that mapping after a crash is painful and mistakes cost accounts.

What gets accounts linked