Analytics and Logs
PING8 separates performance analytics from operational audit logs.
Campaign analytics
Campaign analytics show:
- Queued
- Delivered
- Deferred
- Bounced
- Expired
- Complained
- Delivery rate
- Open rate
- Click rate
- Bounce rate
Use the time range selector to inspect a specific campaign period.
Provider analytics
Provider tables group performance by recipient mailbox provider. Use this to spot provider-specific throttling or reputation issues.
Operation logs
Operation logs show administrative activity:
- Logins
- Domain changes
- Group updates
- Template changes
- Campaign creation
- Send API changes
Use operation logs when you need to answer who changed something and when.
Error logs
Error logs help diagnose backend and service failures. Use them together with task failure details and delivery-engine logs.
Reading failures
Failure details may include:
- Recipient
- Provider/domain
- DSN or SMTP status
- Relay
- Delay reason
- Provider response
- PING8 guard or validation result
If details are generic, check the delivery engine path. KumoMTA events, local Postfix queue logs, and SMTP provider responses can differ.
Operator questions logs answer
| Question | Where to look |
|---|---|
| Who changed this domain or template? | Operation logs. |
| Why did a recipient fail? | Task failure details and provider analytics. |
| Did KumoMTA report back? | Runtime webhook counters and Kumo event troubleshooting. |
| Was this recipient suppressed? | Contact suppression and failure details. |
| Did engagement tracking work? | Campaign analytics and tracking settings. |
Common mistakes
- Reading error logs before checking the task-specific failure details.
- Ignoring operation logs during incident review.
- Comparing analytics windows that do not include the send time.
- Assuming missing opens means no recipients read the email.