Which Node4 Proxy for Amazon Seller, Ad and Social Accounts
Amazon Seller Central and other store logins, ad accounts, social tools and scraping, each matched to the Node4 product that fits and why.
For Amazon Seller Central, other store backends and long-lived seller logins, use Residential when the platform scores the type of address, and Dedicated when it accepts datacenter addresses and you need one address that stays the same for days. For ad verification, social monitoring, price monitoring and scraping, use the datacenter products: Shared or Dedicated for a fixed address, Rotating Datacenter or Rotating Unmetered when the work needs many exits. The table matches each job to a product; the sections after it give the reasons that change the choice.
| Job | Product | Why | Starts at |
|---|---|---|---|
| Amazon Seller Central or another store backend login | Residential, or Dedicated where the platform accepts datacenter addresses | Residential arrives from a consumer ISP address; Dedicated keeps one address across days | $7.47/month for 3 GB ($2.49/GB) |
| Ad account management | Dedicated | One customer per address and the same address at every login | $7.45 a month for 5 proxies |
| Ad verification | Rotating Datacenter | Country targeting in the username and a different exit per connection, billed by the gigabyte | $5.90/month for 10 GB ($0.59/GB) |
| Social media scheduling or monitoring | Shared for public pages, Dedicated for logged-in accounts | A fixed address per account; shared tenancy is fine where nothing is logged in | $5.00 a month for 25 proxies |
| Price monitoring and scraping | Rotating Datacenter | Requests spread across the pool, so no single address carries the whole rate | $5.90/month for 10 GB ($0.59/GB) |
| Large unattended crawl | Rotating Unmetered | No byte meter; priced by concurrent connections | $29.00/month for 250 connections ($0.116 per connection) |
| Local results checks by city | Residential | Country and city targeting in the username | $7.47/month for 3 GB ($2.49/GB) |
These are Node4's standard prices for the plan sizes named. If you have not yet measured whether your target cares about address type at all, choosing the right proxy type gives the test procedure; this page assumes you know the job.
The five products in one line each
- Dedicated (Premium Datacenter): static datacenter address, one customer at a time, no bandwidth meter, billed per proxy per month, HTTP(S) and SOCKS5.
- Shared: static datacenter address shared with other customers, metered by traffic, HTTP(S) and SOCKS5. The free tier is a small Shared plan over HTTP(S) only; SOCKS5 and the gateways need a paid plan.
- Rotating Datacenter: gateway at
gw-rotating_datacenter.node4.io, datacenter exits in the US, Italy and Spain, billed per gigabyte. - Rotating Unmetered: the same gateway pool at
gw-rotating_unmetered.node4.io, no byte meter, priced by concurrent connections. - Residential: gateway at
gw-residential.node4.io, exits from a partner network of consumer connections, country and city targeting, billed per gigabyte.
The two rotating products draw the same addresses and differ only in the meter; metered bandwidth versus no meter works out which costs less for a given volume. Understanding proxy types explains the axes behind the list, and dedicated vs shared datacenter proxies compares the two static products in full.
Datacenter addresses and account platforms
Marketplaces, payment providers and ad platforms often buy IP-intelligence data, and those risk scorers can classify a datacenter address as higher risk for store, seller and payment logins. Every Node4 product except Residential is a datacenter product, and an IP checker will report its addresses as hosting. That report is accurate, and no setting changes it.
What that means in practice depends on the platform. Some accept a datacenter login as long as the address is steady and unshared; some add verification steps; some refuse it. Node4 cannot tell you in advance which one your platform does, and nobody can promise how a platform will judge an account. Run one account on the smallest plan of the product you are considering, watch it through a few logins and a payout cycle, then scale.
Residential fits the store and seller login job when the platform weighs address type, because its exits are consumer ISP addresses. The trade-off is in the next section: a residential exit does not stay the same across days. Node4 does not sell a static residential product.
Address history is the other concern. A Dedicated address carries only your traffic while you hold it, but Node4 cannot vouch for what any address did before it reached you. Check each new address with your own checker before attaching an account to it. A Premium Datacenter plan with a monthly replacement allowance can swap an address that fails your check, and automating IP replacement covers doing that from the dashboard or the API.
Rotation and long sessions
The gateways choose an exit per connection: each new CONNECT tunnel or SOCKS5 connection can leave from a different address. A session id in the username pins one exit for up to 30 minutes on Rotating Datacenter and Rotating Unmetered. On Residential the pin is best effort with a 30-minute ceiling, and a dropped exit needs a new session id. Sticky vs rotating sessions covers the syntax.
So a profile reopened tomorrow through a gateway leaves from a different address, in the same country or city if you targeted one. For scraping and monitoring that is the point. For an account you warm up and keep, frequent address changes can themselves look unusual to the platform, which is why the rotating products belong on collection jobs and not on account logins.
Dedicated is the only product that keeps one address across days. It changes when you replace it, or when Node4 replaces an address that has failed its health checks, and the proxy.replaced webhook reports both. At renewal, an unpaid plan holds the same IPs for 14 days; after that the plan pauses and the IPs are released, and paying later brings fresh ones. Subscription management has the full sequence.
One address per account
Give each account its own address and keep it there. When several accounts share an exit, a platform that links accounts by address sees them as related, and a problem on one can reach the others. With Dedicated that is one proxy per account; with Residential it is one targeted session per account, accepting that the address moves within the targeted location.
A proxy only changes the address. Cookies, browser fingerprints, payment details and login habits are separate signals, and keeping them apart is the browser profile's job, not the proxy's. An anti-detect browser gives each profile its own storage and fingerprint, and each profile then gets its own proxy fields.
Setting it up in an anti-detect browser
Once you know the product, the browser needs four values per profile: type, host, port and login. Step-by-step pages cover AdsPower, BitBrowser and Hubstudio, including the bulk import format each one accepts and what to check when a profile's proxy test fails.
When you have picked a product, the residential proxies page and the datacenter proxies page describe each in more depth, and country and city targeting shows how to pin a residential location.