Prove one buying workflow
before expanding.
A proposed first pilot for an independent agency: one advertiser, a 30-second CTV creative and one agreed supply connection.
This plan is a proposed scope. A participating customer, live supply authorization, commercial terms and success thresholds have not been agreed. No customer results are published here.
Keep the first evaluation focused.
Start with the synthetic MCP sandbox. Then review the same buying workflow with the agency’s operator, using its requirements and an authorized supply relationship. Make live activation a separate decision.
Try the synthetic workflow ↗- Buyer profile
- Independent media agency
- Media format
- 30-second CTV video
- Initial workflow
- Agent brief, creative sync, buy, review and delivery
- Initial environment
- Isolated synthetic evaluation
Agree on evidence before the test.
Complete the buying workflow.
Discover a compatible product, sync the 30-second creative, create a buy and retrieve its status. Record every request and response.
Enforce buying authority.
Check unauthenticated access, out-of-scope operations and a buy requiring operator review. A pending buy must stay inactive until approved.
Explain the decision.
Inspect one eligible CTV request and at least three deliberate no-bid cases: incompatible duration, a privacy restriction and an exhausted budget.
Reconcile delivery.
Compare accepted billing events, duplicate callbacks and reported delivery. Explain each discrepancy and verify that a duplicate does not add spend.
Measure the agreed traffic.
Agree the request mix, catalog size, concurrency, latency target and error budget before the load test. Report the measured tail latency and failed requests.
Make a documented go or no-go decision.
Name the buyer and operator owners. Review open defects, supply authorization, creative review and recovery. Any live flight needs separate approval and agreed commercial terms.
Bring a brief the operator can evaluate.
Describe the intended audience, geography, device and app restrictions, flight, budget ceiling, reporting needs and the person authorized to approve the buy. Supply access and privacy requirements should be settled before any live traffic.
The evaluation record should retain the agreed thresholds, test inputs, request traces, outcome reconciliation, open defects and both parties’ go or no-go decisions. Customer names or results require their approval before publication.
Download the pilot brief ↗Use the DSP evaluation checklist ↗Review the measured benchmark setup ↗