An agency that runs Instagram, X and LinkedIn for a dozen clients has a problem a single brand never has: many unrelated accounts, logged in by several people, all from the same office network. A social media proxy gives each client account a stable, dedicated IP address, so each client's activity stays consistent and separated from the others. This article is a working playbook for agencies: how to map accounts to IPs, how to organise the team, and how to handle credentials so that a departing freelancer does not walk out with access to everything.
One thing first. A proxy is an infrastructure tool, not a way around platform rules. Each platform has its own policies on automation, multiple accounts and third-party access. Follow them, and prefer the official agency features (business managers, page roles, delegated access) wherever a platform offers them. No proxy can promise that an account will not be restricted.
Why agencies use a social media proxy
Platforms look at many signals when an account logs in: the device, the browser, the login history and the IP address. When twenty client accounts appear from one office IP, sometimes from the same browser, the pattern looks nothing like a normal brand. Agencies typically use proxies to:
- Give each client account a consistent IP that does not change from day to day, so logins look the same every time.
- Keep clients separated, so an issue on one account is not tied to the others by a shared address.
- Log in from the client's market, for example a US IP for a US brand, when the team works from Vietnam.
- Let remote staff and freelancers work from anywhere while the account still sees the same IP.
A dedicated proxy fits this well because the IP is assigned to one customer only. Cloudj's dedicated IPv4 proxies are static ISP proxies, meaning static IPs registered to an ISP, in Vietnam, the United States, Japan, South Korea, Singapore, Hong Kong and the United Kingdom. In the United States and Vietnam you can also choose static residential ISP proxies, which are home-broadband addresses that stay the same and look like a regular user. The dedicated proxy guide explains both types.
Step 1: build an account-to-IP map
Before ordering anything, write down every client account and decide where it should "live". A simple sheet like this is enough:
| Client | Platform | Market | Proxy type | Proxy ID |
|---|---|---|---|---|
| Coffee brand | Instagram, LinkedIn | Vietnam | Static residential ISP, Vietnam | VN-01 |
| Fashion shop | Instagram, X | United States | Static residential ISP, US | US-01 |
| SaaS startup | LinkedIn, X | United Kingdom | Dedicated IPv4, UK | UK-01 |
| Restaurant group | Singapore | Dedicated IPv4, SG | SG-01 |
Rules that keep the map useful:
- One client per IP. Several platforms for the same client can share an IP, because they belong to one business anyway.
- Match the market. A Vietnamese brand logging in from Vietnam is the least surprising pattern.
- Never move an account between IPs casually. Consistency is the point.
For counting how many IPs you actually need, see how many proxies do I need.
Step 2: give every account its own browser profile
An IP alone does not separate accounts if they share cookies in one browser. Give each client a dedicated browser profile, with the matching proxy set in that profile. Some agencies use an antidetect browser to manage many profiles; using proxies with antidetect browsers covers that setup. For a smaller roster, separate Chrome or Firefox profiles work fine, as shown in proxy setup for Chrome and Firefox.
Label profiles with the same ID as the sheet (for example "US-01 Fashion shop") so nobody opens the wrong client by accident.
Step 3: decide how the team authenticates
Cloudj proxies use a username and password by default. You can instead set an IP whitelist of up to 20 addresses, which replaces password access. Each option suits a different team shape:
| Team setup | Better option | Why |
|---|---|---|
| Everyone works from one office | IP whitelist | Staff never see a proxy password; access ends when they leave the office network |
| Remote staff and freelancers | Username and password | Works from any connection; rotate the password when someone leaves |
| Mixed | Whitelist for the office, password proxies for remote clients | Keeps the sensitive accounts tied to known locations |
The detailed comparison is in whitelist vs password authentication.
Credential hygiene for agencies
Most agency incidents are not technical. They come from a shared spreadsheet of passwords, a freelancer who kept access, or a client login typed into the wrong profile. A few habits prevent most of them.
Separate the three kinds of secrets
There are three different secrets in play: the client's social account login, the proxy credentials, and your Cloudj console login. Store them separately, in a password manager with per-client vaults, and give each person only the vaults they need.
Rotate on offboarding
When a team member or freelancer leaves, rotate the proxy password from the console. The old password stops working. If you use a whitelist, remove their home IP from the list. Then change the client account passwords they had access to, following each platform's process.
Watch who views proxy credentials
In the Cloudj console, each time someone views a proxy's host, port, username and password, the view is logged and you get a notice. Keep console access to account owners and team leads; staff only need the profile that already has the proxy set.
Use platform roles instead of shared logins
Where the platform supports it, add team members as page admins or business manager users instead of sharing the client's login. It is cleaner, it is what platforms expect from agencies, and the client can remove a person themselves when needed.
Platform notes
- Instagram and Facebook: many agencies manage both through Meta's business tools. If you also run paid campaigns, the Facebook ads proxy guide covers ad account setups.
- TikTok: if your clients sell in the US, see the US TikTok proxy guide.
- LinkedIn: company pages support admin roles, so personal profiles of client executives are the main case where an agency logs in directly. Agree that arrangement with the client in writing.
- Shopee and Lazada shops: some agencies also manage marketplace stores for Vietnamese clients; the ecommerce seller proxy guide covers that workflow.
Ordering and running costs
Orders are self-service in the console and paid from your account balance, with 1 to 1,000 IPs per order and terms of 1, 3, 6 or 12 months. Larger orders get a lower price per IP. Turn on auto-renew so the same proxies keep running; letting a proxy lapse means a client account suddenly logs in from a new IP, which is exactly what you were trying to avoid. Live prices are on the proxy page, and the US and Vietnam pages show the static ISP options.
FAQ
Should every social account get its own proxy?
Every client should. Several platforms belonging to the same client can share one IP, since they represent the same business.
Dedicated IPv4 or static residential ISP for social media?
Static residential ISP addresses come from home broadband and look like a normal home user, which suits consumer-facing accounts; they are available only in the US and Vietnam. Dedicated IPv4 static ISP IPs are fast and stable and cover all seven countries.
Will a proxy stop accounts being restricted?
No. Platforms judge behaviour, content and policy compliance, not only the IP. A proxy gives you consistency and separation; following each platform's rules is still up to you.
Can I add a client later?
Yes. Place a new order for one IP in the right country and add a row to your account map.
Set up your client roster
Draft your account-to-IP map, then order the matching proxies in the Cloudj console; they are usually ready within minutes. Check current prices per IP on the pricing page before you decide how many to order.