AdBuyMCP's own vocabulary

Evidence ledger

A six-level grading of how far each supplier integration has actually been proved: sandbox-only, stub, client-built, contract-tested, spend-tested, report-verified. Deliberately not inferred from the presence of code or credentials.
also calledsupply verification statusprovenance ledger
what it means here

In practice, for a UK buyer

The paragraph above is the neutral answer. This is the part a vendor glossary leaves out.

The reason this site can publish a supply matrix that is falsifiable rather than a logo wall. Its governing sentence is worth quoting: a mocked HTTP test proves a client was built, not that a vendor accepted the request, spent money, or returned real delivery. Of twenty-five registered connectors, eighteen are client-built, six are stubs that make no vendor call at all, and one has had read-only calls accepted by a live vendor. Nothing has reached spend-tested or report-verified, and a continuous-integration check keeps those two counts at zero until something genuinely earns them.

Goes deeper: All 25 rails, graded

same group

More on adbuymcp's own vocabulary

Six terms we either invented or use more strictly than the category does. Defined here so nobody has to guess.

All 76 terms

45 minutes. Bring a real brief and we compile it live. You describe one audience and watch it compile into seven targeting specifications, each with the score for how much of the definition survived.

Talk it through