Diagnostics is where you look before you open a ticket, and what you attach when you do.
The health check:
Five checks at the top of the screen cover the things that usually sit behind a support ticket.
- License: active or not, and whether PRO is unlocked
- License synced with server: synced, or not synced yet with a daily retry
- WordPress REST API: whether the plugin's routes are registered
- WP Sync detected: installed, or not installed which is fine because it is optional
- WP Conversion Tracker detected: same, optional
The debug log:
Logging is off by default so a quiet site stays quiet. Switch on Log what Engage is doing, reproduce the problem, for example by submitting a test opt-in on your own site, then read the Recent Activity table. It records campaign activity, lead capture and every autoresponder delivery attempt with the reason it succeeded or failed, in plain English.
The log is a ring buffer capped at 400 lines, so it can never grow without bound.
The support report:
Click Copy Support Report and you get a single block of text: the plugin version, licence status and sync state, the WordPress and PHP versions, the site URL, whether WP Sync and WP Conversion Tracker are active, how many campaigns and leads you have, and the most recent 100 log lines.
Every line is scrubbed before it is stored. Email addresses are reduced to a first letter and the domain, and anything that looks like an API key or token keeps only its last four characters. Fields named key, secret, token, password or authorization are replaced entirely. A support report is safe to paste into a ticket.
If Engage's own code ever hits a fatal error, it records a breadcrumb naming the file and line in the log rather than leaving you with a blank screen and no explanation. It only ever claims errors from inside its own files.