Persona compiler
In practice, for a UK buyer
The paragraph above is the neutral answer. This is the part a vendor glossary leaves out.
The division of labour is the whole design. A language model extracts semantics from the brief: what kind of person, which interests, which geography, what intent. It never emits a vendor segment identifier. Deterministic registry code then matches those semantics against catalogue keywords by whole-token overlap — exact token equality, never substring containment, so 'ai' cannot match 'sustainability' — and emits known identifiers. That is why a compiled plan can be audited line by line, why a hallucinated segment cannot reach a buy, and why the same brief compiles the same way twice.
Goes deeper: The loop, step by step
What this one connects to
Most confusion in media buying comes from two adjacent terms being used interchangeably, so these are the neighbours worth reading next.
Fidelity score
A published score out of 100 answering one question: how much of an audience definition survives translation into a channel's native targeting words. It is a property of that translation rather than a forecast, and it is not a quality rating.
Audience segment
A named group of people a seller will let you target, defined by some combination of demographics, behaviour, stated interest or inferred intent, and identified in a buying system by a specific identifier.
Lawful-basis manifest
A record attached to every compiled channel plan naming each data source used, the lawful basis it relies on, the conditions that come with it, and the warnings raised while compiling — produced automatically rather than assembled on request.
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.
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