Campaign detail by lifecycle (draft vs running vs completed)

Campaign detail is not one page. It is a state-driven UI that changes depending on campaign status.

If you understand the lifecycle model, you’ll stop getting lost and you’ll debug faster.

At a glance

  • Draft campaigns show readiness and configuration.
  • Scheduled/running/paused campaigns show live monitoring and dispatch health.
  • Completed/failed/cancelled campaigns show the full report dashboard with drilldowns and exports.

Draft campaigns (configure and validate)

Draft view is for:

  • verifying the campaign is launch-ready
  • reviewing configuration before dial
  • previewing the audience distribution

Use Draft campaign detail for the full breakdown.

Scheduled / running / paused campaigns (operate and monitor)

Running view is for:

  • monitoring progress
  • inspecting blockers
  • reading dispatch & queue health
  • drilling into tasks and debug evidence

Use Campaign live monitoring for the full breakdown.

Completed / failed / cancelled campaigns (report and learn)

Completed view is for:

  • interpreting outcomes
  • finding patterns in issues
  • comparing variants
  • exporting evidence to stakeholders

Use Campaign reporting for the full breakdown.

Operator note: don’t trust a “tab” mental model

There is no true tabbed navigation model here. The UX is lifecycle-driven. Teach operators to think “Which state am I in?”

Next: pick the right state guide
Use the guide that matches your campaign status.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.