Use cases · 15 workflows

Proxies for every proper job.

Fifteen workflows we see most often. Each has a recommended proxy type, a real customer pattern, and a quick path from $4 to production. Pick the one that fits.

Business

10 use cases

High-volume B2B workflows - what teams use proxies for at production scale. Residential is the recommended type for almost all of these.

Residential

Web Scraping

Extract any data from sites that block datacenter traffic. Rotating residential, 98%+ success across top-1k domains.

Most popular
Residential

SERP Scraping

City-targeted Google & Bing rank tracking. Each city returns its own ranking - agencies pull 50+ cities daily.

SEO agencies
Residential

Price Monitoring

Track competitor pricing across markets. Same product on Amazon US vs UK vs DE = different prices. Local IPs reveal the truth.

E-commerce
Residential

Ad Verification

Spot-check that ad creatives display correctly across DSPs in every target region. Catch fraud and misplacement early.

Ad ops
Mobile

Social Media Management

Run 20+ client accounts safely. Each gets a dedicated mobile IP in the right city. Platforms expect mobile traffic.

Agencies
Residential

Email Protection

Shield your inbox-tooling and verification flows with secure routed traffic. Avoid sender-IP correlation issues.

Marketing
Residential

Brand Protection

Monitor unauthorized usage from a local-user perspective. Catch affiliate creative violations & counterfeit ad placements.

Legal & brand
Residential

Market Research

Automated competitor intelligence - product pages, changelogs, support docs. Replaces 20+ hours of manual analyst work / week.

Strategy / PM
Residential

Lead Generation

Directory and listing sites block repeat scrapers and cap pages per IP, capping your data pull. Collect public business data from directories and listings: rotate residential IPs to gather at volume without tripping limits.

Sales & growth
Residential

Travel Fares

Airlines and OTAs quote different fares by location and device, and aggressively block aggregators. Pull fares and availability across origin markets: country-matched residential IPs get the real local quote, not a blocked or default price.

Travel · OTAs

Web scraping is the most popular workflow we see.

Real customer pattern: 500K+ requests/day at 98%+ success, $300/month for 100 GB. The full guide walks through code examples, common pitfalls, and the right setup recipe.

Quick decision

Residential or Mobile?

Every card above has a recommendation pill - but here's the rule of thumb if you want to pick before clicking in.

Pick Residential

For ~80% of B2B workflows.

From $2.25/GB at scale · from $4 starter

  • Web scraping & SERP - most volume sits here
  • Price & ad monitoring - geo-targeted across markets
  • Privacy & geo-access - streaming, regional sites
  • Gaming - most game-store access works fine
Pick Mobile

For the hardest targets only.

From $4.25/GB at scale · from $6 starter

  • Social media management - IG, TikTok, FB account ops
  • Sneaker reselling - Nike SNKRS, Adidas Confirmed
  • Ticket reselling - Ticketmaster, StubHub, AXS
  • Retail drops - multi-account checkout flows

How to pick a use case.

Every workflow has a recommended proxy type and a typical bandwidth range. The 15 use cases here split into three groups by buyer intent - Business for production B2B work, Privacy & Access for personal/corporate connectivity, Consumer & Niche for high-demand purchase flows.

You don't have to pick just one. A single SimplyNode account can run web scraping (residential), price monitoring (residential, geo-targeted), and social media management (mobile) side by side - same balance, same dashboard, same auth string with different parameters per workflow.

Bandwidth scales with volume per workflow. A scraping team typically uses 100-500 GB/month; a social agency managing 30 mobile-IP accounts might use ~50 GB/month; a one-person SEO consultant maybe 5-10 GB. Pick by what you actually need - pricing slides with volume regardless of how you split it.

FAQ · Use cases

Common questions about picking a use case.

Yes. One SimplyNode account, one shared GB balance - split however you want across use cases. Different parameters in the password field route to the right pool (residential vs mobile, which country, etc.). Most customers run 2-4 use cases in parallel from the same dashboard.

The 15 cover what we see most, but proxies are general-purpose - anything that needs an HTTP / HTTPS / SOCKS5 connection through a different IP works. Email support@simplynode.io with your workflow and we'll recommend a setup (proxy type, country, session strategy).

No - pricing is per GB, not per use case. Residential is one rate ($2.25-$4/GB by volume), mobile is another ($4.25-$6/GB). Choose your use case → that picks your proxy type → that picks the rate. No surcharges for "premium" workflows like Amazon or Instagram.

Rough guide from our customer base: web scraping 100-500 GB/mo, SERP tracking 20-100 GB/mo, price monitoring 50-200 GB/mo, social management 30-80 GB/mo (mobile), sneaker drops 5-20 GB/mo (mobile, bursty). Start with 1 GB ($4), see how far it goes.

Sometimes yes. An e-commerce price-tracking pipeline might use residential for 95% of targets (Amazon, Walmart, Target) and mobile for the harder edge cases. You can mix freely - switch via the password parameter, same script, same balance.

Test your use case for $4.

1 GB buys you about 6,700 product page loads or 2,000 SERP results. Pick the closest match above, hit the page, copy the setup recipe.