Skip to content
CountdownFlow Help Sign in

The pre-launch and post-launch checklist

Catch deadline, identity, layout, destination and publication mistakes before customers see them.

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.

Before publishing

  • Confirm the correct workspace and an internal name that identifies this promotion.
  • Check the timezone, start policy, end date or duration and any hard-stop deadline.
  • Preview the saved design at a realistic email or mobile width. Make sure digits, labels and the offer headline are readable.
  • Test the waiting, live and expired appearances where the preview controls allow them.
  • Use working HTTPS live and closed destinations. Check that your store independently honors the advertised deadline.
  • Check any plan warnings. Resolve restricted settings rather than assuming the editor preview means public delivery is allowed.
Visual countdown designer with controls and the rendered timer preview
In the application Use the design controls and preview together. Save your design when it looks right; previewing a change alone does not publish it. View full-size screenshot (opens in a new tab)

Test the actual channel

  1. 1Publish the campaign and, if applicable, publish the connected landing page.
  2. 2Email: send a real test through your email provider so its merge tags and image proxy are involved. Website: load the embedded page outside the builder editor.
  3. 3Evergreen: test two different opaque identities. Revisit with the first identity and confirm it retains its original deadline.
  4. 4Follow the countdown link. Verify both the live and closed paths with a short-lived test campaign rather than altering a running customer promotion.
  5. 5If tracking is enabled and permitted, confirm an appropriate event is recorded. Do not interpret an image request as proof of a human read.
Website publishing screen with the countdown delivery controls
In the application Use the website code generated for your campaign. Test it on your published website, not only inside the website builder. View full-size screenshot (opens in a new tab)

After launch

Monitor campaign availability, recorded activity and integration failures. Keep a note of the campaign ID, publication time and configuration changes so a later issue can be explained.

If you correct a live design, verify a new request and allow for email caching. If you change the offer deadline, communicate the change honestly; a timer should not repeatedly reset in a way that misleads customers.

Related articles

Add a countdown to an email newsletterEmbed the generated HTML, choose PNG or GIF, and test real inbox behavior. Embed a live countdown on a websitePlace the generated website code, preserve identity and diagnose builder or script restrictions. Understand countdown analytics and conversionsRead activity reports without confusing image requests, visitors, clicks and completed purchases. Fix a wrong deadline, reset timer or unexpected closed stateDiagnose timing issues in a clear order instead of repeatedly changing the campaign.