Delivery Tracking and Read Receipts

What the delivery report shows per person, how a status moves, and why prelim and full sends are counted apart.

6 min readUpdated August 2026

One Row Per Person Per Channel

Every send writes a tracking row for each recipient on each channel it used. Text and email are recorded apart, because reaching somebody by one and missing them by the other is a different situation from reaching them twice. The report groups by person and shows both.

StatusWhat it means
QueuedHanded to the provider, nothing back yet
SentThe provider accepted it
DeliveredIt reached the handset or the mailbox
OpenedThe email was opened, or the call sheet link was followed
ClickedA link in the message was followed
BouncedThe mail server rejected it
FailedThe carrier or provider could not deliver it
No addressNothing to send to. Different from nothing sent
Interactive Demo
Send and Delivery Report
Send a prelim to the approvers, then the full sheet to the unit. Watch both channels report per person, including the one number that will never work.
Recipients
Dana Whitfield
Producer · 8:00A
Pending
Luis Ferrer
UPM · 7:00A
Pending
Mike Rodriguez
Director of Photography · 7:00A
Pending
Sarah Chen
1st AC · 6:45A
Pending
Tom Walsh
Gaffer · 6:30A
Pending
Emily Park
Script Supervisor · 7:00A
Pending
Message Preview
(555) 234-5678

G-Casper Pro

Mike Rodriguez, your call for "SUNRISE STUDIOS" on Day 15 (Fri, Mar 15) is:

7:00A

View full call sheet: gcasper.pro/cs/abc123

Not sent

Statuses Only Move Forward

Providers do not deliver their webhooks in order. A late "delivered" arriving after an "opened" would otherwise walk somebody backwards. The merge refuses that move, so a row that reached Opened stays there.

Important: A bounce that lands after an open is the provider catching up, not the message failing. Nobody opens mail they never received. The report will not draw a red line under a row that reads Opened.

Machine Opens

Apple Mail Privacy Protection and similar services fetch the tracking pixel before the person has seen anything. Counting that as an open would inflate the number and, worse, lock the row above any later bounce. G-Casper Pro records it as delivered instead. The message reached the mailbox, which is all it actually proves.

Tip: A high delivered count and a low opened count on an email-heavy unit is usually privacy protection rather than crew ignoring you.

Prelim and Full Are Counted Apart

A prelim goes to the producer, the UPM and whoever else signs off. The full sheet goes to the unit. Rolling both into one list makes a day look distributed when only four people have seen it. The report separates them and labels which send it is showing.

Important: Sending a prelim does not mark the day as distributed. That is deliberate. The AD Control Center still shows the day as not sent until the full send goes out.

Counts Are Cumulative

An opened message is also a delivered one. The roll-up counts it in both. Reporting them exclusively is what once showed a fully delivered send as "3 delivered" the moment opens started arriving.

Reviewing a Different Day

The report owns its own day selector. You can read Day 3's delivery while drafting Day 5 without moving the app's selected day. Filters cover channel, status, and a search across name, department and address.

Reconciling

If a webhook never arrived, Reconcile asks the provider directly and replays the message history for that send. A reconciliation walks the whole history in one pass, which is exactly why the forward-only rule exists.

Tip: Reconcile before you chase anyone. A status that looks stuck is often a webhook that got dropped between the provider and us.

FAQFrequently Asked Questions

Was this article helpful?

Let us know if this answered your question.

Related Articles

Still have questions?

We're here to help you get the most out of G-Casper Pro.