Checklists

A guide explains one thing. A checklist is several guides ordered into one journey, so a new user can work through everything they need in their first session without you deciding which single guide matters most.

The Checklists page puts it plainly: "Group guides into ordered journeys. New users complete them step-by-step to master your product."

A checklist versus a guide

A guide is one walkthrough made of steps, and it covers one task. Naming your first project. Inviting a teammate. Connecting a data source.

A checklist is a wrapper around several of those guides, in an order you choose. "Your first day in Acme" might be five short guides that together get someone genuinely set up. Each one stays a guide in its own right, with its own steps, its own analytics, and its own behavior rules. The checklist decides the sequence and tracks how far through it someone is.

Nothing is duplicated. A guide included in a checklist is the same guide that appears in your Guides list, and re-recording a step updates it everywhere.

What your users see

Users see a checklist as a floating widget on your product. It lists the guides in order and ticks each one off as they complete it, so progress is visible while they work rather than only at the end.

The empty state on the Checklists page describes it the same way: "Group existing guides into an ordered journey. New users see a floating widget on your product and tick off each guide as they complete it."

The widget is delivered by the pixel, the same script tag that serves your guides. There's nothing extra to install for checklists.

Two states

Checklists have two statuses, Published and Draft. The tabs at the top of the Checklists page are All, Published, and Drafts, each with a count.

There's no archived state, which is the one difference from guides worth remembering. A checklist you've finished with is either still there or gone, so keep drafts tidy rather than accumulating retired journeys.

When a checklist is the right shape

Use a checklist when the guides only make sense together and there's a natural order. First-run onboarding is the obvious case: someone who has just signed up has four or five things to do, and the order matters. It's also the answer when a walkthrough is running too long. A fifteen step guide is where completion rates collapse, and splitting it into three five-step guides inside a checklist usually recovers most of that.

Use separate guides when each one stands alone. Reference material, a walkthrough for a feature only some customers use, or something you want to fire from a specific button or page. Those are better served by a guide with its own trigger on the Behavior tab, so it appears when it's relevant instead of sitting in a list everyone sees.

A useful test: if someone could reasonably do these in any order, or skip four of the five, they're separate guides.

Before you build one

Checklists are built from guides that already exist, so recording comes first. The tip on the Checklists page says exactly that: "Record guides first, then bundle them into a checklist."

Record your five guides, check each one on its own, then group them. Building the journey first and hoping the recordings arrive later leaves you with an empty widget.

Coming soon. Detailed documentation for configuring a checklist, including the creation wizard and the checklist detail page, is on the way. This page covers the concept and what the app states today. For anything not described here, the app is the source of truth.

Next steps

• Create a checklist: What you need in place before you start.

• Record a guide: Checklists are built from guides, so start here.

• Delivery options: How the pixel gets your content on the page.

• Analytics: Completion, drop-off, and feedback per guide.