Classic advertising, optionally agentic: display, video and native with or without an agent

Display, video and native remain the formats brands use to buy reach. What is new is who operates the campaign: a person in an interface, an agent via MCP, or both. How this comes together at Nexbid, what is in use today and what is still a pilot. The former Digital Campaign Manager has been folded into Nexbid along the way.

Anyone planning a campaign today rarely faces the question "classic or agentic". The real question is: how much of the work should an agent take on, and where does approval stay with a person? The formats hardly change. Display, video and native on established publishers and networks remain the core of media buying. What changes is how campaigns are operated. This article is part of the Agentic Ad Server topic and describes how Nexbid brings both paths together. The Digital Campaign Manager becomes Nexbid We used to offer agent-driven media buying under the name Digital Campaign Manager (DCM) at digital-campaign-manager.com. That function has been folded into Nexbid. There is no second platform and no second login: creating, running and evaluating campaigns happens through the Nexbid Agentic Ad Server. The address digital-campaign-manager.com redirects to Nexbid. The classic path: display, video, native Classic formats are bought programmatically, for example through Google Display & Video 360. There, campaigns, line items, creatives and audiences can be managed across established publishers and networks. Buying and campaign operations for clients are handled by the agency digital nalu GmbH; Nexbid provides the technology behind it. Anyone who does not want to use an agent works exactly this way: briefing, media plan, approval, delivery, report. For publishers using Google Ad Manager, Nexbid is already in use today: context signals from page content are passed to the existing ad server as targeting keys. The ad server stays; it gets better signals. No cookies or device IDs are needed. The agentic path: MCP instead of an interface An agent does not operate an interface, it calls tools. The Model Context Protocol (MCP) is the standard through which assistants such as Claude or ChatGPT use such tools. The Nexbid MCP server (mcp.nexbid.dev) is in use and offers 19 tools, including querying inventory, creating, activating, pausing or cancelling a media buy, submitting creatives and retrieving reports. Public search tools work without a key; transactions require an API key. Nexbid's own ad server, with placements, priority levels and billing by CPM, CPC or CPL, is built and running in a pilot with one sales house. It can also be operated via MCP: an agent can create and evaluate a campaign without anyone filling in a form. Buying ChatGPT ads through OpenAI's official interface is also built and in a pilot. Other vendors are taking the same route. On 13 May 2026, Adform opened …

Author

Nexbid Marketing

Published

2026-11-13

Topics

Ad Tech, Agentic, Programmatic