15% off your first purchase with code WELCOME15, up to 25 GB.

See pricing

Ad verification · Mobile ad verification

Mobile ad verification on carrier networks

Mobile ad verification checks what a campaign actually serves to people on a mobile carrier network: the creative, the placement and the landing page. Line items targeted at wireless carriers do not serve to Wi-Fi or home broadband, so a check needs a carrier IP in the market, and ARC Mobile provides one in four countries.

Pay per GB · No subscription · Prices in EUR, excl. VAT

Illustration. The URLs and values are fictional; the connection string is the real grammar.
€2.00
per GB on ARC Fast, excl. VAT
−44%
at 1 TB (€1.12 / GB)
185+
countries, city targeting
Never
expires — no subscription

Written for

  • Mobile ad operations teams
  • App marketers
  • Programmatic campaign managers
  • Ad quality and brand safety analysts

The short answer

  • Carrier-targeted buys only serve on cellular connections. In Display & Video 360, for example, wireless carrier targeting includes only cellular data connections, not Wi-Fi, so a residential or office check cannot see them.
  • ARC Mobile exits on genuine 4G/5G carrier IPs in Germany, the UK, the US and Japan only, with no city targeting and sticky sessions of 5 to 60 minutes.
  • The proxy supplies the network. Device signals, such as user agent, viewport and touch support, are yours to set; in-app inventory needs a real device or emulator, not just an IP.
  • Mobile carriers use carrier-grade NAT, so many subscribers can share one public IP. Do not infer audience or frequency from carrier IPs.

The problem

What goes wrong without the right IPs

Carrier-targeted line items never reach your check

A line item targeted at a wireless carrier serves only to cellular connections. Check it from an office, a residential line or a phone on Wi-Fi and it does not appear, so the report says 'not found' for an ad that is running.

A desktop browser on a carrier IP is not a phone

Ad servers decide on device as well as network. A carrier IP with a desktop user agent gets desktop inventory. Emulate the device properly, or the check verifies a combination no real user has.

No city in the mobile pool

ARC Mobile targets by country only. A campaign geo-fenced to one city cannot be verified at city level on carrier IPs; you can verify the carrier dimension nationally and the city dimension on residential exits, as two separate checks.

Sessions end

A mobile sticky session holds for 5 to 60 minutes, and an exit can drop earlier. A long verification script that assumes one IP for an hour should expect to restart.

Rendered mobile pages are heavy

A mobile page with creatives, video pre-roll and trackers can run to several megabytes. Mobile bandwidth costs more per GB than residential, so check frequency is the lever that matters.

What to collect

What you can collect

Exit country and carrier ASN
Which market and which carrier network served the check. Look up the exit IP's ASN and store it with the result, since you choose the country, not the carrier.
Device profile used
User agent, viewport, pixel ratio and touch support. Without it you cannot reproduce or dispute a result.
Creative ID and screenshot
What actually rendered in the slot, captured as evidence. Compare against the approved creative.
Placement and surrounding content
The page and the content next to the ad, for brand safety. A correct creative in the wrong context is still a problem.
Click-through URL and landing page
Where the ad leads on mobile, resolved without clicking the ad. Mobile landing pages and app store redirects differ from desktop ones.
Seller declarations
For programmatic buys, the publisher's ads.txt or app-ads.txt entries, to check the seller in the bid path is authorised.
Timestamp and session ID
Pairs the check with your ad server's logs and tells you whether a run spanned more than one exit.

How it runs

How a collection run works

  1. 01

    List carrier-targeted line items per country

    From the media plan, take the placements and line items that target carriers or mobile devices in DE, GB, US or JP. Anything outside those four countries needs a different method.

  2. 02

    Generate mobile endpoints in the dashboard

    ARC Mobile connection strings are generated for you in the dashboard per country, as sticky or rotating, rather than composed by hand. Store them as secrets and read them in your script.

  3. 03

    Load the placement with a real mobile device profile

    Use a browser automation tool with a mobile device descriptor so user agent, viewport and touch match a phone, and route it through the carrier endpoint.

    Playwright with a mobile profile on an ARC Mobile endpoint
    import osfrom urllib.parse import urlsplitfrom playwright.sync_api import sync_playwright# Copied from the dashboard: one ARC Mobile endpoint per country, as a URLp = urlsplit(os.environ["ARC_MOBILE_DE"])  # http://user:pass@host:portwith sync_playwright() as pw:    browser = pw.chromium.launch(proxy={        "server": f"http://{p.hostname}:{p.port}",        "username": p.username, "password": p.password,    })    ctx = browser.new_context(**pw.devices["Pixel 7"], locale="de-DE")    page = ctx.new_page()    page.goto("https://publisher.example.de/article", wait_until="networkidle")    page.screenshot(path="placement-de.png", full_page=True)    browser.close()
  4. 04

    Capture, then resolve the click-through without clicking

    Store the screenshot, creative ID and surrounding content. Read the ad's click-through URL from the page and resolve it hop by hop, as in affiliate link monitoring, instead of tapping the ad.

  5. 05

    Pair with a residential check for the city dimension

    Where a campaign is also geo-fenced to a city, run a second check on ARC Fast with city targeting. Report the two as separate dimensions rather than claiming one check proved both.

Setup

Recommended setup

The pool is dictated by the buy: carrier-targeted inventory needs carrier IPs, everything else is cheaper on residential.

PlanRoleSessionTargetingPrice
ARC Mobile
Mobile 4G/5G
For carrier-targeted and mobile-network inventory
Genuine 4G/5G carrier IPs, the only way to see line items targeted at cellular connections. Endpoints are generated in the dashboard. No city targeting.
Sticky 5–60 minutes per checkCountry only: DE, GB, US, JP
€3.50 / GB
€3.15 at 1 TB (−10%)
ARC Fast
Rotating residential
For mobile-web inventory not targeted by carrier, and for city checks
Residential exits with a mobile device profile cover mobile inventory that is targeted by device and geo rather than by carrier, at a lower price per GB, and they take the city token ARC Mobile lacks.
Sticky, 10 minutes per checkCountry + city
€2.00 / GB
€1.12 at 1 TB (−44%)

Prices are list prices in EUR, excl. VAT. Volume discounts apply automatically at checkout — full ladder on the pricing page.

Connect

One connection string per market

The country, city and sticky session are tokens in the username. Change the token, change the market; keep the session handle, keep the IP.

sticky · Germany · 10 min
http://USERNAME_pool-arcfast_country-de_session-k3f9a1x2_sesstime-10:PASSWORD@proxy.arcproxies.io:8000

Swap _country-de for any market you quote. The full grammar is on the residential proxies page.

Illustration

What carrier checks in four markets costs

An illustration with round numbers — your pages, payloads and retry rate will differ. The arithmetic is the real price ladder.

Assumptions

Placements
120
Markets
4 (DE, GB, US, JP)
Checks per placement per day
3
Weight per rendered mobile check
2 MB with creatives
Period
30 days
Bandwidth per month
≈ 87 GB

On ARC Mobile

€286.23per month, excl. VAT

87 GB bought in one purchase at €3.29 / GB (−6% volume rung, applied automatically).

The same 87 GB on ARC Fast: €128.76 at €1.48 / GB. Move down as soon as the cheaper pool holds up.

Move every placement that is not carrier-targeted to ARC Fast with a mobile device profile, and keep ARC Mobile for the line items only a carrier IP can see. See mobile proxies for the plan's limits.

Bandwidth never expires, so a bigger single purchase is only ever cheaper per GB. See the ladder.

In depth

Mobile ad verification, in depth

Why carrier IPs matter for mobile ad verification

Programmatic platforms let buyers target by connection as well as by device and location. In Google's Display & Video 360, the Carrier & ISP targeting option distinguishes the two explicitly: wireless carrier targeting includes only cellular data connections and not Wi-Fi, while ISP targeting covers Wi-Fi and wired connections based on the public IP the provider assigns.

For verification this is decisive. A check run from a residential line, an office or a phone on Wi-Fi is, by that definition, not on a carrier, so carrier-targeted line items will not serve to it. A mobile proxy on a carrier network is the way to request the page from the network the buy targets.

What ARC Mobile can and cannot do

CapabilityARC MobileARC Fast (residential)
Network typeGenuine 4G/5G carrier IPsResidential broadband IPs
CountriesGermany, UK, US, Japan185+
City targetingNoYes, published metro list
Sticky sessions5 to 60 minutesSet in minutes, best effort; dashboard offers 1 minute to 24 hours
Choosing a specific carrierNo; record the ASN per checkNot applicable
Connection stringsGenerated in the dashboardComposed from the username grammar
Price per GBHigher than ARC FastLower; see pricing

If your media plan targets carriers outside those four countries, or a single city on a carrier network, ARC Mobile cannot verify it and we would rather say so than sell you bandwidth that will not help.

Carrier-grade NAT: what a shared carrier IP means

Mobile carriers commonly put subscribers behind carrier-grade NAT. RFC 6598 reserved the 100.64.0.0/10 address block in 2012 specifically for the links between carrier-grade NAT devices and customer equipment. The result is that many subscribers can share one public IP at the same time.

Two practical consequences for verification. First, a carrier IP is not a user: do not infer reach, frequency or uniqueness from how many checks came from one address. Second, sticky sessions on ARC Mobile last at most 60 minutes and an exit can change before that, so treat a changed IP mid-check as normal and restart the check.

Mobile web vs in-app: what a proxy can verify

  • Mobile web placements. A browser with a mobile device profile on a carrier exit sees what a phone on that carrier sees. This is the case ARC Mobile covers directly.
  • In-app placements. Ads in apps are requested by the app's SDK, with device identifiers and app context. A proxy can supply the carrier network to a test device or emulator, but the IP alone does not reproduce an in-app request.
  • Seller authorisation. For programmatic buys, check the publisher's ads.txt (web) or app-ads.txt (apps), the IAB Tech Lab standards for publicly declaring which companies are authorised to sell their inventory.
  • Landing pages and app store redirects. Resolve the click-through URL on the same carrier exit without tapping the ad; mobile chains often differ from desktop ones.

Never tap or click the ads you verify. Generated clicks or impressions are invalid traffic and breach our acceptable use policy. The ad verification page covers desktop and residential checks.

Works with anything that takes a proxy URL

  • Playwright
  • Puppeteer
  • Selenium
  • Python requests / httpx
  • Docker

FAQ

Questions

Something not covered? Write to contact@arcproxies.io.

Why do I need a mobile carrier IP to verify mobile ads?

Because line items targeted at wireless carriers serve only on cellular connections. In Display & Video 360, for example, carrier targeting includes only cellular data connections and not Wi-Fi. A check from an office, a home line or a phone on Wi-Fi will not see those ads.

Which countries can I verify mobile ads in?

ARC Mobile exits on genuine 4G/5G carrier IPs in Germany, the UK, the US and Japan. It has no city targeting, so mobile checks run at country level. For other countries, or for city-level checks, use ARC Fast with a mobile device profile and accept that it is not a carrier network.

How long can a mobile proxy session last?

Sticky sessions on ARC Mobile run from 5 to 60 minutes. The carrier can still reassign an exit earlier, so verification scripts should treat a changed IP as normal and restart the check rather than fail.

Can I choose which mobile carrier I exit on?

No. You choose the country and the endpoint is generated in the dashboard. Look up the exit IP's ASN at the start of each check and store it with the result, so you know which carrier network served the ad.

Can a mobile proxy verify in-app ads?

Only in part. In-app ads are requested by the app's SDK with device and app context, so you need a real device or emulator. A mobile proxy can supply the carrier network to that device, but an IP alone does not reproduce an in-app ad request.

How much bandwidth does mobile ad verification use?

A rendered mobile page with creatives is commonly one to three megabytes. Checking 120 placements in four countries three times a day at 2 MB comes to about 86 GB a month. Keep only carrier-targeted checks on ARC Mobile; the rest are cheaper on ARC Fast.

Sources & review

Last reviewed by the ARC Proxies team. Prices are read from the live catalog at build time.

  1. [1]Google Display & Video 360 Help: Carrier & ISP targeting
  2. [2]IETF: RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space
  3. [3]IAB Tech Lab: ads.txt and app-ads.txt

Get started

Buy a gigabyte and try it on your own targets.

No subscription, no sales call. Code WELCOME15 takes 15% off your first purchase, and whatever you do not use is still there next quarter.