Campaign approval workflow

Every campaign needs a visible review path before it touches publisher traffic.

This module structures how campaigns move from draft to approval, rejection, changes, pause and delivery. It protects advertisers, publishers and admins from the chaos that happens when campaign review is informal.

Approval control snapshot

Review route

Draft → Submitted → Decision

Admin checks

Creative + wallet + targeting

User clarity

Visible rejection notes

Publisher safety

Approved campaigns only

Review stages

A campaign should not be approved because it exists. It should be approved because it is ready.

Clear approval stages help the platform reject bad campaigns early, protect publisher audiences and make advertiser feedback specific enough to act on.

Campaign submission

Advertiser submits campaign objective, creative, CTA, landing page, targeting, budget and schedule.

Creative and CTA review

Admin checks copy, image, video, CTA fit, misleading claims and whether the preview matches platform rules.

Landing page and wallet check

Platform verifies landing page safety, destination relevance, available wallet balance and minimum campaign budget.

Targeting and publisher-fit review

Admin checks whether the selected location, niche and available publisher inventory can support the campaign.

Admin review checklist

Campaign title and description are clear, specific and not misleading.

CTA matches the landing page action and does not trick users into clicking.

Uploaded image or video is clean, brand-safe and relevant to the offer.

Landing page loads properly and does not contain malicious, deceptive or unrelated content.

Budget, CPC, schedule and target location are realistic for available inventory.

Campaign niche fits at least one approved publisher category or inventory group.

Restricted claims, regulated offers and suspicious traffic promises are escalated before approval.

Visible campaign statuses

Draft

Advertiser is still building the campaign and nothing is visible to publishers.

Submitted

Campaign has been sent to admin review with all required fields.

Needs changes

Campaign is blocked until advertiser corrects weak creative, broken links, poor CTA or policy issues.

Approved

Campaign can enter eligible inventory and be shown through approved publisher placements.

Paused

Campaign is temporarily stopped because of budget, schedule, review or advertiser decision.

Rejected

Campaign violates platform rules or cannot be fixed enough for safe delivery.

Transparency rules

Approval must leave an audit trail

If the platform cannot explain why a campaign was approved, rejected or paused, disputes will become personal arguments. A visible workflow turns moderation into policy.

Advertisers should always see why a campaign is pending, approved, rejected or sent back for changes.

Admins should not approve campaigns manually without leaving review notes.

Publishers should not receive campaigns until the campaign has passed minimum review checks.

Campaign resubmissions should preserve the rejection reason so problems do not repeat silently.

Approval speed should never be used as an excuse to allow weak campaigns into the network.

Approve

Campaign meets platform quality, budget, safety, landing page and targeting requirements.

Request changes

Campaign can be fixed, but needs clearer creative, better CTA, corrected link or stronger targeting.

Reject

Campaign is unsafe, deceptive, non-compliant, unsupported by inventory or too risky for publishers.

Notify

Advertiser receives status change and admin notes instead of guessing what happened.

Weak approval systems destroy ad-network trust.

Use the approval workflow to make every campaign status, review note and decision traceable.

Submit a campaign