Vexal Documentation by WileyLabs

Visibility Campaigns

Stable

Applies to: SmartBlocks campaign orchestration

Introduced: Campaign workflows in v1 lineage

Updated: Documentation v1

Visibility Campaigns organize optimization into governed phases: scan, safe fix, FAQ guided review, and compare.

Summary

Campaigns group page-level evidence and actions into a repeatable run. The system keeps recommendations explainable and preserves rollback points before write operations.

Use cases

  • Batch triage pages with low readiness
  • Apply only approved safe fixes
  • Review FAQ improvements before publish

How it works

A scan collects readiness and recommendation evidence, campaign queues are generated by recommendation key, and users execute governed apply actions with snapshot logging.

Inputs

  • Campaign scope (post types/pages)
  • Readiness and telemetry signals
  • Registry-backed recommendation keys

Outputs

  • Campaign status and queue items
  • Safe fix and FAQ action outcomes
  • Before/after comparison metrics

Admin UI location

WordPress admin page slug: smartblocks-optimization-campaigns.

Campaign metrics consume crawler/agent and readiness trends from Telemetry Engine.

Campaign run, apply, and snapshot events are written to the Visibility Ledger.

Security

Campaign actions are nonce-protected and capability-gated. Writes are bounded to safe handlers and evidence-backed keys.

See also