Skip to content
Jonot Docs

Marketing Content

The Marketing Content add-on lets you show custom messages and images on customer-facing screens while customers wait or after they are served. Content is configured per placement in the admin panel and can be set at the org level or overridden per location.

Enabling marketing content

Section titled “Enabling marketing content”
  1. Open admin.jonot.io/settings/marketing.
  2. Select the placement tab you want to configure (see Placements below).
  3. Choose Text or Image content, fill in the fields, and click Save.

Placements

Section titled “Placements”

Each placement maps to a specific moment in the customer journey. All accept text or image content except where noted.

  • Display idle — the display screen when no ticket is currently being called.
  • Customer waiting — the customer's ticket page while their ticket is in WAITING state.
  • Customer terminal — the customer's ticket page after their ticket reaches a terminal state.
  • Status overlay — the queue join page when the queue is paused or closed. Text only — image content is not accepted for this slot.

Text content

Section titled “Text content”

A text block has:

  • Headline (optional) — up to 120 characters, displayed in bold.
  • Body — 1–280 characters, required.
  • Call to action (optional) — a label (up to 80 characters) and an HTTPS URL. The CTA is rendered as a link below the body text.

Image content

Section titled “Image content”

An image block has:

  • Image — uploaded through the admin panel; must be served from your org's uploads prefix.
  • Alt text — required, up to 200 characters. Used by screen readers and shown when the image fails to load.
  • Caption (optional) — up to 280 characters, displayed below the image.
  • Call to action (optional) — same label + HTTPS URL as for text content.

Org defaults and location overrides

Section titled “Org defaults and location overrides”

Content is resolved in two layers:

  1. Org default — applies to all locations that do not have their own override for that placement.
  2. Location override — takes precedence over the org default for the specific location.

Org-managers can author both org defaults and location overrides for any location in their org. Location-managers can author overrides only for their own location — they cannot modify org defaults.

Scheduling

Section titled “Scheduling”

Each piece of content can have an optional Start and End time. Content outside its scheduled window is not shown. Scheduling is evaluated using the server clock, so it works correctly even on kiosks and displays with drifted local clocks.

Storage quota and cleanup

Section titled “Storage quota and cleanup”

Each organisation has a 500 MB quota for uploaded marketing images. The upload endpoint rejects files that would push your org over this limit.

Uploaded images that are not referenced by any saved content row — for example because you uploaded an image and then closed the tab without saving — are treated as orphans. Orphaned images older than 7 days are removed by an automatic nightly cleanup. This means you can safely re-open a draft within that window; images remain available for the upload preview.

When you replace or delete an image from a saved content row, the previously stored image is scheduled for deletion in the background. Deletion is best-effort — if it doesn't succeed the first time, the nightly orphan cleanup will pick it up.

Section titled “Related guides”