Timers for EmailDocumentation
Back

Test before sending

Send a test email and check animation, timing, image loading and caching.

Send to Email

On the information page, choose Send to Email, enter a destination you control and select Send Test. A success message means the application submitted the test message; it does not guarantee delivery into the inbox.

The message uses the public timer image. Requests from the recipient application or its proxy may count as views. This is different from the private dashboard preview.

This test checks the hosted timer, not every detail of your final campaign layout. Also send a test from the email platform after pasting the final HTML.

Pre-send checklist

  1. Confirm the team, timer name, deadline and fixed UTC offset.
  2. Check the countdown and the chosen expired state.
  3. Test the background and text contrast in light and dark email surfaces.
  4. Check the final width on desktop and mobile.
  5. Inspect both animation and the first frame.
  6. Confirm the image URL is public and uses the production timer domain, not localhost.
  7. Check the team's remaining view allowance.

The image does not load

Some email applications block remote images until the recipient allows them. Verify the public URL separately, check that the timer still exists, and confirm that your email platform did not rewrite it into a private attachment.

A local development address cannot be reached by a remote mailbox. Copying a working localhost URL into an email does not make it public.

The timer is a still image

The list view intentionally uses a single-frame preview. In email, the client may show only the first frame or a cached image. The team's quota rules can also stop animation. Check usage before changing the design.

The timer looks old after an edit

The public URL is stable after an update, but mailbox caches and image proxies can keep older content. Saving again or refreshing the dashboard cannot force a recipient's provider to discard its cached image.

The count does not match people opening the email

A view is an eligible image request, not a unique person. Prefetching, proxies, repeat requests and caching can all affect the relationship between requests and human opens. Use timer analytics as image-delivery usage, not proof that a particular recipient read the message.