Geo-Targeting & Ban Protection
Geo-targeting assigns your userbot a residential IP address from a specific country. To platform detection systems, your bot appears as a regular user browsing from that location — not an automated account running from a data center.
How Geo-Targeting Works
When you create or edit a profile, the Proxy Country setting controls which country your bot’s traffic originates from.
- Your profile is assigned a proxy session tied to the selected country
- All traffic routes through a residential IP address in that region
- The platform sees a real residential IP — indistinguishable from a normal user in that country
- The session persists for a configurable duration, so your bot maintains the same IP over time
Selecting Random lets the system pick the best available country automatically. This gives access to the widest IP pool and is the recommended default for most use cases.
Choosing a Country
Your choice depends on the community you are managing:
- Random (recommended) — Best availability and largest IP pool. Use this when geographic consistency does not matter, or when your community spans multiple regions.
- Specific country — Choose this when your community members are predominantly from one region. A bot connecting from the same country as your audience appears more natural and reduces the chance of geographic anomaly flags.
For example, if you run a community focused on Indonesian crypto traders, selecting Indonesia ensures your bot’s IP matches your members’ expected location.
What Happens When You Change Country
When you change a profile’s proxy country:
- A new proxy session is generated with a fresh IP from the new country
- The bot’s visible IP address changes immediately
- Any active connections are re-established through the new IP
- Previous session data (IP history) is not carried over
Frequent country changes can look suspicious to platform detection systems. Choose a country that fits your community and stick with it. If you need to change, do so sparingly.
Built-in Protection
Community Swarm includes several layers of protection to keep your accounts safe:
Residential IPs
All proxy traffic routes through real residential IP addresses — the same type of IPs used by regular home internet users. Unlike datacenter IPs, residential IPs are not flagged by platforms as hosting or automation infrastructure.
IP Isolation
Each profile receives its own unique proxy session. If one account is flagged or banned, other profiles on different IPs are completely unaffected. There is no shared IP between profiles.
Session Persistence
Sticky sessions keep the same IP address for a configurable duration (up to 24 hours or more, depending on your provider). This avoids the suspicious pattern of an account’s IP changing every few minutes while maintaining the same active session.
Device Fingerprinting
Each profile is assigned a unique device fingerprint that matches its geographic location. This includes appropriate language codes, system locale, and device model information — so a bot connecting from Brazil presents a device configured for Portuguese, not English.
Human-like Behavior
Configurable behavioral settings make each bot’s activity pattern appear natural:
- Typing indicators — Simulates typing before sending messages
- Reply delays — Randomized wait times between receiving and responding to messages
- Activity schedules — Define online hours and quiet periods to avoid 24/7 activity patterns
- Sticker and GIF usage — Optional media responses that mimic casual user behavior
No protection system is 100% immune to detection. Using conservative settings — realistic delays, scheduled activity windows, and stable proxy countries — significantly reduces risk. Always be mindful of platform Terms of Service.
Best Practices
- Use “Random” unless your community is geo-specific — Wider IP pool means better availability and rotation
- Avoid switching countries frequently — Pick one and commit to it for each profile
- Enable typing indicators — Small detail that makes a big difference in appearing human
- Use realistic reply delays — 2–10 second delays are more natural than instant responses
- Set up activity schedules — No real user is online 24/7; quiet hours make your bots more believable
- One profile per account — Never share proxy sessions between multiple accounts
Next Steps
- Proxies Overview — Understand proxy types and how they work
- Managing Profiles — Configure and manage your userbot accounts
- Schedules — Set up activity schedules for natural behavior patterns