What actually happens when a countdown lands in someone's inbox

A countdown in an email looks like the simplest thing in the world. It is a picture of a clock, and the clock goes down. What makes it awkward is that you are not putting it on a page you control. You are handing it to a few hundred different mail apps, each of which will treat it slightly differently, and some of which will look at it long before the person you sent it to does.

None of that is a reason to avoid them. It is a reason to set them up so the edge cases work in your favour instead of against you.

An email cannot count

A website can run a clock. It ticks in the browser, in front of the person reading, and it is right to the second.

An email cannot. Mail apps do not run that kind of code, and the ones that tried stopped years ago for good reasons. So a countdown in an email is a picture, an animated one, and the only moment it can be correct is the moment it is requested. Everything interesting follows from that.

The picture is built when someone's mail app asks for it. If they open your message four days after you sent it, they get a picture built four days later, showing four days less. That part works exactly as you would hope, and it is what makes the technique worth using at all.

Three things that get in the way

Images that are blocked

Plenty of people read mail with images turned off, and some see them only after clicking “display images”. If your deadline lives only in the picture, those readers see nothing at all.

The fix is not technical. Put the deadline in the text of the email as well. The timer is the thing that creates urgency; the sentence is the thing that survives.

Images that are cached

Some mail providers fetch your picture once and keep a copy for everyone. Some fetch it fresh every time. You do not get to choose, and it varies by provider and sometimes by account.

Where it matters most is a message read repeatedly over several days. The first view is right. A later one might be showing what the provider kept. That is the strongest argument for keeping the deadline in the copy too, and for not writing sentences like “you have exactly the time shown below”.

Opens that are not people

Apple Mail Privacy Protection, and several corporate mail filters, open messages before any human does. They fetch the images to check them and to hide the reader's location. That means a picture can be requested minutes after you press send, by nobody.

This costs you nothing directly. But if you are watching how often a timer was displayed, part of that number is machines. Treat it as a rough signal of delivery rather than as a count of readers.

What the big three actually do

The three problems above are general. How hard each one bites depends on which app your reader opens, and most lists are dominated by the same three families. Here is what each one actually does with a countdown.

Gmail: timers work, through a middleman

Yes, Gmail supports countdown timers: animated images play in the web app and in the phone apps. What Gmail adds is a middleman. Every picture in every message is fetched through Google's own image servers, not directly from the sender, and that proxy may keep a copy. The first open is fresh; a message re-opened across several days may be looking at what Google kept. That is the caching problem above with a name on it, and the answer is the same: the sentence next to the timer does not cache.

One Gmail habit of its own: long, heavy messages get clipped, with the rest hidden behind “view entire message”. A timer sitting below the clip is a timer nobody sees. Keep it in the top part of the email, which is where a deadline belongs anyway.

Outlook: two Outlooks, and one of them does not animate

“Outlook” is two different programs wearing one name. Outlook on the web, on the Mac, on phones, and the new Windows app all play animated timers normally. The classic Windows desktop Outlook, still standard issue in many offices, renders email with Word's engine and shows only the first frame of any animation.

For a countdown built properly this is quieter than it sounds. The first frame is drawn at the moment the message is opened, so it shows the correct remaining time; it just stands still. Which explains a complaint you may recognise: a timer in Outlook showing the wrong time is very often a timer that was right when the reading pane first fetched it, an hour ago, and has not moved since. The reader saw a snapshot, waited, and blamed the clock.

The practical consequences: never write copy that depends on the animation (“watch the clock run down”), and if your audience is corporate, assume a still picture and let the surrounding text do the urgency. Corporate mail also runs security scanners that fetch images before anyone reads them, which is part of the machine opens story above.

Apple Mail: the best renderer, with a privacy twist

Apple Mail draws email better than almost anything else, and timers animate exactly as designed. The twist is Mail Privacy Protection, which most Apple users switched on years ago. It fetches a message's images through Apple's relays when the message arrives, not when the person reads it, both to hide the reader's address and to stop senders learning open times.

For a countdown that means two things. The phantom opens above: a large share of Apple opens happen minutes after sending, performed by nobody. And a freshness gap: the picture the reader eventually sees may have been fetched hours before they looked, so the timer can show more time remaining than is true. Near a deadline that gap matters, and it is the strongest single argument in this article for the rule that never fails: the deadline lives in the text, and the timer makes it felt.

Round down, never up

Here is a small decision that matters more than it looks.

When a timer has 3 hours, 59 minutes and 40 seconds left, it can round to “4 hours” or to “3 hours 59 minutes”. We always round toward less time remaining.

The reason is that the two ways of being wrong are not equally bad. A timer that says slightly less than the truth expires a few seconds early, and nobody notices. A timer that says slightly more can still be counting down after your sale has closed. Somebody clicks through to a page that tells them they are too late, having just been shown they were not.

When a countdown is wrong, it should be wrong in the direction that keeps its promise.

When it hits zero

A timer that reaches zero should stay at zero. It sounds obvious, and it is the detail that is most often got wrong: an animation that loops will roll back to the beginning and start counting down again, so a person opening your message an hour after the deadline sees a fresh countdown promising them another day.

Ours stops, holds the expired state, and stays that way. Which brings up the question of what the expired state should say. “Offer ended” is honest and final. Something softer usually does more, “this offer has closed” next to a link to your current one, because the person opening late is still a person who opened.

A short checklist

• Put the deadline in the text as well as the timer.
• Say what time zone you mean, if the deadline is a date rather than a duration.
• Send a test to yourself, in the app your readers actually use, and look at it.
• Assume some readers see a still snapshot rather than an animation, and write so the email still works for them.
• Decide what the expired version should say before you need it.
• Do not promise accuracy to the second. Promise a deadline.

None of this is difficult. It is mostly a matter of deciding, once, that the timer is there to create urgency rather than to be a clock, and then writing the email so that it still makes sense to somebody whose mail app never showed them a picture at all.

This article is one chapter of a larger story. For the rest, from adding a timer to your campaign to using urgency without spending trust, see the complete guide to countdown timers for email.