The hard cases: 4 ad screenshots other tools can’t capture
Click paths, sizeless native ads, missing URLs, and choosing where the ad is captured
Landon Bennett
Most proof-of-placement screenshots are simple: load a page, find the ad, capture it. The ones that eat up ad ops teams’ weekends are the edge cases: ads that only exist after a long click path, native ads with no size, pages that aren’t in the campaign setup at all. Ad Reform has spent nearly a decade building for these. Here are four we solve today.
1. Ads that only load after a click path
One of the largest real estate sites in the US runs a native ad at the bottom of a listing’s photo gallery. To see it, you search a city, filter to houses, open a listing, click “See all photos” and scroll past every image. Only then does the ad slot load.
There’s no URL to point a tool at. The page doesn’t exist until someone browses their way to it, so the publisher’s team used to do this by hand hundreds of times a month.
Ad Reform’s agent does the browsing: every click and scroll, on a listing that’s actually for sale, in the geo the campaign targets. Our GAM agent reads the geo from the line item, so the ad never lands on a sold listing or in the wrong market.
2. Native ads with no width, height or preview
In Google Ad Manager, most native creatives have no width and no height. You get an image asset and a set of template variables, and the page assembles the real ad when it serves, in the shape of whatever slot it lands in. There’s nothing on the ad server to preview or screenshot.
One of our publisher customers, a top 5 news site, has four units a native ad can render into, depending on the line item’s targeting. Ad Reform’s agent reads that targeting, renders the native ad in our GAM native previewer, then captures it on the right page, unit and placement. Same creative, four completely different shapes.
Before, someone had to wait around, even on weekends, for a specific native ad to show up in a specific unit. The GAM native previewer is also available through our API, and teams use the rendered images to analyze and tag their native creative in their own AI-based creative intelligence tools.
3. Branded content with no URL
Sometimes a publisher doesn’t just sell an ad slot. It writes the article, such as a restaurant map or a topic explainer made for that advertiser, and sells every ad slot on it. When the advertiser asks for proof, you need screenshots on that specific article. But its URL exists nowhere in the campaign setup: not on the line item, not on the order.
What GAM does have is the creative’s click-through, usually wrapped in a DoubleClick tracking redirect. Ad Reform’s agent works the problem the way your team would: it confirms the line item is branded content, looks for a capture page, rules out the advertiser’s own site, checks sibling lines in the same order, reads the real article URL out of the tracking wrapper, and then captures every ad slot on that page.
4. You decide where the ad is captured
Some customers only get domain-level reporting, like nytimes.com, but don’t want screenshots on a homepage for brand safety reasons. Others always need an article page. Now each organization chooses where the agent captures the ad:
Exactly the URL you enter
An article on the site, when you enter just a domain. Every organization starts here, and it’s how captures already worked.
Any page on the same site that fits the ad and your instructions better
The agent always stays on the site you entered. In-article formats like native ads go on an article even with the exact-URL setting, because they sit between paragraphs. And if your special instructions ask for a specific page, such as the homepage, the agent follows them.
Have a hard case of your own?
We add new edge cases every week. Send us the one your team dreads and we’ll show you how we’d capture it, or see how automated ad screenshots work.
