Sauce Labs Mobile Proxies for US Geo QA in Cloud Device Tests

Sauce Labs runs automated and manual tests on cloud browsers and real devices, and QA teams depend on it for coverage. Its infrastructure lives in datacenters, so anything that keys on the visitor's location, geo-redirects, consent banners, currency, availability, ads, is tested from the wrong place. Pointing a Sauce Labs session at a Stateside Proxies line makes the test browser or device exit from a US carrier address in a chosen state, so those checks are run as a real US phone user would experience them. This page explains how to set it up.

What a datacenter test session gets wrong

Geo logic reads the exit address. A datacenter address is placed wherever the facility is, may be classified as hosting and served generic pages or CAPTCHAs, and never receives mobile-targeted ads. Compatibility and layout tests do not care; geo, consent, currency, availability and advertising tests do. A US carrier exit fixes that set.

The usual symptom is a US launch that passes every cloud test and then shows the wrong cookie banner to a real American visitor.

Choosing a US data centre in Sauce Labs does not solve this. A session in the US West region exits in the United States but still from a datacenter, which passes a country check and fails any test depending on a state or a mobile connection. It is worth saying plainly, because a stakeholder who reads US in the job settings may assume the geo work is covered.

Who combines the two

QA teams whose automated suites include geo-dependent checks for US launches. Localisation testers verifying US page versions across browsers and devices. Compliance teams checking consent banners by state. Agencies running client acceptance tests as US visitors. Each is the team's own site, tested through the team's own line.

Put the state in the job name so results can be read at a glance, and keep the exit address check, the job link and the app build number together in the record. Devices in the public real device pool are cleaned between sessions, so a test cannot rely on anything saved by an earlier job.

Why a carrier line

A carrier address in the chosen state is a US mobile subscriber, so geo logic, consent rules and ad targeting treat the test session as a real US phone user. The address holds steady through a run, keeping results consistent across a suite.

Real devices in Sauce Labs are routed the same way as browsers, so an app under test can be exercised on an actual US-market handset model while exiting from a US carrier address, which is as close to a US user's experience as a cloud lab gets. As with any suite, keep the line for the geo-dependent subset and run the rest on the default connection, so the geo results stand out in the history.

Setting up the check

Rent a line in a metro in the targeted state. In Sauce Labs, configure the session's proxy capabilities or the tunnel to use the line's HTTP proxy with its username and password, and set the browser's time zone and locale to the metro where the platform allows. Run the geo-dependent tests and capture screenshots and videos. Repeat from another state after a free move.

A mobile connection is slower than the one most suites were tuned on, so raise page load timeouts and Sauce's own command and idle limits for the geo jobs, otherwise slow pages get reported as failures. Do not rotate the line during a run: consent, cookies and any server-side bucketing can change mid-suite, and the resulting failures look random. On supported desktop browsers, Sauce's extended debugging option captures the session's network traffic, and the job video shows exactly when a banner appeared.

Staying within terms

Test your own properties and those you are engaged to test. The line changes the exit address and nothing about your permissions.

Setting up a Sauce Labs proxy on Stateside Proxies

1. Rent a line in a metro in the state you target.
2. In Sauce Labs, set the session's proxy capabilities or tunnel to the line's host, HTTP port, username and password.
3. Set the browser's time zone and locale to the metro where the platform allows.
4. Run the geo-dependent tests and capture screenshots and videos.
5. Move the line to another state, free, and repeat.

Sauce Labs proxy questions