You pay the DSP for impressions in Germany, but in reality, part of the traffic is coming from somewhere in India or Brazil through proxy domains. This is one of the most common problems in programmatic buying — and the only way to catch it is to personally check where the banner from the desired country is actually displayed. Let’s break down how to do this without access to the platform's servers, using a regular browser and proxies.
Why the banner is not displayed where it is claimed
Programmatic advertising is built on automated auctions between DSPs (Demand-Side Platforms) and SSPs (Supply-Side Platforms). In theory, the advertiser specifies geo-targeting — the USA, Germany, Russia — and the system shows the banner only to users from that country. In practice, there is a chain of several SSPs, traffic resellers, and sometimes outright fraudulent platforms between you and the actual display.
The platform may indicate one domain and geo in the bid, but in reality, it shows ads in a completely different location — on low-quality traffic, through bots, or using spoofed user location data. This is called domain spoofing and geo-mismatch, and these two phenomena consume a huge portion of the budgets of media buyers and arbitrageurs who drive traffic through programmatic networks instead of direct purchases in Facebook Ads or TikTok Ads.
The problem is exacerbated by the fact that DSP reports show "pretty" statistics: impressions seem to come from the desired country, and the CTR is normal. But if you physically access the platform with an IP from that country, the banner will either not be there at all or will be shown with different targeting. This is a direct sign that the real impressions are not coming from where they are claimed.
Types of geo-fraud in programmatic advertising
Before checking placements, it is useful to understand what exactly you are looking for. In the programmatic industry, several established schemes of geo and domain fraud are identified:
- Domain spoofing — the platform substitutes a domain of an authoritative site (for example, a major news portal) in the bid request, while the actual display occurs on a low-quality site or in an app.
- Geo-mismatch — the claimed display country does not match the actual location of the user who sees the banner. VPN traffic or IP spoofing on the SSP side is often used.
- SDK spoofing in mobile apps — the advertising SDK in the app simulates impressions that physically did not occur, substituting random devices and geo.
- Ad stacking — several banners are layered on top of each other on one page, counting an impression that the user did not physically see.
- Click injection and fake clicks from botnets — often tied to specific countries with cheap proxy traffic, which also distorts geo-statistics.
Each of these schemes produces the same external effect — you pay for impressions in the claimed geo, but there is no real audience there. Checking through proxies from the desired country allows you to track exactly geo-mismatch and domain spoofing — the two most common and easily detectable types of fraud.
Why to check placements yourself
Many media buyers rely on reports from DSPs and verification services like IAS or DoubleVerify. These are useful tools, but they also work with a limited sample and may not notice local fraud on specific SSPs, especially in tier-2 and tier-3 geos, where verification scripts trigger less frequently.
Self-checking provides several practical advantages:
- You see the banner with your own eyes exactly as a real user from the USA, Germany, or Brazil sees it — without distortions in the DSP panel.
- You can capture a screenshot and the display domain as evidence for a dispute with the SSP or agency.
- You quickly find low-quality traffic sites and disable them in the whitelist/blacklist of the campaign, saving budget as early as the next day.
- You check the creative — sometimes the banner is not physically adapted to the locale (incorrect language, currency, time zone), which reduces conversion even if there is no fraud.
For arbitrageurs who drive traffic from programmatic sources to offers, this check directly affects ROI: money spent on impressions in "dead" geo does not convert at all.
Tools for checking: browser + proxy
To see the ads as a user from another country sees them, you need two components: a browser that does not show signs of automation or location change, and an IP address from the desired geo that looks like a regular home or mobile user.
In practice, a combination of an anti-detect browser and a proxy is used to check programmatic placements:
- Anti-detect browsers — Dolphin Anty, AdsPower, Multilogin, GoLogin, Octo Browser. They substitute device parameters (User-Agent, screen resolution, time zone, system language) so that the profile looks like a real user from the target country, not like a bot or script.
- Residential proxies — provide IPs of real home users in the desired country. SSPs and ad networks trust such traffic the most because it is almost impossible to distinguish it from a regular visitor.
- Mobile proxies — critical for checking programmatic advertising within mobile apps and mobile versions of websites, as some SSPs show different inventory on mobile and desktop traffic.
Using a regular VPN for such checks is a bad idea: the subnets of VPN providers have long been blacklisted by most SSPs and DSPs, and the system may serve you a "clean" version of the page without fraud simply because it sees a VPN IP, not because it reflects the actual behavior of the platform.
Step-by-step check of placements by country
Let’s break down the practical algorithm that marketers use to check where the banner is actually displayed.
Step 1. Gather a list of domains from the DSP report. Export the supply-side report for the campaign — it will list the domains or app IDs where impressions were supposedly made, along with the claimed geo for each impression.
Step 2. Create a profile in the anti-detect browser for the desired country. In Dolphin Anty or AdsPower, select to create a new profile, specify the time zone and language corresponding to the target geo, then connect the proxy in the network settings.
Step 3. Connect a residential proxy from the desired country. In the profile settings section, choose the proxy type SOCKS5 or HTTP, insert the host, port, username, and password for the purchased IP pool for the specific geo. For checking programmatic advertising, residential proxies are the best fit, as ad networks perceive such IPs as ordinary residents of the country, not as data centers or VPNs.
Step 4. Go to the domain from the report and wait for the ad to display. Open the page, wait for the ad block to load, and compare what you see with the claimed targeting of the campaign — the country, language of the creative, format.
Step 5. Capture the result with a screenshot and through DevTools. Open the Network tab in the browser's developer tools, find the request to the ad server, and check which domain and ad unit ID are actually being served — sometimes the banner looks visually similar but is loaded from a completely different source.
Step 6. Repeat the check from a mobile profile. Some programmatic inventory is only displayed in mobile apps through in-app advertising. For this, connect mobile proxies and open the required app or mobile version of the site on an emulator or a real device.
Step 7. Repeat the check in 2-3 days at different times of the day. SSPs often rotate inventory and show different ads depending on the time of day, day of the week, and even auction load. One check may not catch fraud if the platform selectively shows honest traffic.
For mass checking of dozens of domains from one DSP report, it makes sense to set up several profiles in the anti-detect browser for different countries and run checks in batches rather than manually one domain at a time — this saves hours of a marketer's work.
Which proxies are suitable for ad verification
The choice of proxy type directly affects whether the platform will show you the real picture or suspect you are a bot and serve a "clean" version of the page without fraud.
| Type of Proxy | Suitable for programmatic verification | Features |
|---|---|---|
| Residential Proxies | Yes, primary choice | IP of real users, minimal risk of blocking by SSP |
| Mobile Proxies | Yes, for in-app and mobile web | IP of mobile operators, necessary for checking mobile inventory |
| Data Center Proxies | Limited | Fast and cheap, but often blacklisted by SSPs — risk of result distortion |
| Public VPN | No | Massively blocked by ad networks, provides a distorted picture of impressions |
In practice, the optimal combination for auditing programmatic campaigns is residential proxies for the majority of checks on desktop domains and mobile proxies specifically for mobile inventory, where a separate bid is claimed in the auction.
Media Buyer Checklist Before Launching a Campaign
To avoid wasting budget on post-factum checks, it is useful to integrate placement verification into the very process of launching a programmatic campaign. Here’s a basic checklist:
- Request a complete supply-side report with domains and ad unit IDs from the DSP within the first 24-48 hours after the campaign starts.
- Create profiles in the anti-detect browser for each target country of the campaign with the correct time zone and language.
- Connect residential proxies from the corresponding countries and check the top 20 domains by budget expenditure.
- Capture screenshots of domains where the banner does not match the claimed geo or is completely absent.
- Add problematic domains to the campaign blacklist at the DSP level to stop budget leakage.
- Repeat selective checks every 1-2 weeks — SSPs may change the behavior of platforms over time.
- Compare data from verification services (IAS, DoubleVerify) with your own manual checks — discrepancies will indicate blind spots in automated verification.
Conclusion
Programmatic advertising offers a wide reach, but along with it comes the risk of paying for impressions that physically did not occur in the claimed geo. The only reliable way to ensure that your banner is actually running in the USA, Germany, or another target country is to personally access the platform with the correct IP and see the results with your own eyes, rather than relying solely on DSP reports.
For such verification, we recommend using residential proxies as the primary tool — they present themselves as ordinary users and do not raise suspicions among ad networks. If part of the campaign targets mobile inventory, complement the check with mobile proxies, and for quick mass checks of domains without high sensitivity to blocks, data center proxies are suitable. Regular placement checks will save you from budget leakage on fraudulent traffic and increase the actual effectiveness of programmatic purchases.