Our technology

Publishers do not need to be engineers to benefit from AdsWine — but many are, and ask. Here is what runs underneath, in plain terms.

The auction engine

A dedicated ad server runs the live auction for every request. For each placement it checks eligibility, calls the connected demand partners in parallel under a strict time budget, applies floor prices and creative-safety rules, and picks the highest eligible net bid. Late bids are worthless — even by a millisecond — which keeps the auction honest and the page fast.

Hybrid demand

Three integration types feed the same auction: server-side OpenRTB 2.5 endpoints, Prebid header-bidding partners whose client-side bids compete against the server result, and JavaScript tag partners whose tags join the waterfall at their expected value. One request can therefore be contested by every demand source a publisher has.

Measurement and protection

A lightweight tag on the publisher's page handles delivery and measurement: viewability (50% for one continuous second), click validation, consent signals and — with the publisher's settings — privacy-respecting visitor counting that stores hashes, never raw identities. An invalid-traffic layer classifies bots and data-centre traffic, and an AI traffic guard can stop a bad site's requests before they reach demand at all.

Data and finance

Auctions, impressions and earnings are stored in a transactional database with an append-only financial ledger; asynchronous workers validate impressions, calculate revenue shares and release earnings after the holding period. The result is a platform where the numbers on a publisher's dashboard and the numbers in our ledger are the same numbers.