A tracker answers one question extremely well: which campaign, source, landing page and offer combination actually made money. Binom answers it at a scale most trackers do not attempt, with a flat licence price regardless of click volume and up to 260 million clicks per day per server on the self-hosted v2 tier.
But a tracker can only measure the traffic that reaches it, and it can only test what your network lets it reach. That is where a mobile proxy network fits into a Binom stack. This article covers five concrete places where the two products touch, with the exact configuration for each, and one section on what this combination does not fix.
Why a tracker and a proxy network belong in the same stack
Binom already treats network identity as a first-class signal. Its campaign rules engine can route on Country, Continent, City, State, Region, ISP, Connection type, IP, IP version, User agent and Reverse DNS (PTR), and it ships dedicated criteria for Proxy/VPN (“Checks if the click uses Proxy or VPN”), Datacenter (“Associated with well-known hosters”) and Company. Binom Protect, the standalone bot filter, goes further and screens for bots, VPNs, proxies, antidetect browsers, click farms, spy services, moderators, checkers and crawlers.
Read those two facts together and the implication is direct: Binom is built to tell datacenter and VPN traffic apart from real users. Anything you do on the operational side of your media buying, from logging into ad accounts to QA-ing your own funnel, is going to be classified by that same logic. If your operational traffic comes from a datacenter IP, Binom will correctly treat it as datacenter traffic, and so will the ad platforms.
PROXIES.SX supplies the other half: real 4G/5G mobile carrier IPs across 100+ countries, so that operational traffic carries a genuine mobile network identity rather than a hosting-provider one.
Use case 1: Adding Facebook ad accounts to Binom with a mobile proxy
This is the most literal connection point between the two products, because Binom’s own documentation asks for it.
Why Binom asks for a proxy here
Binom v2’s Facebook integration syncs campaign costs through the Facebook Marketing API. To connect an account you supply an access token, and the Binom docs state plainly:
“You need to get the Access token and (preferably) a mobile proxy to add the Facebook account to the tracker.”
The reason is that the API calls originate from your Binom server. A self-hosted Binom instance lives on a VPS or dedicated box, which means its IP belongs to a hosting ASN. Repeated Marketing API traffic from a hosting IP that has no history with the account is exactly the pattern Facebook’s automated review treats as suspicious. Binom therefore exposes a per-account proxy field so the integration can egress from an IP that looks like the one the account normally uses.
The exact format
Binom’s proxy field accepts a full URL. Its own documentation gives this example shape:
socks5://u20981:zNdq5A@22.45.70.37:13050
With PROXIES.SX you have two ways to fill it, and the right choice depends on how long-lived the account is.
Dedicated port, for one account you intend to keep
A dedicated port pins one modem to a fixed host and port with its own login. The host, port and credentials do not change, which is what you want behind a Facebook account that represents a stable identity.
socks5://proxyLogin:proxyPassword@serverIp:socksPort
Pool Gateway, when accounts span several countries
One credential reaches every country in your tier, and you select the country inside the username.
socks5://psx_<userId>-peer-us:proxyPassword@gw.proxies.sx:7001
One port rule decides whether this works. On the Pool Gateway, port 7000 is HTTP-only and port 7001 is SOCKS5-only. Because Binom’s field expects a socks5:// URL, it must point at 7001. Sending a SOCKS5 scheme to the HTTP port is the single most common setup mistake, and it fails in a way that looks like a credential problem rather than a port problem.
Match the proxy to the account, not to your office
Pick the country of the proxy to match the country the ad account was created and warmed in. A US account that suddenly transacts through a German exit is a bigger signal than no proxy at all. If you run accounts across several markets, use one endpoint per market rather than one shared endpoint for everything.
Use case 2: QA your geo routing from inside the target country
Binom gives you geo tokens such as {country}, {city}, {isp}, {region} and {state}, and campaign rules that split paths on any of them. A typical setup sends Tier 1 traffic to one landing page, LATAM to another, and everything unmatched to a default path.
The failure mode is quiet. A misconfigured rule, a stale GEO database, or a rule ordering mistake does not throw an error. It just routes a slice of your traffic to the wrong landing page, and you find out from the numbers a week later.
Testing this properly means generating a click that Binom genuinely sees as originating in the target country. Opening the link from your desk with a browser locale switch does not do that, because Binom resolves geo from the IP. Sending the click through a mobile exit in the target country does.
A five-minute routing test
- Pick the countries your campaign has rules for.
- For each one, request your campaign URL through a PROXIES.SX exit in that country.
- Open the Binom clicklog and confirm the recorded country, region and ISP are what you expected.
- Confirm the click landed on the path the rule intended, not the default path.
- Repeat for the default path with a country you have no rule for.
Binom’s changelog notes an “Improved GEO database updating logic” in release 2.32.00, so this test is also the fastest way to confirm your instance’s geo data is current after an update.
Use case 3: Do not let Binom Protect flag your own tests as bots
Binom Protect is a paid add-on that filters bots, VPNs, proxies, datacenter ranges, TOR exit nodes, antidetect browsers, click farms, spy services and ad-network moderators. Its basic detection methods run without an extra redirect, at roughly 1 to 3 milliseconds.
This creates a subtle trap for anyone QA-ing their own funnel. If you test your campaign through a datacenter proxy or a commercial VPN, Binom Protect is doing its job when it classifies that click as filtered traffic. Your test then produces one of two misleading outcomes: either the click is filtered and you conclude the funnel is broken, or it is counted and quietly pollutes the campaign’s stats with a click that no real user made.
A mobile carrier IP behaves like the traffic Binom Protect is designed to let through, because it is the same class of network real users are on. That gives you a test click that travels the real path and is judged by the real rules.
Two practical notes:
- Use a separate campaign or a dedicated test path for QA where you can, so even legitimate test clicks stay out of your production numbers.
- Binom also supports an &is_bot=1 test parameter and mark-as-bot rules. Use those to exercise the bot branch deliberately, rather than trying to trigger it by accident with a dirty IP.
Use case 4: One endpoint per ad account for multi-account buying
Binom supports an unlimited number of users on every pricing tier, with Superadmin, Admin and User roles, per-element read and write permissions, per-user API keys and a “Hide profit” option. That makes it a natural fit for teams running many accounts, and for agencies running accounts on behalf of clients.
The tracker side of that scales cleanly. The account side is where teams get into trouble, because ad platforms link accounts by network graph. Two accounts that share an exit IP are two accounts the platform can associate, no matter how well separated they are inside your tracker.
The mapping that holds up is one persistent mobile endpoint per account identity, kept stable for the life of that account. PROXIES.SX does not charge per endpoint, so the number of endpoints is not the cost driver; the bandwidth is. That means the isolation model you actually want is not the one you have to ration.
How the two sides line up
| Layer | What it does | What it costs |
| Binom | Attribution, reporting, routing rules, bot filtering, team permissions | Flat licence, independent of click volume |
| PROXIES.SX | Carrier network identity per account and per test session | Per GB, endpoints free |
Use case 5: See the offer page the way a local user sees it
Binom stores landing pages inside the tracker and rotates them through Smart Rotation, with modes covering paths, landing pages and offers. It records what happened. It does not tell you what the offer page looked like to a user in Brazil at the moment the click landed.
That gap matters most on offers you do not control. Advertiser pages change prices by region, redirect differently by carrier, geo-block without warning, and sometimes serve a broken localisation that converts at zero. From a single office IP, all of that is invisible.
Requesting the offer page through a mobile exit in each target country before you scale spend is a five-minute check that catches:
- Currency and price shown to a local user, including regional dynamic pricing.
- Redirect chains that differ by carrier or by country.
- Geo-blocks and soft blocks that return a page rather than an error.
- Localisation that is technically present but visibly wrong.
A practical setup checklist
- Install Binom v2 on a server that meets its requirements: Ubuntu 22.04 or 24.04 under KVM, at least 4GB RAM, 2 cores and 50GB of disk. HDD is not supported. Binom installs it for free if you ask.
- Start the trial before you buy. Binom’s FAQ describes a 14-day trial with no traffic or feature limits, extendable to 30 days on request or with a coupon. Note that the v2 plan card advertises 30 days directly, so confirm which applies to you.
- Create one PROXIES.SX endpoint per ad account identity, in the country that account belongs to.
- Add each Facebook account to Binom with its access token and its matching socks5:// endpoint on port 7001.
- Build your campaign rules, then run the five-minute routing test above for every country you wrote a rule for.
- Keep a separate QA path so test clicks never mix into production reporting.
- Before scaling spend, pull the offer page through an exit in each target country.
What this combination does not solve
Being straight about the limits is more useful than overselling the fit.
- A proxy is not an account-quality strategy. Clean IPs do not rescue accounts that are warmed badly, run aggressive creatives, or share a payment method across a whole farm. Network identity is one input among several.
- Binom Protect and a proxy network solve opposite problems. Protect filters incoming traffic you did not want. A proxy shapes outgoing traffic you did want. Neither substitutes for the other, and buying one does not reduce the need for the other.
- Self-hosted means self-operated. The Binom licence does not include the server. Budget hosting separately, or take Binom Cloud at $299 and hand the operations back to them.
- Geo QA is a sample, not a guarantee. Testing three countries from three exits tells you those three routes work at that moment. It does not certify the advertiser will not change the page tomorrow.
FAQ
Does Binom require a proxy to work?
No. Binom runs fine without one. A proxy becomes relevant in specific places: the Facebook integration, where Binom’s own docs recommend a mobile proxy, and any QA work where the IP your test originates from changes the result.
Should the proxy be mobile, residential or datacenter?
For adding ad accounts to the tracker, Binom’s documentation specifically says mobile. For geo QA, mobile or residential both work, and the decisive factor is that Binom’s own rules engine and Binom Protect both classify datacenter ranges separately, so a datacenter IP will not reproduce what a real user experiences.
Does routing Binom through a proxy slow the tracker down?
The proxy sits on the Facebook API integration and on your QA sessions, not on the redirect path your real traffic takes. Click processing is unaffected, because visitor clicks reach your Binom server directly.
How many endpoints do I need?
One per account identity you want kept separate, plus one per country you QA in. Since PROXIES.SX charges for bandwidth and not for endpoints, the count is a design decision rather than a budget decision.
Can I use the same endpoint for the tracker integration and for browsing the ad account?
Yes, and for a single long-lived identity that is the preferable setup, because both kinds of traffic then share one consistent network history. Use a dedicated port rather than a rotating gateway entry for that case.
About PROXIES.SX. Real 4G/5G mobile and residential exits across 100+ countries, billed per GB with no per-endpoint or monthly fees, and GB that do not expire. Pricing starts at $4/GB and drops to $2.40/GB at volume. More at proxies.sx, and our full Binom review is at proxies.sx/partners/trackers/binom.