Your ad, in a named placement
A Placement is a specific position on a publisher surface. Your ad runs in the ones you buy, inside the Flight you set, and a request from a domain you haven’t approved gets nothing back.
Scout tracks what happens when people SEE, WATCH, CLICK, and CONVERT from your ads.
A customer doesn’t have to click an ad for Scout to show you that they saw it, how long they watched it, and whether that exposure helped lead to a conversion.

Every view. Every click. Every watch. Every conversion. All in one journey.
One platform covers the whole span: choosing which ad fills a slot, recording what the audience did with it, and keeping those records long enough to be worth reading.
A Placement is a specific position on a publisher surface. Your ad runs in the ones you buy, inside the Flight you set, and a request from a domain you haven’t approved gets nothing back.
Scout records its own serves directly. When a video player or a demand-side platform serves the ad instead, Scout sees the tracking pixels those systems fire back. A single play lands on exactly one path, which is what makes the Blend a sum rather than a double count.
Dashboards read daily Rollups, computed once and kept. Raw activity ages out; the reporting doesn’t go thin behind it, so a campaign still reads the same twelve months later.
Scout isn’t a network reselling someone else’s traffic. It serves onto two properties, and everything it knows about an audience originates on them.
The combat-footage community and its readership. The browsing Scout observes here is what later connects a visit to a sale.
The video catalogue, its channels, and the gear pages attached to them — placements beside the content your buyers came for.
Both are generated in Scout with your id already filled in, as plain HTML or a Google Tag Manager variant. Most vendors deploy both.
| Pixel | Where it goes | When it fires | What it answers |
|---|---|---|---|
| Conversion | Checkout or order-confirmation page | Once per completed order | Did this sale come from a Scout ad? |
| Browsing | Sitewide | On each page view, single-page routes included | What did Scout-referred visitors do on the site? |
A holdout is a serve request Scout deliberately fills with nothing, so the audience that saw you can be compared against a matched audience that didn’t. Without one, every figure on a dashboard is a correlation wearing a campaign’s name.
A holdout renders nothing, so it is never an impression and never counts toward reach. It costs a slice of delivery and buys the only honest answer to what the campaign actually moved.
Tell us which placements you want and the flight you want them in. We’ll set up the account, the pixels, and the first campaign.