Features / Provider results

Read delivery history as the provider reported it.

PostDesk receives provider events and attaches them to the queued message. Accepted, delivered, bounced, and complaint states appear exactly as the provider reported them.

Provider outcome timeline

Example data · source retained

Live record

2,416

Queued

2,398

Accepted

2,341

Delivered

18

Bounced

Audience

Knownry snapshot #K-184

Content

Template version 6

Provider

Outcome import #P-441

In practice

Follow one send from start to finish.

  1. Stage 01

    Match the provider event

    The provider message reference connects an incoming event to the workspace, queue item, and send attempt that produced it.

  2. Stage 02

    Keep the event sequence

    Each provider update is stored as a new event, so the full history stays on the message.

  3. Stage 03

    Protect later sends

    Hard bounces and complaints can add a suppression that holds the address back from later queues.

After provider handoff

Accepted, delivered, and read are three different claims.

A provider accepts a message, later reports delivery, and then sends a complaint event. PostDesk retains that sequence on the queue item, creates the suppression, and labels each event as the provider reported it.

Provider events
Accepted → delivered → complaint
Attached to
One queued message
Follow-up
Address suppressed

The retained record

What stays with the provider result

  • The provider event type and provider message reference
  • The queue item and send attempt the event belongs to
  • When PostDesk received and processed the update
  • Any suppression created from a bounce or complaint

Why keep it

Provider events can arrive later and out of order. Keeping the event history beside the original queue item gives the team the evidence needed to separate a delivery problem from an audience or template problem.

What you can rely on

PostDesk shows exactly what Resend, SendGrid, or SES reported, and names the provider on every event.