Andrew Byzov, CMO of DataImpulse, looks at the issue of Geo blind spots and the importance of overcoming them to know the true value of a campaign.

The launch of a global ad campaign with geotargeting is only the first stage and does not fully guarantee the target audience will see the final approved content. Many endorsers face a 'Geo blind spot' issue. They are isolated from the regional picture and rely only on the analytics of their ad account. With no appropriate local check, there is a critical gap between what’s in the system and what end users see on the screen. 

This 'blind' zone creates an ideal environment for ad fraud. The most popular threats include cloaking, which is the process of identifying the IP addresses of advertisers and showing them a completely legitimate page, while real users in the target region see spam or malicious content. The next problem is zero conversion caused by inaccurate GeoIP data, so ads are being displayed outside the target city or region. Last, but not least, is Invalid Traffic, or IVT, which accounts for up to 22% of all digital ad spend. 

Attempts to resolve these issues with basic instruments usually give a false sense of control. 

The use of standard VPN services or data centre proxies doesn’t work for ad verification. Modern advertising networks and anti-fraud systems easily recognise such connections by the ASN (Autonomous System Number) of the hosting provider. As a result, the target server either completely blocks the request or gives a 'sterile' version of the page that does not match the actual output. To see the campaign through the eyes of the local consumer and to collect reliable data, a network-level infrastructure that can fully simulate the presence of a real device at a given geographical point is a must.

Three levels of geocontrol

Advertising platforms use a multi-level inspection system to identify the user. To set up reliable campaign monitoring, you have to know how to bypass the main levels. The basic location indicator is the IP address. When a device makes a page request, an advertising server or SSP drives that IP address through commercial GeoIP databases.

These databases do not just give coordinates. They map the IP to a specific ASN and provider type. If the system sees an ASN that belongs to cloud hosting, it classifies the connection as data centre or machine traffic. As a result, the server blocks the display of ads instead of the real target creative. Depending on the campaign settings, testing should take place at the following levels:

• 1st level - Country-level. Sufficient for basic validation of global campaigns, for example, for SaaS products, but it is completely blind to local cloaking.
• 2nd level - State or city level. Necessary for localised businesses such as retail and delivery. Advertisements tailored to Chicagoans will not physically be rendered if the script uses an IP address from Dallas.
• 3rd level - ASN or provider level. Highest degree of accuracy. It is used to verify mobile traffic and detect specific fraud within the networks of specific operators.

Why the right IP is not enough

Modern anti-fraud algorithms and ad networks rely on browser fingerprinting. If the fingerprint looks like an automated script, the advertiser falls back into the 'blind' zone. To distinguish a real device from a server bot, anti-fraud systems check a whole complex of hidden markers:

1. Canvas and WebGL imprints analyse the uniqueness of graphics rendering and instantly detect server bots without a real graphics card.

2. The inconsistency of system fonts or language with the declared location is immediately blocked by security algorithms as a suspicious anomaly.

3. The active WebRTC protocol often reveals the true IP address of the device, bypassing the configured proxy.

4. Standard HTTP headers and User-Agent from web automation libraries can label the request as machine traffic.

That is why overcoming Geo blind spots requires a complete infrastructure that simulates a full-fledged environment of a real local device.

Proxies and geotargeting 

For anti-fraud systems and advertising networks to perceive a test request as a valid view from a real person, the verification system must be based on two key components:

• Residential proxies with sticky sessions support. 

Since the IP addresses of data centres are instantly blocked, the basis of the infrastructure should be networks of real Internet service providers (ISPs). Plus, it is critical to keep one address active for several minutes. This allows the entire funnel to pass from the click on the banner to the final target redirect without breaking the connection, which the anti-fraud systems would regard as an anomaly.

• Anti-detect browsers for fingerprinting. 

Even the best residential IP won't work if the browser fingerprint produces an automated script. Anti-detect browsers generate isolated profiles by replacing Canvas, WebGL, fonts, and HTTP headers. After that, users can simulate unique devices for simultaneous testing of campaigns in different cities.

Practical implementation and automation

Building a bulletproof monitoring system comes down to modern automation frameworks and appropriate proxies. The industry standard is the combination of Python and Playwright because it works with browsers directly, better bypasses anti-bot protection, and is able to intercept network requests. Residential proxy pools can be integrated directly into the script, allowing you to dynamically change the test city by simply changing login parameters. 

Since checking ads is always a multi-stage chain from banner display to final redirect, use the sticky sessions feature. Holding one IP address throughout the session ensures that the ad network doesn’t have a connection break and reject the transition as fraudulent. 

The final stage of this funnel is to collect evidence. The script must take a screenshot of the output and capture the final URL to detect cloaking or other violations.

Summing up

Setting up geotargeting in the ad account is only an intention, not a guarantee of impressions. The core task is to technically simulate the presence of a real user in the desired region. For such automation, developers need residential proxies with targeting up to the level of a specific city or Internet service provider (ASN).