Check ads the way a US phone sees them

In-app ads change with the device, the network and the place they are seen from. To know what a person in Atlanta sees on their phone, you need a phone that looks like theirs, on a network like theirs.

Our phone model turned to the left, showing its home screen

Why emulators and datacenter IPs see different ads

Ad networks screen out traffic that looks automated. An emulator or a datacenter address is often shown fallback ads, or none, so a check from one tells you little about what real people see.

A Distilled phone carries a real handset's identity, passes Play Integrity, and browses from a US mobile carrier network, so it is served ads the way a real phone is.

  • A real handset's profile, Pixel 7 Pro, 7 or 7a on Android 13 to 16, checked when it starts and every 6 hours.
  • Passes Play Integrity, up to its strongest verdict.
  • Its own pre-checked US mobile carrier IP, or your own proxy.
  • Apps from the Play Store, our catalogue, or your own APK.
  • Driven live from the browser, or by an AI agent across many phones at once.

Checks from six US cities

Each phone exits in one of six US cities, and you can move it to another. Set the phone's location to match, and apps that use it see the same place.

A record of what was shown

Open the app, scroll to the placement and take a screenshot, by hand from the browser or with an agent across many phones. A run keeps a screenshot of every step, so each check comes with the screen it saw.

Questions

Which cities can phones be in?

Our mobile exits cover six US cities, and more are coming. Pick one for each phone, or bring your own proxy for somewhere else.

Can I automate the checks?

Yes. Describe the check in plain words and run it on up to 50 phones at a time from the console, the API or your own AI agent.

More in the docs, on pricing, and in our acceptable use policy.

Other use cases

All use cases