StackAdapt Mobile Proxies for Native and Video Placement Checks

StackAdapt is a programmatic platform popular with agencies for native, display, video and connected TV campaigns, with targeting by geography, device and audience. An agency team outside the United States running a US campaign sees impressions in the dashboard and nothing on screen. A Stateside Proxies line in the campaign's metro puts the browser inside the targeting, so placements can be found and recorded as American phone users see them. This page describes the check in plain terms.

What StackAdapt targeting reads from the connection

Geography from the address: country, state, metro. Device and operating system from the browser, with mobile and desktop bought separately and carrier traffic counted as mobile. Daypart from local time. Native placements adapt to the publisher's layout and the reader's device. Datacenter addresses are excluded by pre-bid filters and never see the campaign.

Some location settings go finer than an internet address can. Postal-code buys and tight radius buys around a place lean on signals such as an app's shared location, so a line in the right metro supports a claim at city or state level but not at neighbourhood level. Say so in the report. Audience-based buying has a similar limit: company lists, data-provider segments and retargeting pools consist of people already identified, and a fresh test browser will usually not belong to them.

Who verifies StackAdapt campaigns

Agency traders confirming line items serve in the right metro with the right creative. Account managers reporting to clients with screenshots. Brand-safety reviewers checking publishers and adjacency. Creative teams confirming native and video placements render correctly on a phone. Each is a human finding a live placement from inside the audience.

Native units are the hardest to find by eye because they borrow the publisher's styling, so give each page a slow scroll and look for the sponsored label rather than the brand; the headline and thumbnail you approved are what confirm the placement is yours. Video units need a few seconds to begin before a screenshot is worth taking.

Why a carrier line

A real US mobile address in the metro is inside the targeting and passes pre-bid filters; a VPN's datacenter address does not. The address holds steady across a session, so frequency caps and sequential creatives behave as they would for one real user.

Connected TV placements bought through StackAdapt cannot be seen in a browser at all, which is a limit worth stating to a client up front; the line verifies the native, display, mobile web and in-app parts of a campaign, and the CTV portion is confirmed from the platform's own reporting. Teams that explain that split before the campaign avoid an awkward conversation after it.

Setting up the check

Rent a line in the campaign's metro, build a browser profile with the metro's time zone and US English, and browse the publishers in the inventory list during the campaign's daypart. Screenshot each placement with URL and local time, click through once and record the landing page. For mobile video and in-app placements use a test phone through the line's VLESS link.

Start from StackAdapt's domain reporting, which lists where impressions were delivered, and open the sites with recent delivery. Keep two questions apart: whether the creative renders properly, which a creative preview can answer, and whether it serves in the market, which only a live sighting can. When a native unit appears, check how the publisher's template has treated it, as long headlines get shortened and images are cropped to the site's own proportions, and confirm the landing page keeps the tracking parameters your analytics depends on.

Staying inside the rules

Platform and publisher terms forbid click inflation and automated traffic. One human, one click-through per placement, a record of what was seen.

A click-through made during a check may be charged like any other, so list those clicks beside the screenshots and leave them out of the performance figures you send the client.

Setting up a StackAdapt proxy on Stateside Proxies

1. Rent a line in the campaign's target metro.
2. Create a browser profile with the line's details, the metro's time zone and en-US; confirm the carrier on an IP lookup page.
3. Browse the publishers in the inventory list during the campaign's daypart.
4. Screenshot placements with URL and local time; click through once.
5. Move the line to the next metro, free, and repeat.

StackAdapt proxy questions