Use Cases
How teams use Virtual Browser across e-commerce, social, Web3, data, and QA.
1. Categories
| Area | Examples |
|---|---|
| E-commerce | Multi-store Amazon / eBay / Shopify |
| Social | Facebook, Instagram, TikTok ops |
| Web3 | Airdrops, multi-wallet, chain games |
| Data | Research, price monitoring |
| QA | Cross-profile compatibility & perf tests |
2. E-commerce
Multi-store management
- One profile per store + region-specific proxy and timezone
- Use the window synchronizer for repetitive UI tasks
- Avoid cross-store SKU edits in the same minute
Market research
- Dedicated research profiles with rotating proxies
- Track competitor price/stock/reviews on a schedule
- Keep research traffic separate from seller accounts
3. Social media
- Split personal, brand, and ad accounts across profiles
- Stagger posts and engagement; vary fingerprints per locale
- Automate scheduling via Pro API where allowed by platform policy
4. Web3
- Separate profile per wallet; never mix seed storage paths
- Airdrop tasks: social + on-chain steps in isolated sessions
- Game bots: cap concurrent clients to avoid GPU/RAM exhaustion
5. Data collection
json
{
"rate_limiting": {
"requestsPerMinute": 60,
"delayBetweenRequests": 1000,
"randomDelay": true
}
}- Rotate profiles and proxies
- Respect robots/ToS and legal limits in your region
6. Automated testing
- QA profiles mirror target OS/UA/locale
- Playwright over CDP after
launchBrowserAPI — see Automation API - Tear down test data after runs
7. Practices
- Differentiate fingerprints and proxies per profile
- Human-like timing and navigation
- Isolate data and extensions
- Backup exports before bulk changes
- Comply with platform rules and local law
