Social BrowserProfiles, AI & automation

Proxy integrations

Use the proxy provider you already trust.

Assign a different proxy to each Social Browser Profile. Keep provider credentials, location, session mode, and rotation policy under your control — without being locked to one vendor.

8 proxy partnersPer-Profile assignmentHTTP / HTTPS / SOCKSBring your own provider

Proxy partners

Choose a provider or bring your own.

These are current proxy partners enabled in the Social Browser partner directory. Provider services, pricing, IP pools, and policies are operated by the providers themselves.

Partner

WebShare

Use WebShare-issued proxy endpoints and credentials with individual Social Browser Profiles.

Proxy infrastructurePer-Profile setup
PartnerPromo: social_browser

Proxy.luxe

Dedicated residential and ISP proxy options that can be assigned to individual Social Browser Profiles.

ResidentialISP
PartnerPromo: SOCIAL

Proxied

Mobile proxy endpoints backed by carrier networks, with provider-side rotation controls.

4G/5G mobileRotation controls
PartnerPromo: SOCIALBROWSER

PSBProxy

Mobile and residential proxy options with rotating or sticky session modes.

MobileResidentialHTTP(S) / SOCKS5
PartnerPromo: SOCIALBROWSER

TradeProxy

A proxy marketplace where purchased endpoints can be assigned to Social Browser Profiles.

Proxy marketplaceResidential / mobile
PartnerPromo: Thor20d

ThorData

Residential, mobile, ISP and datacenter proxy endpoints with rotating and sticky session options.

ResidentialMobileISPDatacenter
Partner

Proxy001

Residential, static residential and datacenter endpoints configured at the Profile level.

ResidentialStatic residentialDatacenter
Partner

ZooProxy

Residential and static ISP endpoints with provider-side geo and session controls.

ResidentialStatic ISP

Partner disclosure: some external provider links are referral or sponsored links. Social Browser may receive a commission when you use them. This does not determine technical compatibility, and you can use any supported third-party proxy provider.

Complete setup guide

From provider endpoint to verified Profile.

You normally need four values from your proxy provider: protocol, host, port, and authentication. Keep any session or location parameters exactly as the provider generated them.

  1. 1

    Choose the target Profile

    Open the Profile that should use the proxy. Configure proxies per Profile instead of treating them as a browser-wide setting.

  2. 2

    Copy the provider endpoint

    Get the host, port, username, password, and protocol from the provider dashboard. If the username contains country, city, session, or sticky-ID parameters, keep them unchanged.

  3. 3

    Add it in Proxy Manager

    Open Proxy Manager, select HTTP/HTTPS or SOCKS as required, enter the endpoint and credentials, then save it to the selected Profile.

  4. 4

    Launch and verify

    Open the Profile and confirm the public IP, location, DNS behavior, and WebRTC behavior before using the Profile for important work.

Connection formats

Know what to copy from the provider.

Provider dashboards use different labels, but the underlying values are usually the same.

H

Host + port

Typical endpoint fields:

proxy.example.com 8000
A

Authentication

Enter credentials in their dedicated fields:

username password
P

Protocol

Select the protocol supported by the endpoint.

HTTPHTTPSSOCKS4SOCKS5
Do not rewrite provider usernames.Many providers encode country, city, ASN, session ID, or sticky-session duration inside the username. Changing that string can change routing or break authentication.

Verification

Test the Profile before account-sensitive work.

A successful connection is not enough. Confirm that routing and browser network behavior match what you intended.

Troubleshooting

Fast checks when a proxy does not connect.

Authentication failed

Re-copy the username and password from the provider dashboard. Do not remove geo/session suffixes from the username. Confirm the provider allows username/password authentication for that endpoint.

Connection times out

Check the host and port, confirm the proxy is active, verify your firewall or network is not blocking the destination port, and try the protocol listed by the provider.

The IP or country is not what I selected

Review the provider-side location configuration and session parameters. Rotating pools can change IPs by request or time depending on the provider plan.

The proxy works in one Profile but not another

Compare protocol, credentials, and endpoint values Profile-by-Profile. Each Profile keeps its own proxy configuration, so fixing one Profile does not automatically change another.

Ready to configure

One Profile. One routing decision.

Add the provider endpoint to the Profile that needs it, verify the result, and keep the rest of your Profiles independent.