Ad exchange
Two files should be enough to know what you are buying
In connected TV the distance between a buyer and the screen is usually filled with
intermediaries nobody can name. Our supply comes from the party that owns the device or
the network, and the path is written down: sellers.json, a supply chain object on
every request, and a DIRECT line in the seller’s own file.
How the exchange works
- Protocol
- OpenRTB 2.5 / 2.6 Pod objects on 2.6: podid, podseq, slotinpod. 2.5 accepted for legacy buying stacks.
- Auction
- First price, published One auction model, stated plainly. No soft floors discovered by accident, no second-price rebate nobody can audit.
- Supply path
- One hop, declared sellers.json, schain on every request, and a DIRECT line in the seller’s own app-ads.txt. A buyer can verify the whole path in two files.
- Inventory
- Device makers and operators Launcher, FAST, in-app and set-top-box breaks - bought from the party that owns the screen, not from a chain of resellers.
- Quality
- Pre-bid filtering Invalid traffic removed before the bid request leaves us, not credited back after the fact.
We are early and our supply is growing. Rather than publish a volume figure that flatters us this month, we will show you live availability for your regions on the first call.
Tell us the campaign and we will tell you if we have the screens
Regions, formats, and the flight you are planning. If our supply does not cover it, we will say so - a buyer who was told no once will believe the yes next time.