Event Health Docs

Monitor events for silent issues that block registrations and revenue.

Overview

Event Health extends event management by continuously scanning events for configuration issues that can silently block ticket sales, reduce visibility, or disrupt operations.

Many event issues do not produce errors or warnings inside WordPress. An event may appear published and valid, but still be unsellable, hidden, or misconfigured. Event Health is designed to surface these silent failures before they impact registrations or revenue.

Event Health runs read-only checks against upcoming and ongoing events and presents results in a centralized dashboard. Issues are grouped by severity and include clear guidance on what needs to be fixed.

This approach reduces manual checking, improves operational reliability, and helps teams maintain confidence that events are functioning as expected.

Requirements

  • WordPress
  • The Events Calendar

Installation

  1. Install the plugin via the WordPress admin
  2. Activate the plugin
  3. Enter your license key under Plugins → Installed Plugins

Once activated, Event Health begins scanning events automatically using default alert settings.

How Event Health Works

Event Health performs automatic scans of events and evaluates them against a set of configurable checks.

Important notes:

  • All scans are read-only
  • No event data is modified
  • No tickets, settings, or metadata are changed
  • Alerts are informational and advisory only
Event Health highlights issues so administrators can take action intentionally.

Alert Severity Levels

Event Health organizes alerts into three severity levels to help teams prioritize action.

Critical Alerts (Red)

Critical alerts indicate issues that commonly block registrations, hide events, or stop revenue entirely.

Examples include:

  • Events with no tickets attached
  • Ticket sales not started or closed too early
  • Events marked as private
  • Events hidden from event listings
  • Events not published but starting soon

Critical alerts should typically be reviewed and resolved immediately.

Warning Alerts (Orange)

Warning alerts highlight configuration gaps that may not block sales outright, but often cause confusion, operational friction, or inconsistent presentation.

Examples include:

  • Missing categories
  • Missing venue or organizer
  • Duplicate event titles
  • Ticket title mismatches
  • Missing featured images or descriptions
  • Missing zones or schedules when related plugins are active

Warnings help maintain consistency and quality across large event catalogs.

Information Alerts (Blue)

Information alerts provide visibility into important event states without indicating a failure.

Examples include:

  • Events with capacity set to zero or unlimited
  • Events where tickets are sold out
These alerts help teams understand current event status at a glance.

Configuring Alert Checks

Each alert type can be enabled or disabled individually.

To configure alerts:

  1. Navigate to the Event Health settings page
  2. Locate the alert category (Critical, Warning, or Information)
  3. Enable or disable specific checks as needed
  4. Save settings

This allows teams to tailor alerting to their operational workflow and avoid unnecessary noise.

Active Alerts Dashboard

The Active Alerts dashboard displays all current alerts across events.

Each alert includes:

  • Event name
  • Alert severity (color-coded)
  • Description of the issue
  • Guidance on what needs to be fixed
  • A notes field for internal comments
  • An option to ignore the alert

Alerts update automatically as events are edited or conditions change. Cache may need to be cleared in some instances.

Ignored Alerts Dashboard

Not every alert represents a problem. Some configurations may be intentional.

Ignored alerts are moved out of the active dashboard and stored separately. This keeps the main alert view focused on actionable issues.

Ignored alerts can be restored at any time if circumstances change.

Alerts update automatically as events are edited or conditions change. Cache may need to be cleared in some instances.

Plugin Awareness & Integrations

Event Health adapts its checks based on other active LogicalWP plugins.

Examples:

  • If Recurring Schedules is active, Event Health can alert when events have no recurring schedule defined
  • If Venue Zones is active, Event Health can alert when events are missing zone assignments

This ensures alerts remain relevant to the installed workflow without forcing dependencies.

Scan Scope & Timing

Event Health focuses on:

  • Upcoming events
  • Ongoing events
  • Events starting soon (based on configurable thresholds)

Past events are generally excluded unless relevant to a specific check.

Scans run automatically and require no manual triggering.

What Event Health Does Not Do

Event Health is intentionally designed as a monitoring system, not an enforcement system.

It does not:

  • Modify event settings
  • Automatically fix issues
  • Block publishing or saving events
  • Prevent intentional configurations

Its role is to surface issues clearly and early so teams remain in control.

Who Event Health Is Built For

Event Health is designed for organizations managing large numbers of events where manual review does not scale.

This includes sports clubs, academies, schools, recreation centers, community programs, and any organization running high-volume ticketed events where silent misconfigurations can lead to lost registrations or operational issues.