Ad Verification and Brand Safety: Why Ad Tech Needs Verified Proxies

The Ad Transparency Problem

Brands spend billions on programmatic advertising, but where does that money actually go? Studies show that 15-30% of ad spend is lost to fraud, invisible ads, or placements next to undesirable content.

Ad verification platforms solve this by acting as independent auditors — checking that ads actually appeared where and when they were supposed to.

How Proxies Fit In

Ad verification works by simulating real user visits from different locations. Each simulated visit requires:

• A unique IP address in the target geographic market
• A realistic browser environment
• No association with known verification tools (which ad servers might block)

Residential proxies provide exactly this — real user IPs that appear as organic traffic.

Common Ad Fraud Types Detected via Proxies

1. Domain Spoofing

A premium publisher's domain is faked. The advertiser pays for placement on a reputable site, but the ad actually runs on a low-quality site.

Proxy detection: Visit the supposed placement URL from multiple IPs and verify the actual domain.

2. Geo-Fraud

Ad impressions claimed to be from New York actually originate from a server farm in another country.

Proxy detection: Verify ad creative and pricing from the actual target geography.

3. Viewability Fraud

Ads are placed in invisible iframes (1x1 pixels, stacked placements, hidden containers).

Proxy detection: Render the page programmatically and check ad visibility with actual viewport dimensions.

4. Invalid Traffic (IVT)

Bots generate fake impressions and clicks.

Proxy detection: Analyze traffic patterns — identical browser fingerprints, unnatural click timing, and suspicious IP clustering reveal bot activity.

Building an Ad Verification Pipeline

import asyncio
from playwright.async_api import async_playwright

async def verify_ad_placement(url, ad_selector, proxy):
    async with async_playwright() as p:
        browser = await p.chromium.launch(
            proxy={"server": f"http://{proxy}"}
        )
        page = await browser.new_page()
        await page.goto(url, wait_until="networkidle")

        # Check ad element
        ad = await page.query_selector(ad_selector)
        if not ad:
            return {"status": "not_found"}

        # Check visibility
        is_visible = await ad.is_visible()
        if not is_visible:
            return {"status": "hidden"}

        # Get bounding box
        box = await ad.bounding_box()
        if box and (box["width"] < 100 or box["height"] < 100):
            return {"status": "too_small"}

        # Screenshot for manual review
        await ad.screenshot(path=f"ads/{proxy.country}/{url.slug}.png")

        return {
            "status": "verified",
            "size": f"{box['width']}x{box['height']}",
            "url": page.url,
        }

Proxy Requirements for Ad Verification

Real-World Impact

A major holding company used Pineapple Proxy to audit their programmatic campaigns across 45 countries:

Campaigns audited: 12,000+ Fraud detected: 8.3% of impressions Fraudulent spend caught: $2.4M/year (estimated) Saved per campaign: 12-15% of budget

The Cost of Not Verifying

Mobile vs Desktop Verification

Mobile ad verification requires additional considerations:

• Mobile carrier IPs (different from desktop residential)
• Device fingerprint variations
• App vs web rendering differences

Pineapple Proxy supports both mobile and desktop residential IPs for comprehensive verification.

Choosing the Right Proxy Partner

For ad verification, you need:

1. Scale — Thousands of IPs for simultaneous audits
2. Diversity — Multiple ISPs per geography (ad servers cluster by ISP)
3. Reliability — 99%+ uptime on proxy endpoints
4. Speed — Fast rotation to avoid detection
5. API access — Programmatic proxy acquisition

Pineapple Proxy meets all these requirements. View our plans or explore the proxy list to see our global coverage.