LinkedIn Proxy Setup: How to Configure Proxies for Outreach Tools

The One Thing That Matters More Than Settings: Proxy Type

Before getting into configuration, the most important decision is proxy type — because no configuration of the wrong proxy type will save an account. LinkedIn maintains lists of known datacenter IP ranges (AWS, Azure, Google Cloud, DigitalOcean, Vultr, and dozens of others) and treats traffic from them as suspicious. It doesn't matter how well you've configured the proxy if the IP is on one of those ranges. The account will get flagged, usually within hours of first activity.

The three proxy types and their viability for LinkedIn:

• Residential proxies — the only viable type. Internet connections routed through real home ISPs (Comcast, BT, Orange, etc.). LinkedIn sees them as normal user traffic because they are normal user traffic. These are what you need.
• Datacenter proxies — don't use them. Hosted on servers in data centers. LinkedIn detects them automatically. Even premium datacenter providers with 'clean' IPs get flagged quickly because the ASN (the network identifier) belongs to a hosting provider, not a residential ISP.
• Mobile proxies — work but expensive. Traffic routed through real mobile devices on cellular networks. Very effective, very expensive ($50+/mo per IP), unnecessary for most operators. Residential is the right tier for LinkedIn outreach.

What to Look for in a Residential Proxy

Not all 'residential proxies' are actually residential. The market has cheap providers who label datacenter IPs as residential, and semi-legitimate providers who use residential IPs but share them across hundreds of customers. Both cause problems. Four things to check before trusting a proxy provider:

• Dedicated, not shared. A shared residential IP has dozens or hundreds of other users' LinkedIn activity on it. LinkedIn tracks behavior patterns across IPs; a shared IP accumulates flags from every operator using it. Dedicated means the IP is yours alone for the duration of your subscription. Shared IPs are cheap for a reason.
• Sticky session, not rotating. Sticky session means the same IP persists across your logins. Rotating session means the IP changes every request or every few minutes. For LinkedIn, a rotating IP looks like the account is logging in from a different location every session, which is a classic account-takeover signal. Always use sticky session for LinkedIn.
• Country-matched to the account. A US LinkedIn account should use a US residential proxy. A UK account should use a UK proxy. A mismatch — US account on a German IP — is a coherence failure that flags the account regardless of proxy quality.
• Verify the ASN before committing. You can check any IP's ASN (the network it belongs to) at tools like ipinfo.io. A legitimate residential IP will show an ISP name (Comcast, Verizon, Deutsche Telekom). A mislabeled datacenter IP will show a hosting provider (DigitalOcean, OVH, Hetzner). Do this spot-check on any proxy provider before deploying accounts through them.

Proxy Setup in Linked Helper

Linked Helper is a Chrome extension-based tool, which means it runs inside a browser on your machine rather than on a cloud server. This changes how proxy configuration works — the proxy needs to be configured at the browser or system level, not inside Linked Helper itself.

The correct approach with Linked Helper and an anti-detect browser:

• Step 1 — Don't use Linked Helper's built-in proxy field for residential proxies. Linked Helper has a proxy field in its settings, but it works at the application level and doesn't properly isolate browser fingerprint signals the way a dedicated browser profile does. For real account isolation, configure the proxy at the browser-profile level instead.
• Step 2 — Create a separate anti-detect browser profile for each account. In AdsPower, Multilogin, or GoLogin, create one profile per LinkedIn account. Assign that account's dedicated residential proxy to the profile (host, port, username, password). For the full per-profile setup, see our anti-detect browser setup guide.
• Step 3 — Open Linked Helper inside that profile's browser window. Launch the profile in your anti-detect browser — it opens its own isolated Chromium-based browser window, not your system Chrome. Install and run Linked Helper inside that window. All traffic from that window, including Linked Helper's requests, routes through the profile's configured proxy.
• Step 4 — One profile, one account, one proxy. Never run two LinkedIn accounts in the same browser profile, even if they have different proxies configured. The fingerprint is shared at the profile level.
• Important note on Linked Helper at scale: Linked Helper requires the browser to stay open and your machine to be running for campaigns to continue. This is manageable for 1-3 accounts; it becomes operationally difficult past 5. For multi-account operations at scale, cloud-based tools handle this better. See the scaling guide for when to make the switch.

Proxy Setup in HeyReach

HeyReach is a cloud-based tool, which means campaigns run on HeyReach's servers rather than your machine. This makes proxy configuration simpler — you configure it directly inside the HeyReach account settings, and the tool handles the rest.

HeyReach proxy configuration:

• Step 1 — Navigate to the LinkedIn account settings in HeyReach. Under each connected LinkedIn account, there's a proxy configuration field.
• Step 2 — Enter your dedicated residential proxy details. Format is typically host:port with separate username and password fields. Use the exact credentials from your proxy provider.
• Step 3 — Set the proxy type to HTTP or SOCKS5 based on your provider. Most residential proxy providers support both; HTTP is more common and works fine for LinkedIn.
• Step 4 — Test the connection before running campaigns. HeyReach has a proxy test function — use it to confirm the proxy is connecting and the IP shows as residential. If it fails, the most common cause is entering the credentials in the wrong format.
• Step 5 — One proxy per account, no sharing. If you have 10 accounts in HeyReach, each needs its own dedicated residential proxy. Don't reuse the same proxy across accounts.

Proxy Setup in Expandi, Lemlist, La Growth Machine, and Other Cloud Tools

Most cloud-based outreach tools follow the same pattern as HeyReach: each connected LinkedIn account has a proxy field in its settings, you enter the dedicated residential proxy details, and the tool routes that account's traffic through it. The specifics vary slightly by tool:

• Expandi: proxy configuration is per LinkedIn account under account settings. Supports HTTP and SOCKS5. Same one-proxy-per-account rule applies.
• Lemlist: proxy configuration is in the LinkedIn sender settings. Lemlist also has its own residential proxy network you can use instead of bringing your own — a reasonable option if you don't want to manage proxies separately.
• La Growth Machine: proxy configuration per identity (LinkedIn + email pair). LGM has its own proxy infrastructure but also accepts external proxies.
• Skylead / Dripify: both support per-account proxy configuration in the account settings. Standard HTTP/SOCKS5 format.
• General rule across all cloud tools: if the tool supports per-account proxy configuration, use it and assign a dedicated residential proxy to each account. If the tool doesn't support proxy configuration (rare), the tool is routing all accounts through its shared server infrastructure — which may be fine (if the tool has good infrastructure) or a risk depending on how many other users share it.

The Proxy Mistakes That Still Get Accounts Flagged

Having a proxy configured doesn't mean it's working correctly. The mistakes that cause accounts to get flagged despite proxy setup:

• Using a shared proxy. The most common mistake. The IP looks residential but is shared across many users whose behavior accumulates flags. LinkedIn sees a single IP with hundreds of different account logins per day and treats it as a suspicious aggregation point. Dedicated residential IPs only.
• Rotating session instead of sticky. If the IP rotates between logins, every login to the same account comes from a different IP. LinkedIn reads this as the account being accessed from constantly changing locations, which is a classic stolen-account pattern.
• Buying from providers that label datacenter IPs as residential. Cheap 'residential' proxies under $2-3/mo per IP are almost never actually residential. Spot-check the ASN before deploying.
• Not matching country. A German-region account on a US proxy. Even if the proxy is genuinely residential, the inconsistency with the account's stated location is a flag.
• Logging into the account outside its assigned proxy. Checking the account from your personal laptop 'just once' adds an off-proxy login to the account's history. Every login should go through the account's assigned proxy.
• Sharing a proxy across the anti-detect browser and the cloud tool. If you're using both an anti-detect browser (for manual access) and a cloud tool (for campaigns), confirm they're using the same proxy for that account — not two different proxies, which creates an inconsistent IP history.

How Much Should a Good LinkedIn Proxy Cost?

Dedicated residential proxies from reputable providers run $5-15/mo per IP. That's the legitimate market rate. Anything significantly cheaper is almost certainly shared, mislabeled datacenter, or both. Anything significantly more expensive (outside mobile proxies) usually isn't worth the premium for LinkedIn outreach.

At 10 accounts, you're looking at $50-150/mo in proxy costs if you source them separately. This is why many operators use account providers that bundle the proxy with the account — NextGen Profiles includes a dedicated residential proxy per account in the flat $59/mo, which removes the separate proxy line item and the management overhead of sourcing proxies per account.

For the full cost-of-ownership picture including proxies, tooling, and accounts, see the capacity-planning section of our scaling guide.