Quick start

This walks the whole path once: create a ticker, write an update, publish, embed it, and close it when the event is over. Ten minutes, and you can throw the result away afterwards.

If a word here is unfamiliar, Core concepts defines all of them.

1. Create a ticker

In the dashboard, go to Tickers and choose New ticker.

Only two fields are required:

Title: what your team calls this feed. Internal.
Type: news, sports, event or other.

The rest is optional and can be changed later:

Public title: what readers see, if it should differ from the internal title. Left empty, readers see the title.
Category: free text. Type a new one and it is created with the ticker.
Team: if the workspace uses teams.
Description: a short note about what this ticker covers.

The ticker is created as a draft. Nothing is public yet, and drafts do not count against your plan.

2. Write the first update

Open the ticker and write in the composer. An update is made of blocks, so one entry can hold a paragraph, an image, a quote and an embedded post together.

Before you save, you can:

Publish it, or keep it as a draft to finish later
Schedule it for a time in the future
Pin it to the top of the feed
Add labels, so readers can filter a long ticker

Write two or three, so there is something to look at in the next step.

3. Publish the ticker

An update being published is not the same as the ticker being published. As long as the ticker itself is a draft, no reader can reach it.

Set the ticker to live. From this moment the feed is served.

This is also the point where the ticker occupies a slot on your plan. Setting it back to draft frees the slot and takes the feed offline again.

4. Embed it

Open Embed on the ticker and copy the snippet. It looks like this:

<script defer
    src="https://cdn.livetickr.io/embed.js"
    id="livetickr-feed"
    data-ticker-id="YOUR_TICKER_ID"></script>

Paste it into your page where the feed should appear. The script renders the ticker exactly where the tag sits, and refreshes itself every 15 seconds. You never touch the page again.

That is the whole integration. There is no iframe to size, no stylesheet to include, and nothing to rebuild when you publish an update.

For the options, the error cases and the domain restriction, see JavaScript embed.

5. Close it when the event is over

When there is nothing left to report, set the ticker to closed.

A closed ticker stays online and readable, so the archive of your coverage does not disappear. It simply stops accepting new updates. If the story picks up again, set it live and carry on.