17 Sep 2026 · 5 min read

How Agent Mandate Governance Compares to Human Campaign Controls

Published: 17 September 2026

TL;DR: In conventional programmatic, human campaign controls are platform configuration settings that enforce buying behaviour at the DSP level. In agent mandate governance, controls are expressed as mandate parameters that the agent evaluates before acting. The key practical difference is that mandate governance produces a documented decision trail, while platform configuration does not. The two approaches are not mutually exclusive. A buying organisation can use both, with DSP configuration for open auction inventory and mandate governance for bilateral deals.


Every buying organisation has controls on how their advertising budget is spent. In conventional programmatic, those controls exist as platform configuration: bid caps in the DSP, frequency caps, placement exclusions, targeting parameters. The DSP enforces them when evaluating bid opportunities. The buyer configures the settings. The platform applies them automatically.

Agent mandate governance works differently. The controls are not platform configuration. They are parameters in a mandate: a human-approved governance document that the agent consults before making any decision. The agent evaluates every proposal or action against the mandate and acts only within the parameters it defines.


How Platform Configuration Works

DSP campaign controls are configuration settings. A bid cap is a value entered in the DSP that the platform applies when submitting bids. A frequency cap is a rule the platform applies when deciding whether to bid for a user who has already seen the ad. A placement exclusion is a list the platform checks before bidding.

These controls are enforced at the platform level, not by the buyer's agent. The buyer configures them, but the enforcement logic is the DSP's. The buyer cannot easily audit why the DSP declined a specific bid opportunity: the platform's decision logic is internal.

Platform controls can be adjusted in real time. A buyer who wants to raise a bid cap during a high-demand period can update the setting. A buyer who wants to exclude a placement category mid-campaign can add it to the exclusion list. The control is responsive and immediate.

What platform configuration does not produce: a record of every decision made and why. The DSP logs deliveries and spend. It does not log every bid opportunity evaluated and the control that determined the outcome.


How Mandate Governance Works

A buy-side agent operating under a mandate consults the mandate parameters before taking any action. A proposal arrives from a sell-side agent. Before responding, the buy-side agent checks: is the proposed CPM within the mandate ceiling for this content category? Is this inventory category on the approved list? Does this deal size require escalation to a human?

The agent then acts: accept, counter-propose, decline, or escalate. The action and the mandate parameter that determined it are recorded in the decision log. Every decision the agent makes has a documented reason in the mandate.

This produces something platform configuration does not: a decision trail. After a campaign, a buyer can retrieve the decision log and see every proposal the agent evaluated, every mandate parameter it applied, and every decision it made. The governance record is explicit and complete.

Mandate parameters are not adjusted in real time. Changing the mandate requires a human approval process. This is intentional. The mandate is the human's documented decision about what the agent is authorised to do. Adjusting it mid-campaign without human approval would undermine the governance framework.


The Practical Difference: Explainability

The most significant practical difference between platform configuration and mandate governance is explainability.

If a client asks why a specific placement category was included in a campaign, the answer from a DSP-configured campaign is: because the targeting settings did not exclude it. The answer from a mandate-governed campaign is: because the mandate's approved category list included it, and the decision log records which deals were agreed against it.

If a regulator asks how budget was allocated across content categories, the answer from a DSP-configured campaign requires extracting delivery reports and reconstructing the allocation retrospectively. The answer from a mandate-governed campaign is: the mandate defined the allocation parameters, and the DealSheet and decision log record how each deal was agreed.

Explainability is not just a compliance concern. It is a quality control mechanism. A buying team that can explain every decision their agent made can identify where mandate parameters are not calibrated correctly and improve them for the next campaign.


What Mandate Governance Requires From the Buying Team

Mandate governance requires more upfront work than platform configuration. The buying team must document the mandate parameters before the agent begins negotiating. CPM ceilings by content category, inventory category approvals, approval thresholds: these decisions must be made and documented before the campaign starts, not configured incrementally as the campaign runs.

This is a different working pattern from DSP configuration, where controls are adjusted throughout the campaign based on performance data. Mandate governance front-loads the decision-making. The campaign runs under the parameters set at the start.

For buyers who want to adjust parameters based on in-campaign performance, the mandate can be revised between campaign periods. The revision requires human approval. The new mandate governs the next period.


How the Two Approaches Coexist

A buying organisation does not choose between mandate governance and platform configuration. The two approaches apply to different transaction types.

DSP configuration is appropriate for open auction inventory, where the buying decision is made in real time at bid price and the relevant controls are bid caps, frequency caps, and targeting parameters. Mandate governance is appropriate for bilateral deal negotiation, where the agent is agreeing specific deals with specific publishers at specific CPMs, and the relevant controls are CPM ceilings, content category approvals, and approval thresholds.

A sophisticated buying team uses DSP configuration for open exchange inventory and mandate governance for bilateral CTV deals negotiated through an agentic marketplace. The two approaches are complementary, not competitive.

All articles

Speak to the team