Proxies for Facebook Ads

A separate IP for each ad account

When a specialist switches between clients' ad accounts from one address and one browser, their sessions get mixed together. Assign each client its own connection in “Sticky session” mode and always use that same port for them. The session duration is configurable up to 120 minutes, which covers a working session.

The client's country

If the client is based in Poland or Germany, it makes sense to open their account from an IP in that country, just as the business owner does. Precise geo lets you pick a city or carrier; traffic with it counts ×2.

Antidetect browser profiles

A proxy only covers the network side. To give each ad account its own cookies, history and browser fingerprint, create a separate profile in an antidetect browser and add the proxy to it. See the step-by-step guides for AdsPower and Dolphin Anty.

Residential or mobile

Residential addresses are home internet connections and the best fit for daily work in ad accounts. Mobile ones cost more; use them if the client usually manages the business page from a phone. Datacenter addresses aren't a good fit for ad accounts.

Platform rules

A proxy doesn't exempt you from Meta's advertising and business account rules. Access clients' accounts through roles and invitations in Business Manager, and ramp up a new ad account gradually instead of jumping to a large budget on day one.

How Facebook sees links between accounts

Meta looks at more than the IP. It sees cookies and browser data, the devices used to log into a personal profile, the phone number and email, the payment method for ads, and connections inside Business Manager: who granted access to whom, and which pages and pixels are shared. If two clients' ad accounts open in one browser with the same cookies, a separate address won't fix that.

For an agency, the working setup looks like this: a separate antidetect profile for each client, a separate proxy port in that profile, and access to the client's assets through roles in Business Manager. Each client then has its own network, its own cookies and its own login history, and the business owner can see who worked with their assets and when.

Agency setup step by step

1. Create a residential proxy plan. With many clients, a separate plan per client is handy: its own username and password, its own balance, its own traffic limit and separate usage stats that are easy to show in a report.
2. In the generator choose the client's country and the “Sticky session” mode. Set the session duration to 60–120 minutes so the address doesn't change while you're working on campaigns.
3. Download the lines in your antidetect browser's format. Port 10000 is client A, 10001 is client B, and so on; record this mapping in a team spreadsheet.
4. Create a profile for each client and add the proxy. Step-by-step guides are available for Octo Browser, GoLogin and Multilogin, as well as AdsPower and Dolphin Anty mentioned above.
5. Open the IP check in each profile: the country should match the client, and WebRTC shouldn't reveal your office address.
6. Turn on two-factor authentication on staff members' personal profiles that give access to Business Manager.

When the session expires, the port gets a new address in the same country, and a residential IP can change earlier if the device goes offline. For normal work that's not a problem: business owners also log in from home one day and from a phone the next. What matters is that the country and the browser profile stay the same.

What not to do in ad accounts

• Don't open different clients' ad accounts in one browser profile, even with different proxies.
• Don't switch one profile between countries during the day, such as Poland in the morning and the USA in the evening.
• Don't run a VPN on top of the proxy: the site will see the VPN address, not the country you chose.
• Don't use datacenter proxies: server addresses aren't a good fit for ad accounts.
• Don't launch a new ad account with a large budget and a dozen campaigns on day one; scale up gradually.

Another common situation is a bank page for payment confirmation that won't open through the proxy. Some sites are closed for all customers: banks, payment systems and government services. The full list is on the blocked sites page.

To be honest about the limits: there's no guarantee against bans. The pool is shared, so another customer may have used an address before you. If Meta asks for verification right after login, turn on the anonymity filter in the pool settings, which drops IPs already flagged as proxy or VPN, and take another port in the same country.

Tasks, proxy type and rough traffic

Residential proxies cost $1.59 per GB, mobile ones $2.50. Traffic is counted both ways, and Ads Manager is heavy because of charts and video previews. Set a daily or weekly limit on each plan so a mistake in one profile can't eat the whole balance, and turn on email or Telegram alerts. Traffic never expires, so unused volume carries over to next month, and you can move gigabytes between plans of the same type.

Countries for client campaigns

The address should match the country the business owner usually works from. For Ukrainian clients use Ukraine proxies, for Polish and German ones Poland and Germany, and for campaigns in English-speaking markets the USA, the United Kingdom or Canada. There are 195 countries available, and choosing a country costs nothing extra.

Precise geo (city, region or carrier) is useful when the business is local and you want to check how ads appear in, say, Warsaw or Munich. Traffic with precise geo counts ×2, so for everyday work in an ad account the country is enough.

To check the ads themselves, keep a separate clean profile that isn't logged into any work account. Open the client's landing page there through an address in the target country and check the language, currency, prices and lead form before the campaign budget is spent on a mistake.

Team work and access

When an agency has several media buyers, don't send everyone one proxy username. A separate plan per client gives its own credentials, and if a project is on hold you can pause the plan without deleting its settings. For an office with a fixed address, the IP whitelist is convenient: up to five addresses per plan, and no username or password is needed in the proxy line.

One plan handles up to 1,000 concurrent connections, enough for the whole team to work with ad accounts in parallel. If your advertising software supports SOCKS5, use the same ports 10000–20000: they work with both HTTP and SOCKS5. Mobile addresses are in the mobile proxies section.