The Send Log Said Done. The Counter Said Six.

On Saturday night I told thirty four people their book was coming Sunday.

Sunday night it went.

Monday morning I did the part almost nobody does. I went and looked at whether it landed.

Six people had clicked. Two of those clicks arrived broken.

That is what I actually know. Everything past that is a guess, and I am not going to dress a guess up as a delivery.

The plain English version

Sending is not delivering.

Your email tool will tell you a campaign went out. It will show you a green check and a number. That number measures your effort. It does not measure whether a single human being ended up holding the thing you promised them.

There is almost always a second table somewhere that knows the truth. A download counter. A login record. A first-use timestamp. Something on the other end of the promise that only moves when a real person does something real.

Find that table. Read that table. That is the whole lesson.

Why it matters if you sell anything digital

If you sell a PDF, a course, a template, a recording, a membership, a file of any kind, you have a delivery step that can fail quietly.

Quiet is the dangerous part.

A failed charge screams. Your card processor emails you. A failed delivery says nothing. The customer paid, the send log is green, and the buyer is sitting there wondering if you took their money and disappeared.

They do not email you. They just decide what kind of person you are.

The receipt

FACT. Thirty four people have paid for the digital edition of Fighting Shadows. $628.30. The first order was June 6, 2026. The most recent came in September 13, 2026.

FACT. An email went out from updates@realryannichols.com on September 13 at 12:32 AM Central saying PDF delivery would begin that night.

FACT. The first download link was requested September 13 at 8:34 PM Central. Delivery happened. That part worked.

FACT. In the forty eight hours around it, eight different download addresses were requested on the site.

Six of those eight matched a real paid order.

Two matched nothing at all.

The two that matched nothing

This is the part worth stopping on.

A download link on my site ends in a forty eight character key. One key, one buyer, one book.

Two of the requests came in carrying a key that was thirty six characters long, and thirty five characters long.

Cut off. Short. Pointing at nothing.

And here is the tell. Each short one fired within one second of the full version of the exact same key, from the same reader.

DOCUMENTED INFERENCE. That is what a long link looks like when something in the middle cuts it. An email client wrapping a line. A preview scanner grabbing half. A copy and paste that stopped early. I cannot prove the cause from my own site data, so I am labeling it, not asserting it.

In both of those cases the full link also fired, so those two readers got through. They got through by luck, on the second try, in the same second.

A link that only works on the retry is a link that is going to fail somebody.

Four counted. Two did not.

Of the six requests that matched a real order, four moved the download counter on that order.

Two did not move it at all. Request came in, counter stayed at zero.

NEEDS AUTHENTICATION. I do not yet know whether that is a counter that failed to increment or a download that failed to complete. Those are two very different problems and I am not going to pick one before I know.

But notice what both of them have in common. If I had only read the counter, I would have said four. If I had only read the traffic, I would have said eight. Neither number is right, and I would have believed whichever one I looked at first.

What this does not prove

It does not prove twenty nine people got nothing.

It has been less than a day. People buy a book at midnight and open it Thursday. Most of these orders are months old and the buyer has been waiting patiently. A lot of them have not looked at their inbox yet.

It does not prove the email failed to send. I have no evidence of a bounce. I checked forty eight hours of mail and there is not one.

It does not prove any particular person was left out. I am not naming anybody and I am not counting a single human being as a failure this early.

What it does prove

It proves I do not currently have a way to confirm delivery for twenty nine paying customers, and I did not know that until I went looking.

It proves the link is fragile enough to arrive cut in half at least twice in one night.

It proves the number I would have reported, if I had trusted the send, would have been wrong in both directions at once.

And it proves the thing I keep saying and keep having to relearn.

Delivery is not demand. A send is not a delivery. A green check is a measure of what you did. The counter on the other end is a measure of what happened.

What I am doing about it

I am not going to sit here and tell you I have it solved this morning. I do not.

Here is what is actually on the list.

Shorten the link so it cannot be cut in transit, and make a short human readable code work as a backup for anybody whose link arrives broken.

Make the counter and the completed download two separate records, so I can tell the difference between somebody clicking and somebody actually holding the file.

Put a plain page behind it that says who you are and what you bought, so a buyer with a broken link has somewhere to land instead of a dead end.

Then send a second, quieter email to anybody whose counter never moved. Not a pitch. A door.

That is the order. Smallest fix first, and every one of them is checkable the next morning.

If you sell something, do this today

Do not take my word for any of it. Go do the thirty minute version on your own business.

Write down the promise. The exact one. What does a customer get, and when.

Find the table that records the receiving end, not the sending end. It exists. It is a download count, a first login, a file opened, a course started, a shipment scanned.

Pull one number. How many people who paid have actually taken the thing.

If that number is lower than the number who paid, you found the leak, and you found it before your customer had to tell you.

If you cannot find that table at all, that is the bigger finding and it is the one to fix first. You cannot improve a delivery you cannot see.

The bottom line

I promised thirty four people a book.

I sent it.

Six clicked. Two of those arrived broken. Four counted.

That is the honest number, on the record, the morning after, with my name on it.

I would rather publish a number that is uncomfortable than a number that is flattering and made up.

The send log is a story you tell yourself. The counter is what happened.

What to do with this

Do not threaten anyone. Do not harass anyone. Do not contact anyone in my name.

If you bought the digital edition and your link did not work, reply to the email or text (903) 500-8898 and I will get you the file. That is it. No hoops.

If you run a business and you just realized you have no idea whether your customers are receiving what they paid for, that is the exact kind of thing I fix. Here is how to hire me.

If you have not read the book yet, it is here.

Read it. Share it. Put eyes on the record.