AI writes the code. Jev gates the decisions. Humans decide what "done" means.
I'm open-sourcing Workflow: a ticket-to-production playbook for coding agents (Claude Code, Codex, Grok). Independent review, human-owned AC, shadow mode by default.
https://t.co/Hp0APZNILt
Ad tech for devs (6/6): Prebid + ad server, and the summary
Prebid can work without an ad server (programmatic-only). But the common flow: Prebid collects bids, the ad server makes the final decision.
The ad server doesn't need to know your SSPs. It only accepts a price parameter. Line items are set per price bucket ("CPM $12.40 fires when hb_pb=12.40"), hundreds of them created in bulk. The ad server compares that price with direct campaigns and picks the higher one. That's why header bidding became possible without Google integrating every SSP.
For video, Prebid caches the VAST and passes key-values (price, bidder, deal ID, format, cache ID). If the Prebid line item wins, the ad server returns a wrapper pointing to the cache and the player plays it.
The market creative plays by the ad server's decision, not around it, or the publisher loses counting. The inventory is yours. You pass info about the external bid plus a cache reference.
If your ad server can't accept external bids, you need your own decision layer, and you own priorities, pacing, frequency and reporting across two blind systems. Feeding Prebid into the ad server is cleaner.
The big lesson: it isn't a chain.
- Ad server: which of my sold campaigns to show, and did it deliver?
- SSP/exchange: who from the market pays for this impression now?
- DSP: who is buying? (Not yours.)
- RTB: how the price is calculated.
- Header bidding: who we ask, and when.