Fixing email countdown display issues
Trace and repair errors related to personalization, static images, and countdown movement in emails.
2 min read
Screenshots use fictional demo data. Your controls may differ by plan, role, or environment. Use the values generated in your own workspace.
Fixing missing images
- 1Verify that the campaign is published and not restricted by a plan notice.
- 2Ensure the generated HTML is placed in a code or HTML block rather than as plain text.
- 3Inspect the sent message source to see if the email builder modified or stripped the image URL.
- 4Enable remote images in your email client and perform a new real test send.
- 5Confirm that the image's HTTPS host is reachable and, if using a custom domain, that it is fully activated.
Troubleshooting frozen timers
PNG files are static snapshots, not animations. GIFs have a finite clip length, and some email clients only display the first frame. Furthermore, mail proxies may cache either format. Test the public page for a live, ongoing display rather than relying on an image fetched by an inbox cache.
Correcting personalization errors
- 1Perform a real send to a contact with populated fields instead of using an editor-only sample.
- 2Verify that the provider successfully replaced every tag within the image and smart-link URLs.
- 3Check the supported countdown_id/contact ID recipe and ensure that identities differ across contacts.
- 4Use countdown-artwork placeholders only in supported text fields and retain provider merge tags in your workflow.
- 5Test a contact lacking optional fields to ensure readable fallback copy appears.
Resolving incorrect expired displays
Request a fresh asset and verify the server-calculated state. An old email response may remain cached after expiry. Use a closed destination URL on your smart link and enforce the offer deadline at checkout so a cached image cannot authorize a late purchase.
Interpreting pre-send analytics spikes
Provider previews, image preloading, privacy proxies, and security scanners can trigger requests. Recorded image requests are not verified human reads. Compare the specific event type and timing before assuming a recipient opened the message.