Incogniton is an anti-detect browser where each browser profile is isolated: separate cookies, cache, local storage, settings, and a dedicated fingerprint. This isolation matters when you manage multiple accounts or workflows and you can’t afford websites to link them together.
In real operations, changing the IP alone is not enough. Your network identity (IP, geo, ISP) should match the profile, and different clients or regions should never “cross”. That’s why many teams pair Incogniton with dedicated mobile proxies: 4G/5G exit IPs that work well for longer, human-like sessions.
Mobile proxies for Incogniton: why dedicated mobile proxy matters
Mobile proxies for Incogniton help you assign a separate mobile IP (4G/5G) to each profile, so platforms see a stable, believable network identity without overlaps. The rule of thumb is simple: one profile = one network story.
When you actually need it
- Freelancers and small teams managing 5–50 profiles (SMM, ads, community management, support).
- Geo-sensitive work: checking localized content or ads, regional dashboards, local pricing.
- Long sessions where yesterday’s profile should behave like yesterday (cookies + IP + timezone).
- Fraud-sensitive platforms where country/IP jumps trigger extra verification.
Dedicated vs shared pools
With shared pools, the same exit IP can be used by many customers of a provider. It may be fine for quick checks, but for consistent sessions and important accounts, a dedicated channel is easier to control, debug, and keep stable.
Incogniton as an anti-detect browser for multi-profiles
Incogniton is profile-first: you create separate “virtual browsers” and keep workflows apart with tags, groups, and permissions. The safest pattern is to assign proxies per profile, not “globally”.
A minimal isolation model for SMM
- One profile per client (or per brand/platform if needed).
- One proxy per client region, with no geo jumps.
- Client-only extensions to avoid leaking tools/settings across profiles.
How to set a proxy in Incogniton at the profile level
Assign the proxy inside the specific profile settings. This reduces mistakes and keeps the proxy attached to the profile when you share or move it within a team.
Required fields
| Field | Meaning | Common issues |
|---|---|---|
| Host / IP | Proxy server address | Extra spaces, wrong domain, mixing with exit IP |
| Port | Connection port | Using a port for a different protocol/tier |
| Username | Auth login (if required) | Wrong format, copied with extra characters |
| Password | Auth password | Copied with trailing symbols, mixed with token |
| Protocol | HTTP / HTTPS / SOCKS5 | Choosing the wrong protocol |
Step-by-step setup and quick validation
- Open Profile Management and create a new profile (or edit an existing one).
- Go to the Proxy section inside the profile.
- Fill in host/IP, port, protocol, and username/password if needed.
- Use Check Proxy to confirm you see an external IP and basic location/timezone signals.
- Save and run the profile only with its assigned proxy.
When Proxy Management is better
If you manage many proxies, store them in the proxy list/database first, test connectivity, group by country/provider, and then assign to profiles from the list. This lowers the chance of typos and speeds up scaling.
Mobile IP sessions: sticky vs rotation
Mobile proxies usually come in two modes:
- Sticky session: the IP stays for a defined time or until you reset it.
- Rotation: the IP changes automatically (time-based or on demand).
For account work in Incogniton, sticky sessions are typically safer because the profile remains consistent. Rotation can be useful for bulk checks, but you must prevent one profile from jumping across countries during the same workflow.
| Proxy type | Pros in Incogniton | Cons / risks | Best for |
|---|---|---|---|
| Mobile (4G/5G) | Strong trust signals, natural traffic, geo options | Higher cost, variable latency | Accounts, SMM, ads, long sessions |
| Residential | Many locations, flexible targeting | Often pooled, reputation less predictable | Geo checks, content review |
| Datacenter | Fast and stable bandwidth | More anti-bot / anti-fraud triggers | Technical tasks where speed matters |
Validation checklist: make sure the profile “sticks” to its proxy
Validation is not just “does the website open”. In multi-profile work, network signals must stay consistent and reproducible.
Inside Incogniton
- Check Proxy succeeds and shows an external IP.
- Geo and timezone make sense together (avoid “US IP + Eastern Europe timezone”).
- No constant challenges/captchas for normal navigation.
Technical checks (also explains broken widgets/pixels)
| Check | Why it matters | Failure symptoms |
|---|---|---|
| DNS resolution | Third-party domains must resolve via the proxy | Some domains fail, scripts don’t load |
| WebRTC leaks | Prevent exposing the real IP | Mismatch IP signals, more verification |
| IP stability | Keep IP during login/posting | Logout loops, re-verification |
| Latency/timeouts | JS/CSS resources must load in time | Empty blocks, buttons not working, missing events |
Crawlee proxy settings: “profile-level” proxy and validation
If you automate parts of the workflow (availability checks, page verification, data collection), apply the same principle: stable session + stable proxy. In Crawlee, this is typically done with ProxyConfiguration and SessionPool, where a session id helps keep the same proxy for related requests.
Safe, practical steps
- Keep your proxy URLs in project configuration and feed them into ProxyConfiguration.
- Use SessionPool and request proxies with proxyConfiguration.newUrl(session.id).
- Log proxyInfo.url in the request handler to confirm which proxy was used.
- Validate proxies before the main job: 1–2 test requests, status codes, response time, basic location sanity.
| Concept | Incogniton | Crawlee | Purpose |
|---|---|---|---|
| Identity container | Browser profile | Session (session.id) | Keep cookies/headers/proxy isolated |
| Network identity | Proxy in profile | newUrl(session.id) | One exit IP per workflow |
| Diagnostics | Check Proxy | proxyInfo.url + tests | Find broken proxies fast |
Risks and common mistakes
Wrong protocol or port
If your provider expects SOCKS5 and you set HTTP, you may get unstable sessions or partially broken loading. Ports also differ across protocols and tiers, so verify the exact combination.
One proxy for everything
It looks convenient, but profiles will overlap on the same IP and your isolation benefit shrinks. At minimum, split by client or region.
Geo/timezone mismatch
When the proxy geo and the profile timezone/language don’t match, platforms may raise risk signals. Keep geo, timezone, and locale aligned.
Why widgets and pixels break
- Third-party scripts are blocked due to geo restrictions or suspicious traffic patterns.
- Timeouts: mobile networks can add latency, heavy JS bundles fail to load.
- Third-party cookie restrictions and privacy policies prevent state tracking.
- A challenge page on one domain stops the load chain, events never fire.
IP rotation mid-action
If the exit IP changes during login or posting, platforms may require extra verification. Use sticky sessions for account work and define rotation rules with your provider.
Case: an SMM specialist splits clients by region
An SMM freelancer manages 8 clients across three countries. The goal is stable daily work: posting, replying, ad checks, and verifying how content looks in the client’s region.
- Create one Incogniton profile per client.
- Assign a dedicated mobile proxy matching the client region.
- Group and label proxies by country/provider for easier maintenance.
- Align profile timezone/language with proxy geo.
- Before sensitive actions, run a quick health check: external IP, stability, no geo jumps.
FAQ
Can I reuse the same proxy for multiple profiles?
You can, but it weakens isolation. Prefer splitting by client or region.
What should I prioritize: proxy or fingerprint?
Consistency matters most. Network signals (IP/geo/timezone) should match the profile identity and behavior.
How do I know it’s a proxy problem?
If proxy checks fail, or you see repeated timeouts and broken third-party resources with one proxy, start by validating protocol, port, auth, and provider limits.
Sources and documentation
- Incogniton Knowledge Hub: introduction, profile management, proxy management, proxy checks.
- Crawlee documentation: ProxyConfiguration, Proxy Management, SessionPool/Session Management.
- Proxy provider integration guides for Incogniton (host/port/protocol/username/password, sticky vs rotation).