Multi-account: a clean mobile IP per session
When several accounts share the same IP address, the platform links them within minutes. A dedicated mobile IP per account puts a network boundary back between sessions that must stay independent.
What platforms look at first
Correlation by IP address is the simplest and most widely used signal. Two accounts connecting from the same address at the same time are, to an anti-fraud system, the same person until proven otherwise. Datacenter ranges are additionally scored as high risk: a business account connecting from a server triggers extra verification.
A French mobile address reduces both signals: it is shared by nature between thousands of subscribers, and it belongs to a carrier rather than a host. Used one address per account, it removes direct correlation.
Shared or dedicated for multi-account?
Multi-account work needs stability. A rotation every ten minutes makes the same account appear with a new address mid-session, which is at best suspicious and at worst blocking. You need an IP that stays put for the length of the session, and rotation you trigger yourself.
- Shared plans: useful for testing, not for holding long sessions.
- Dedicated phone at $79: one line, one stable address, rotation on demand and 256 simultaneous streams. This is the recommended configuration.
- Agency pack at $339: five dedicated phones, so five independent addresses, with business invoicing and priority support.
Isolating cleanly with SOCKS5
The simplest approach is to run every session in its own network context, for example with one environment variable per profile: export https_proxy="socks5h://USER:PASSWORD@proxy.proxymobile.fr:28081".
In a browser, use one user profile per account and configure the SOCKS5 proxy in the network settings of that profile. The socks5h scheme matters: it makes the mobile line resolve DNS, which avoids local resolution leaks.
Beyond the IP: other factors
Let us be honest about what a proxy does and does not do. It isolates the network layer. It does not replace good practice: a distinct browser per account, partitioned cookies, normal activity rhythms and coherent payment methods. A proxy alone does not make mass account creation credible, and that practice, contrary to platform terms, is not covered by our terms of service.
A clear usage framework
Our service is for professionals who legitimately manage several accounts: agencies with multiple clients, e-commerce operators with several shops, marketing teams with one account per brand. It is not for circumventing suspensions or mass-creating accounts. The agency plans page details the cases we cover and the contact page answers architecture questions.
Questions fréquentes
Is one different IP per account enough?
No, it is necessary but not sufficient. Platforms also look at browser fingerprint, cookies, behaviour and payment methods. The mobile IP is the network brick: it stops two accounts being tied together by the same address.
How long does an IP stay stable?
On shared plans automatic rotation changes the IP every 5 to 20 minutes, which does not suit long sessions. For multi-account work the dedicated plan with on-demand rotation is the right option: you keep the same IP for as long as you need.
Is this allowed?
Managing several accounts you legitimately own, such as several shops or several agency clients, is routine. Creating accounts in violation of a platform terms, impersonating someone or evading a suspension is not acceptable, and we suspend those uses.
Can I separate sessions per client with one subscription?
Proxy credentials are generated per subscription. To strictly isolate clients, the cleanest route is one dedicated subscription per client, which is what the agency pack with five phones provides.
One dedicated line per client, no commitment
The agency pack at $339 provides five dedicated phones. Start with a trial at $1.49 or ask for a walkthrough of the Pro plans.