adstack
Ad monetization infrastructure

Know why revenue moved, not just that it did.

Publishers assemble their advertising from tags, wrappers and vendor scripts accumulated over years, until nobody owns the whole picture. adstack replaces that with reviewable configuration and a measurement pipeline that records every auction — so a change in revenue has an explanation attached to it.

One runtime, the whole delivery path

Slot definition through to rendered impression, configured per site rather than coded per site.

Slot definition and placement

Ad positions declared in configuration, including in-article insertion that counts content blocks rather than guessing at pixels.

Header bidding and price floors

Demand configured per site and per placement, with floors applied where the auction outcome is known and the ad request has not yet gone out.

Consent, properly sequenced

The consent platform is asked while configuration is still loading, so privacy compliance costs the page nothing it did not already spend.

A/B testing that can be settled

Run A/B tests on layout, floors, demand or refresh. Readers are assigned to arms before anything reads configuration, bucket ranges are version-controlled, and every arm is recorded against the revenue it produced — so the test ends with an answer rather than an argument.

Refresh and viewability

Refresh policy expressed as configuration, driven by what the reader actually saw rather than by a timer alone.

Reviewable configuration

Every site's setup is version-controlled and linted before it ships, so review, blame and rollback come as standard rather than as a console audit log.

Measurement is the product, not a report

Most advertising stacks can tell you what happened. Far fewer can tell you why, because the auction detail is discarded before anyone thinks to ask. adstack keeps it.

Every bid A row per slot, bidder and auction — including the ones that lost, timed out or were turned away by a floor.
Every render Defined, requested, rendered, refreshed and viewed, joined to the impression that earned the money.
Named denominators Every rate states what it is a rate of, and thin samples report a fraction rather than a misleading percentage.

Three ways to run a modern ad stack

adstack is built for mid-size news publishers and multi-title groups — large enough that a managed wrapper's revenue share and black-box reporting get expensive, small enough that staffing a dedicated ad engineering team is not realistic.

A managed wrapper

Someone else runs your demand for a share of the revenue. Quick to start, and you see what they choose to show you — which is rarely the bid that lost, or the floor that turned it away.

Build it in house

Full control, and an ad engineering team to hire and keep. The work is never finished, because the vendors, the formats and the privacy rules never stop changing.

adstack

Your configuration, your data, your decisions — on a platform that is already built and already tested, leaving every bid and every render in a warehouse you own.

How it is built

A publisher's page is the business. These are the constraints the platform is held to.

It degrades
Every component has a defined behaviour when it fails, and the failure is announced rather than swallowed. A page that reports nothing still earns; a page that does not render still costs.
It stays light
A single runtime of roughly sixty kilobytes with no third-party dependencies, and nothing added between the auction settling and the ad request going out.
It stays honest
A wrong number is worse than a missing one. Gaps are counted and carried rather than left to be inferred, so a quiet dataset can be told apart from a broken one.
It extends sideways
New behaviour arrives as a subscriber to an event bus or as a configuration field, never as a change to the sequence that puts ads on the page.

Talk to us

adstack is built and in production use. If you run advertising on a publisher site and want to see it, get in touch.

On commercial terms. They are set per publisher, against the number of titles, the traffic they carry and how much integration work the existing setup needs. There is no price list here because a table that fits every publisher fits none of them — it is a short conversation, and we would rather have it properly.