Event detail
Everything recorded about a single change or error, and what has been stripped out of it.
Click any Timeline row to open the full record.
What you see
Header — a readable label, a severity chip, the site, and when it happened in your timezone.
Fields, whichever apply to the event type:
| Field | Appears on |
|---|---|
| Type | Every event |
| Occurrences, First seen, Last seen | Grouped errors |
| Line, Column, File | PHP and JavaScript errors |
| Error level | PHP errors |
| Status, Method | HTTP failures |
| Browser name, version, OS | JavaScript errors |
Message, File, URL and, where one was captured, a stack trace.
Performance impact — for change events, a before/after comparison of page-speed metrics, when ChangeTrace has measurements either side. More →
Related changes — other events close in time, which is often how you spot that three plugins updated together.
What has been removed
Events are cleaned on your server, before anything is sent.
- Sensitive fields are redacted. Around forty key names — passwords, tokens, API keys,
cookies, card numbers, email addresses, phone numbers, names, addresses, postcodes, dates of
birth, whole form payloads — are replaced with
[redacted]. - Email addresses and long digit runs inside text become
[redacted-email]and[redacted-number]. - URLs lose their query string and fragment, so
?token=…and#session=…never travel. - Size is capped at 8 KB per event and 2,048 characters per value; anything longer is truncated or dropped, and the event is marked as capped.
So an event shows you what happened, not who it happened to. A failed checkout tells you the order total and currency, never the customer.
Order events
Commerce events carry only what the metrics need: order id, total, currency, payment method, status. Refunds carry order id, refund id, amount, currency.
No customer name, no address, no email, no line items, no card details. The checkout fields a customer typed are discarded outright rather than filtered.
Why an event you expected is missing
- A PHP notice or warning — not collected, only fatals and user errors.
- A JavaScript error — sampled at ~25%, capped at 5 per page load.
- A change made over SFTP or WP-CLI — waits for the next admin-page load.
- Your very first change after connecting — consumed by baseline establishment.
- An old event — deleted at your plan's history window.