Delivery modifiers as budget weights

Delivery modifiers in programmatic buying are a budget-allocation object, not a bid scaler and not a targeting exclude. Terms are { targeting, rank, weight } plus a required fallback_weight. They weight spend across supply segments after a request is already eligible. This seat has had zero delivery modifier objects. We have no delivery to quote. This page is a plan.

If you searched for whether delivery modifiers would have cleaned Supply Bench, we do not know. We have not created one.

Where this sits next to the other levers

Hard exclude removes eligibility. A bid modifier scales the bid when a term matches. A delivery modifier weights budget across matched segments and needs a fallback for the unmatched remainder. Those are three different writes. Folding them into one "supply control" is how a later agent will ship the wrong object.

The bid-scaler plan is Bid down a bad placement instead of killing it. The exclude map is Open exchange waste, mapped by grain. There is still no object named supply route. What we mean by a supply path.

What a first test would have to prove

Create one modifier. Leave a documented revert. Attach it to a copy, not to every live line item. Read spend share by the same grain the weights named. If the fallback takes all the money, the weights did not run. If CTR is the only readout, the test is not judged. CTR is how remnant looks busy.

We will not invent a weight table for OPENX, SMARTADSERVER, or the seven-domain set. We will not say a fallback_weight of any number is the right default. Those numbers do not exist until we write and restore a real object.

This file stays kind: plan until a dated object exists on the seat and a revert command is written before the attach.