When you still want a trader
QPS traffic templates, deals, and a custom bidding agent are account-manager and trader work. Adprime Zero will not sell those as a Cursor prompt.
Published 2026-09-09 · Search job: when to hire adops
Some media work is not a public API call.
Adprime Zero lets an agent launch prepaid display, create targeting, submit creative, and read performance. That is real work and it is the product. It is not the whole programmatic stack. Three jobs still belong to a trader or an account manager: QPS traffic templates, deals, and a custom bidding agent.
If your plan depends on those, hire or keep the person who can change them. Do not paste a prompt and hope the model discovers a seat entitlement.
QPS templates are intake, not targeting
QPS is how many bid requests the seat is allowed to see. Front-end traffic templates and filters decide which auctions enter the bidder and therefore consume that allotment. Line-item targeting decides which of the already-received requests may bid. Targeting does not shrink intake by itself.
That split is documented in FreeWheel's own "filtering traffic vs targeting line items" guidance and in our supply research. Excluding a bad placement in targeting stops spend on that slot. The request can still fill the pipe and crowd out better auctions. Reshaping the pipe is an account-manager conversation about templates and list filters. It is not a Buzz PUT from this product.
If remnant waste is mostly "we saw the wrong auctions," you want a trader at the template layer. If waste is "we bid on junk we already received," targeting and placement or site excludes can help. Our Supply Audit apply path acts on exchange, placement, and site grains the compiler can emit. It does not redesign QPS.
Deals are a different supply path
A deal is a packaged path: a deal ID, often a private marketplace or a preferred arrangement, not the open remnant firehose. Open exchange is what our public tests have actually flown. Child-seat deal use has been historically empty even when deals existed elsewhere on the wider Beeswax world.
Do not ask an agent to invent a deal ID. Do not treat "programmatic" as "we must have a deal to start." A first $20/day test does not need one. A brand that already bought a package might. That package is trader work: legal, floor, and trafficking onto the line item.
Delivery modifiers (budget weights across supply segments) sit near this job. They are documented on the seat and were not a buyer workflow when we wrote this. Soft preference is not the same as a hard exclude. A trader who already thinks in weights will care. A founder launching one cell can wait.
Custom bidding agents are a bidder project
Stinger, a custom Bidding Agent API, and data augmentors are real FreeWheel paths. They are not the Adprime Zero campaign object. Building or attaching a custom bidder is seat engineering. It changes how bids are decided in real time. It is not ztdsp campaign create.
If you need a custom bidder, you want a trader plus engineering time on that API. You do not want a chatbot to "set up Stinger" from a prompt.
What the agent should still do
Keep the agent on the public product: isolated funnels, prepaid caps, creative rotation, conversion events, and a readout that does not worship CTR. When the next improvement is "ask AM to filter this class out of QPS" or "traffic this deal" or "attach a bidding agent," write that as a person-owned task.
The daily operator loop still applies. One change, revert written first. A template change and a targeting change on the same day will not teach you anything on a thin remnant book.