Ad verification with mobile proxies

What to check in placements, redirects and landing pages, and how to run checks through mobile carrier IPs.

By DINPROXY Team · · 4 min read

On this page

An ad that looks right from your office can look different on a phone in another country. Ad verification means checking ads the way real users see them, and for mobile campaigns that means a mobile connection in the right market. This guide covers what to check and how to set it up with DINPROXY Mobile Proxies.

Why ad checks need a local mobile view

Campaigns are often targeted by country, language, device and network, so the ad a person sees depends on where they are and how they connect. A check from a desktop on an office network shows only one of those combinations.

The path after a click can vary as well. A click may pass through several redirects before the landing page, and visitors from different markets may be sent to different places. To confirm what a phone user in Germany sees, your check has to come from a phone-like client on a German connection.

Proxies give you that connection without people or devices in every market. Your scripts and browsers stay where they are, while the exit IP sits in the country you choose.

How mobile carrier IPs help

Mobile Proxies send your requests through IP addresses of mobile carriers, so the publisher sites and ad servers you check see traffic from a mobile network. Many people share each mobile IP, so sites treat them gently.

You choose the market by country, and the dashboard's Select Location list shows the countries available. The IP decides the location and the network; your client decides the device and the language. Pair each mobile IP with a phone profile: a mobile User-Agent, a phone-sized screen and the market's language.

When a check needs a specific state or city, use Rotating Residential Proxies, which also target by state and city. Residential proxies are also the ones to use for streaming, payment, banking, government, ticketing, LinkedIn and webmail pages.

What to check

A useful check covers the whole journey, from the page where the ad appears to the page it leads to.

  • Placement: the ad shows up in the expected slot on the expected pages, with the creative meant for that market.
  • Landing page: the click ends on the intended page, and that page loads on a phone with the right offer, currency and contact details.
  • Redirects: each hop in the click chain goes to the expected domain. Record the status code and address of every hop, and the final URL.
  • Geo and language: the creative, the redirect target and the landing page all match the country you test from, and the text is in the market's language.
  • Variation: repeat the check from several IPs in the same country to see what different users get.

Keep the evidence. A screenshot of the placement and the list of redirect hops make it easy to compare markets over time and to share findings with a partner.

Set up DINPROXY Mobile Proxies

Mobile Proxies use the host proxy.dinproxy.com on port 7779, over HTTP, HTTPS or SOCKS5. Write the proxy as http:// or socks5h://, and sign in with a proxy user from Tools → Users, or connect from a whitelisted server IP without a password. Mobile traffic is billed per GB from its own balance and never expires.

Your choices go at the end of the username: @country= with a two-letter country code, plus @session= and @time= for a sticky session of up to 120 minutes (10 if you leave time out). Pick the session type per task:

TaskSessionUsername
Sample what many users in a market seeRotatingUSERNAME@country=de
Follow one click from the ad to the landing pageStickyUSERNAME@country=de@session=click1@time=10
Load and screenshot a full page in a browserStickyUSERNAME@country=de@session=page1@time=10

A browser opens several connections for one page, and each HTTPS connection keeps its own IP. A sticky session puts all of them on one IP, as a real visit would be. Use a new session ID for the next check to get a new IP. The IP can also change sooner if it becomes unavailable or after 60 seconds without requests.

In Mobile Proxies → Connection setup, the dashboard writes these usernames for you. Pick a country, choose Sticky Session, set a quantity of up to 500 and click Generate Preview. Each endpoint gets its own session ID, so each one is a separate mobile IP for a separate check. To test on a real iPhone, choose the QR code (Shadowrocket) format and scan the code in Shadowrocket to add the proxy.

Run the checks from code

In every example, replace USERNAME and PASSWORD with your proxy user, using the full connection username such as 1024~myuser. Start by confirming the exit: https://ipinfo.io/json shows the IP and location the site sees.

curl --proxy 'http://proxy.dinproxy.com:7779' \  --proxy-user 'USERNAME@country=de:PASSWORD' \  'https://ipinfo.io/json'

Next, load the publisher page in a headless browser with a phone profile and save a full-page screenshot for the placement check. This example uses Playwright, which takes the proxy user and password as separate fields.

// npm install playwright && npx playwright install chromiumimport { chromium, devices } from "playwright";
const proxy = {  server: "http://proxy.dinproxy.com:7779",  username: "USERNAME@country=de@session=page1@time=10",  password: "PASSWORD",};const browser = await chromium.launch({ proxy });const context = await browser.newContext({ ...devices["iPhone 13"], locale: "de-DE" });const page = await context.newPage();await page.goto("https://publisher.example.com/");await page.screenshot({ path: "de.png", fullPage: true });await browser.close();

Then follow a click URL hop by hop with a mobile User-Agent and the market's language. Replace MOBILE_USER_AGENT with the User-Agent of the phone you want to match. Both versions print every hop, so you can compare the chain across markets.

from urllib.parse import quoteimport requests
user = quote("USERNAME@country=de@session=click1@time=10", safe="")proxy = f"http://{user}:{quote('PASSWORD', safe='')}@proxy.dinproxy.com:7779"headers = {"User-Agent": "MOBILE_USER_AGENT", "Accept-Language": "de-DE,de;q=0.9"}
response = requests.get("https://ads.example.com/click?id=123", headers=headers,                        proxies={"http": proxy, "https": proxy}, timeout=30)for hop in response.history + [response]:    print(hop.status_code, hop.url)

To cover another market, change the country code, the language and the session ID, and run the same checks again. Each account can keep up to 100 connections open at once, residential and mobile together, so plan parallel browser checks with that in mind. For more on proxy settings in Python, see using a proxy with Python requests, and for the difference between the two proxy schemes, read HTTP vs SOCKS5 proxies.

Frequently asked questions

Mobile proxies are chosen by country only. To pick a state or city, use residential proxies.

Port 7779 on proxy.dinproxy.com, over HTTP, HTTPS or SOCKS5, with the same proxy users and IP whitelist as residential proxies.

Add a session ID and a time to the username, for example @session=check1@time=10. The same ID keeps the same IP for up to 120 minutes.

Keep reading