Ad Verification Mobile Proxies: See Your Ads on US Carrier Networks

An ad that looks right from the office is not the ad your audience sees. Mobile campaigns are targeted by carrier, by metro and by device, and the creative, the landing page and the tracking chain can all differ when the request arrives from a Verizon phone in Houston rather than a laptop in a data centre. Ad-verification and QA teams use a DoubleProx line to stand in that exact position: a real carrier SIM, a real US city, an address they control. This page covers why the carrier IP is the point, how to lay out lines per metro and carrier, when to rotate for fresh impressions, how to schedule checks, and what a broken result actually tells you.

The carrier IP is the test, not just the transport

Ad platforms and publishers read the requesting address to decide which creative to serve, which geo variant to show and whether to serve anything at all. A datacenter address is often served a house ad or nothing, because it does not match any buyer's audience. A carrier address behind carrier-grade NAT looks like the many real phones that share it, so the auction proceeds as it would for a customer. That makes a dedicated mobile line the only vantage point from which you can honestly say what a subscriber on that network in that city receives. The same NAT property is why reputation tools score the address as high risk, which is irrelevant to verification.

Because each DoubleProx line is one SIM in one device, you also know which carrier you are testing. An AT&T line is AT&T traffic, not a residential pool that happens to include some AT&T users. For carrier-targeted campaigns that distinction is the entire experiment. It also means the address history is yours alone, so a publisher that has learned to serve house ads to a pool address will not have done so to your modem, and the result you capture reflects the campaign rather than someone else's earlier behaviour.

Lay out lines by metro and carrier

Decide the matrix before you order. A national campaign with metro variants might want New York, Chicago, Los Angeles and Miami, one line each. A carrier-specific promotion wants the same metro on two or three carriers. Carrier geolocation is approximate, to the metro or state, which is also how most ad platforms define their geo targets, so a Chicago line will trigger Chicago-targeted campaigns without needing street-level accuracy. Run checks during the campaign's dayparting windows in the metro's local time; a creative scheduled for Central evenings will not appear at noon Eastern. We run New York, Los Angeles, Chicago, Houston, Phoenix, Miami, North Carolina and Boston.

Rotate for fresh impressions, hold to follow a funnel

Verification has two modes. Impression sampling wants many independent looks: load the page, capture the ad, rotate, load again. Each rotation re-attaches the modem to the carrier gateway and pulls another address from the regional pool, so frequency caps and retargeting tied to the previous address reset. Rotation is unlimited and on demand, which is what sampling needs. The pool is finite, so an address may repeat; log the exit IP with each capture so a repeat is visible rather than a mystery.

Funnel checks want the opposite. Click the ad, land, add to basket, reach the confirmation, and confirm every pixel and redirect fired. Hold the IP sticky for the whole path, because a change halfway through can break attribution and produce a false negative that costs an afternoon. Rotate only after the funnel is complete and recorded, then start the next pass with a clean profile if you want to see the first-visit experience again.

How many checks per line, and how to schedule them

A single line handles a steady stream of page loads comfortably at 20-45 Mbps on 4G or 50+ Mbps on 5G, and unlimited data means a screenshot-heavy job never hits an allowance. The constraint is realism, not bandwidth. A real phone does not load the same publisher page every second, and some publishers rate-limit an address that does. Space captures out, vary the pages in a run, and use separate lines for parallel metros rather than hammering one. Keep browser profiles per device class you care about, since the ad server reads the user agent as well as the IP, and store each capture with its exit IP, carrier, metro and timestamp. That record is the deliverable.

Reading a failed check

No ad at all usually means the address fell outside the target or the daypart, not that the line is broken. Confirm the exit IP's metro on two geolocation lookups and the local time, then rotate and retry. The wrong creative points at a targeting rule or an outdated asset. A landing page in desktop layout means your profile's user agent is not mobile; the IP is doing its part. Pixels that fire from a laptop but not through the line often reveal a script a mobile browser blocks or a mixed-content error, which is the kind of finding the job exists for. If the line will not answer an IP-echo request, check credentials and port, then contact support with the line ID.

Record every anomaly with the exit IP, carrier, metro, time and a screenshot, and separate the three causes cleanly in your report: targeting configuration, creative or landing-page defects, and network or tooling faults. Only the last category is ours to fix. A verification line documents what your own ads do; it is not a tool for clicking competitors' ads or generating traffic, which advertising platforms prohibit. To set up your matrix, review plans on the DoubleProx homepage and pick metros on the USA locations page.

Setting up a Ad verification proxy on DoubleProx

1. Order one DoubleProx line per metro and carrier combination you need to verify.
2. Copy each line's host, port, username and password from the dashboard.
3. Set them in a mobile-emulating browser profile, your verification tool's proxy field, or a test phone's Wi-Fi proxy settings.
4. Confirm exit IP, carrier and metro on an IP-echo page, then hold sticky through funnel checks and rotate between impression samples.

Ad verification proxy questions