Direct advertiser campaign management inside an AdTech platform

Set the commercial and scheduling boundaries

The reviewed editor exposes a CPV bid, daily and total budgets, frequency capping, a conversion-tracking switch and scheduling. Inventory includes all-campaign and pending-approval views. Fields and billing models are workflow-specific, not universal across Search, Video, RTB and CPA.

• Name the advertiser, permitted users and approval owner.
• Set commercial limits and the delivery window.
• Define the tracking objective and accepted event.

Target with supported request evidence

Target geography, operating systems, browsers and versions. Available source allowlists and blocklists cover IP ranges, domains, publisher IDs, SubIDs, keywords and feeds. Check that the integration supplies the required context and how missing fields are handled. Targeting does not replace publisher approval of creatives or traffic.

Prepare the creative and its measurement path

Creative records identify advertiser, campaign, type, status and dimensions. The editor separates basic details, tracking and media: width, height, click URL, impression pixel and asset. Match the format and supply requirements. A tracking URL or conversion switch is configuration evidence, not proof of delivered, attributed or accepted events.

Illustrative acceptance check: one campaign, one source

For fictional Spring Demo, agree on one source, creative, target country and bounded test allocation. Exercise eligible, excluded-source and out-of-schedule requests against the delivery and reporting path. This is a test plan, not a Nexus API request, a customer result or a budget-enforcement guarantee under concurrent traffic.

• Eligible: verify creative, destination and recorded events.
• Excluded or out of schedule: check rule enforcement.
• Budget or frequency boundary: agree on counting and timing, then test.
• Missing event: investigate integration and reporting before changing commercial records.

Campaign management is not the whole DSP

DSP Deployment is an integration-scoped combination of campaigns and the RTB runtime. Validate supply access, creative acceptance, advertiser experience, automated bidding, attribution and billing separately; an editor provides no universal exchange access. CPA offers are also a distinct workflow with conversion windows, payout models, caps and publisher permissions.

Hand over an observable workflow

Keep configuration, approved creatives and test results together. Compare channel reports using the same period, advertiser and campaign; distinguish local activity from partner results and their update timing. Assign creative review, event investigation and spend reconciliation. Use the Nexus demo to confirm modules and outstanding integration work.