Sending Lifecycle
PING8 separates attempt progress from delivery outcome.
Task progress means PING8 has processed recipients for a task. It does not mean every recipient received the email in their inbox. Inbox delivery is measured through delivery lifecycle events.
Lifecycle states
| State | Meaning |
|---|---|
| Pending | The message is waiting to be prepared or queued. |
| Queued | The delivery engine accepted the message for sending. |
| Accepted | The downstream mail path accepted the message for delivery attempt. |
| Delivered | The recipient provider accepted the message. This still does not guarantee inbox placement. |
| Deferred | The recipient provider temporarily delayed the message. |
| Bounced | The recipient provider rejected the message permanently or after retries. |
| Expired | The delivery engine stopped retrying after the retry window. |
| Complained | A complaint event was received from a provider or feedback path. |
| Suppressed | PING8 skipped the recipient because of unsubscribe, bounce, complaint, or suppression rules. |
| Opened | An open tracking pixel was loaded. |
| Clicked | A tracked link was clicked. |
How to read campaign progress
Use these rules:
- Progress tells you how much of the task has been attempted.
- Success / Failed should come from delivery telemetry.
- Analytics explains provider-level delivery, engagement, and failure behavior.
- Failure Details shows why recipients failed or did not receive telemetry.
What success looks like
For a healthy first send:
- The test send queues successfully.
- A lifecycle event appears for the recipient.
- Delivered, deferred, bounced, or suppressed counts update.
- Failure details show provider responses when a message fails.
Common mistakes
- Assuming
100%progress means inbox delivery. - Launching a full group before one-recipient telemetry is confirmed.
- Ignoring deferred messages too early; some providers retry later.
- Treating opens as exact counts. Privacy features can block or prefetch pixels.