Skip to content
CountdownFlow Help Sign in

Embed a live countdown on a website

Place the generated website code, preserve identity and diagnose builder or script restrictions.

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.

Copy the website code from the campaign

  1. 1Save and publish the campaign, then open its website publishing option.
  2. 2Copy the generated embed code from that campaign. This includes the correct campaign references and script URL.
  3. 3Paste it into a Custom HTML or code area that allows the supplied script. Place it where you want the timer to appear, then save and publish your website.
  4. 4Load the public website outside the builder editor. Test mobile sizing, the live state and the expired state.
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)

Why the public page matters

A website builder’s editing canvas may disable scripts or use a different iframe environment. A working editor preview is not proof of a working public page, and a blank editor preview is not always proof that the embed is broken.

If your builder strips script tags, use its supported code-injection mechanism or another supported countdown delivery channel. Do not paste JavaScript into an ordinary text block and expect it to execute.

Cross-channel evergreen consistency

If a recipient arrives from an email, keep their opaque vid value and any required send-deadline fields from the generated link. Stripping those parameters can make the website use an anonymous visitor window instead.

A public embed is not a place for an API key. Use the campaign’s public references, keep administrative credentials on your server and avoid private customer data in URLs.

Security policies and page caches

Content Security Policy, consent managers, browser extensions or mixed-content blocking may stop the countdown script or its network requests. Keep the page and referenced resources on HTTPS and ask your website administrator to allow the required countdown origin.

After a saved change, inspect a fresh public load. A page builder’s own cache can keep old markup even when the campaign is correct. Do not change the campaign deadline repeatedly to diagnose a script-loading problem.

Related articles