Fix missing, frozen or unpersonalized email countdowns
Check generated HTML, image loading, merge tags, GIF support and mail caching.
2 min read
Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.
Nothing appears in the email
- 1Confirm the campaign is published and has no blocking plan notice.
- 2Check that the generated HTML is in a code/HTML block, not displayed as literal text.
- 3Inspect whether your email builder rewrote or removed the remote image URL.
- 4Allow remote images in the receiving mail app and test another real inbox.
- 5Confirm the referenced HTTPS host is reachable and, for a custom domain, correctly activated.
The digits stop moving
A PNG is a snapshot, not an animation. A GIF has a finite clip length and some clients display only its first frame. A mail proxy can also cache either format. Test the published website/public page for an ongoing live display rather than expecting a previously fetched inbox image to refresh forever.
A name or recipient window is wrong
- 1Use a real send to a contact with populated fields rather than an editor-only sample.
- 2Inspect whether the provider replaced every tag in the image and smart-link URLs.
- 3Check the supported countdown_id/contact ID recipe and make sure identities differ across contacts.
- 4Use countdown-artwork placeholders only in the supported text fields, and keep provider merge tags in the sender-generated workflow.
- 5Try a contact missing optional fields to verify readable fallback copy.
The expired image still shows an offer
Request a fresh asset and check the server-calculated state. An old email response can remain cached after expiry. Use a closed destination on the smart link and enforce the real offer deadline at checkout so a cached illustration cannot authorize a late purchase.
The analytics show opens before the send or human view
Provider previews, image preloading, privacy proxies and security scanners can generate requests. Recorded image requests are not verified human reads. Compare the exact event type and timing before concluding a recipient opened the email.