A Checklist is a persistent list of tasks that checks items off as users complete them. Use one for onboarding, feature adoption, or setup to-do lists. The whole Checklist is built on one page in the App: its items, look, and targeting, next to a live preview.

Before you start

• Pick the tasks. A Checklist holds up to 10 items, and shorter lists get finished more often.
• For each item, decide what counts as done: the user clicks it, a Flow starts or finishes, or the user matches rules such as an event or a user property.
• If an item launches a Flow, build and publish that Flow first. To keep the Flow from showing on its own, set its trigger to Only manually. See Configure an experience's settings.

Create the Checklist

1. Click Experiences > New experience. The New experience wizard opens.
2. Select Web, then Checklist.
3. Enter a Name. Only your team sees it.
4. Optionally, pick a Campaign Tactic to add the Checklist to.
5. Click Continue. The Checklist page opens, with the settings on the left and a live preview on the right.

Changes save as you make them. The preview's status shows Saving…, then Saved. Saved changes stay in the draft until you publish.

Set how the Checklist opens

In Details, answer How should the checklist appear by default?:

• Open once, then collapsed: opens the first time someone sees it, then shows as a beacon after that. This is the default.
• Collapsed: shows only the beacon until someone clicks it.
• Open: shows the list open.

Add items

1. In Items, enter the Heading and Description shown at the top of the list.
2. Click Add item. A new item opens for editing.
3. Enter the Label: what users see in the list. Write it as a task, such as "Invite a teammate".
4. Under When clicked, choose what the item does:

• Go to a page: enter a Page URL. Start it with https:// for another site or / for a page on this one. Turn on Open in a new tab if needed. To include a user property in the URL, wrap its name in two curly braces, such as https://example.com/accounts/{{account}}. See Personalize Flows.
• Launch a flow: pick the Flow. To send the user somewhere first, turn on Go to a page first and enter the URL.

5. Under Mark complete when, choose what checks the item off (see the next section).
6. Repeat for each item. Use the up and down arrows on an item to reorder it.

To make users finish items in sequence, turn on Complete items in order. Each item unlocks once the one before it is done. The toggle needs at least two items.

If you leave When clicked empty, the item does nothing when clicked. The item row says Does nothing when clicked.

Choose what completes each item

The options under Mark complete when depend on the item's action:

The user matches rules confirms the user did the task, so prefer it over The item is clicked. For example, "Add a teammate" can complete when the added_teammate event fires. To track a click as an event without code, see Click to Track.

A legacy Flow can only complete when it starts, so The flow is completed isn't offered for it. Completion happens when the Flow's first step shows. If that step is a Tooltip or Hotspot, the user has to interact with it before the item checks off.

Completion is tracked per user, not per account. To let anyone on an account complete an item, see Create Checklist items that can be completed by anyone on an account.

Choose who sees it and where

Who sees this and Where this appears work the same way as for other experiences: audience rules, page URL rules, and domains. See Configure an experience's settings.

Patterns that come up often with Checklists:

• After a welcome Flow: target users who completed the welcome Flow. The Checklist also stays hidden while any Modal or Slideout is on screen.
• One Checklist after another: target the second Checklist to users who completed the first.
• One Checklist per role: create one per role and target each to a different role value. Keep the rules mutually exclusive.
• A/B test two Checklists: target each to one half of the audience_randomizer property, such as greater than 50 and less than or equal to 50.
• Test with your team first: target users whose email contains your company domain, publish, test, then switch to the real audience.

Style the Checklist

In Style:

• Brand color colors the beacon, the progress bar, and items on hover.
• Theme applies one of your themes, or No theme.
• Font uses Checklist default or Custom. For Custom, enter the CSS Font family and a Font URL for the stylesheet that loads it, such as a Google Fonts link. See Loading Custom Fonts for Checklists.
• If you see More colors, set the Background color, Text color, and Item hover color.

In Beacon, set where it sits (Bottom left or Bottom right), the Beacon text (up to 20 characters), and the Beacon text color. To move it off the corner, open Adjust position and set From the side and From the bottom in pixels. The preview ignores these offsets, so check the position in your app after publishing. See Preview and test your Checklist.

Set the finish and dismiss screens

In When everything is done, set what users see after the last item:

• Pick an image under Which image celebrates the finish?: No image, Checklist icon, an emoji, or your own upload.
• Edit the Title, Message, and Button text.
• Set the Success color, which colors completed items and the title.

In Dismiss, turn on Let people dismiss the checklist to add a link that hides it for good once the user confirms. Edit the Link text, Confirmation question, Cancel button, and Confirm button. With the toggle off, the Checklist stays until the user finishes every item or you unpublish it.

Click into either section and the preview switches to that screen. You can also switch it with List, Completed, and Dismiss above the preview.

Publish

Publish from the Checklist's page. See Publish, schedule, and unpublish an experience. Checklists can't be scheduled.

Confirm it worked

1. Open your app as a user who matches Who sees this, on a page that matches Where this appears.
2. The beacon shows in the corner you chose. If you picked Open or Open once, then collapsed, the list opens on the first visit.
3. Complete one item. It checks off and the progress bar moves.

If the Checklist doesn't appear

Click Audiences > Users, open the user, and go to the Eligibility tab. See Find and inspect users.

Enter the page in Page URL and click Check page.

If the Checklist shows Not eligible, click See why. Audience not met means the audience rules exclude the user. Page not met means the URL or domain rules exclude the page.

If a Modal is on screen, the Checklist waits until it closes.

If an item won't check off

• The user matches rules: open the user's activity and confirm the event fired or the property has the value you expect. Property values are case-sensitive. See Read a user's activity.
• Launches a legacy Flow that starts with a Tooltip or Hotspot: the user has to interact with that first step.
• The Flow is archived, unpublished, or empty: the item editor shows a red warning. Choose another Flow or publish the one you picked.
• "Completion still points at the removed flow": the Flow was deleted. Choose another Flow or another completion option.

If targeting says "Edit it in classic Studio"

Who sees this and Where this appears show "This checklist's targeting was set up in a way this page can't edit yet" when the rules use something this page has no control for. These rules can't be edited from the Checklist page yet. Contact support with the Checklist's URL and we'll help you change them.

If the Checklist disappeared for a user who didn't finish

Check whether the user dismissed it: look for a Checklist dismissed event in the user's activity. If dismissing is off, check that the user still matches Who sees this. A property that stops being sent can drop them out of the audience.

Still stuck?

Collect the following and contact support:

• The Checklist's URL, copied from your browser's address bar. It contains the Checklist ID.
• The affected user's User ID.
• The page URL where the issue happens.
• A screenshot of the user's Eligibility tab, or of the failing item's Mark complete when settings.