A Flat-Rate Carrier Line or Residential Data by the Gigabyte: Which Does a Marketing Team Need?

Two kinds of US proxy are on offer to a marketing or QA team outside the United States, and they look alike in a sales deck: both give a US address, both say the address is real. One is a dedicated carrier line, a single SIM in a single device in a US metro, rented by the day, week or month with unlimited data, which is what Stateside Proxies sells. The other is residential proxy data, gigabytes spent through a pool of other people's home connections, with a different home on every request or a few minutes on one. They differ in what an ad platform sees, in whether a session stays one visitor, in what the bill looks like as screenshots and video pile up, and in which checks each is good for. This page compares them plainly and says when the gigabyte pool is the right answer.

What each one is

A Stateside line is a carrier SIM from AT&T, T-Mobile or Verizon inside a modem, router or phone we own in one of eight US metros, used by one customer for the plan's length. Its address belongs to the carrier, is shared with the carrier's real subscribers, reads as cellular, sits in the metro or its state, and changes only when you rotate it. Data is unlimited for a flat price.

A residential pool is a set of home broadband connections whose owners have agreed to share them, gathered by a vendor and sold by the gigabyte. Each request may exit from a different home, or one home may be held for a few minutes. The address reads as residential, sits wherever that home is, and is shared with the vendor's other customers.

What an ad platform sees

Ad platforms classify traffic by connection type and buy inventory by device. A carrier line is mobile inventory in the metro: campaigns bought for mobile, for the metro or for the state are served to it as to any subscriber. A residential exit is desktop or home inventory in whichever city the home is, which suits campaigns bought for desktop and does not suit campaigns bought for mobile. For verifying a mobile campaign, the line is the only one of the two that will show the ads.

There is a second effect worth knowing. Ad platforms also apply frequency caps per user, and they identify a user partly by address. A line holds one address, so the cap behaves as it does for one real reader and the team sees the real frequency. A pool presents a new home every few minutes, so the cap never engages and the team sees more impressions than any real reader would, which distorts the report.

Side by side

The table sets out the facts that decide the choice for a marketing or QA team.

Consistency over a session

QA passes and verification sessions take time. A line holds one address for the whole session, so the site sees one visitor from first page to checkout, frequency caps behave as they do for a real person, and retargeting sequences can be walked from trigger to banner. A pool presents a new home every few minutes at most, which breaks long sessions, confuses frequency caps and makes retargeting impossible to follow. For a one-touch check of a page, the pool's churn is irrelevant; for anything longer it is the problem.

QA teams feel the same thing in a different place: a consent banner accepted on page one should stay accepted on page nine, and a shipping estimate quoted in the cart should still be there at checkout. Both depend on the site seeing one visitor, which the line provides and the pool does not.

What the bill looks like

Verification and QA move more data than people expect: full-page screenshots, video ads played to the end, session recordings, media-heavy pages. On a pool every megabyte is billed, and a week of video ad verification can cost more than a month of a flat-rate line. A Stateside line costs the same whether it moves a few megabytes or a terabyte: $65 a month for 4G, $74 for 5G. For light, broad sampling across many cities, a few gigabytes of pool data costs less than lines in each city would.

When the pool is the honest answer

Sampling prices or pages across many US cities, one visit each. Checks that need a residential rather than a cellular classification, such as a desktop-only campaign. Cities outside our eight metros. Light volume spread over many addresses. We sell pool data by the gigabyte in the same dashboard, and we will say so when it is the better buy.

When the line is the honest answer

Verifying a mobile campaign. Any QA pass or verification session that must look like one visitor from start to finish. Walking a retargeting sequence. Video and media-heavy checks, where volume would make a pool expensive. Any check where the metro and the carrier must be known and fixed. For a marketing or QA team outside the United States, that is most of the work, and a Stateside line at $5 a day is built for it.

Questions about per-GB pricing