Skip to main content

Completion conditions

Completion conditions determine when checklist items get checked off. It’s like grading your users. Do it too frivolously and users can breeze through your checklist without learning anything. Too strict and users might abandon your checklist altogether.

Completion condition types

CTA clicked

This is the simplest trigger, which causes the item to complete when the user clicks the CTA for the item in the checklist. Although this is the least robust trigger since it allows the user to complete the item without taking an action in your app, it can be appropriate for certain scenarios. For example, you could tell the user some key information about how they should use your app with the checklist item’s title and description, and the CTA could be “Let’s go!”. Upon clicking this, they would then move onto the next checklist item.

Page visited

Page visits are another way to trigger item completions in checklists. When the user visits a page, it’s possible to have an item complete. For example, a checklist could nudge a user to check out their profile page — once they visit the page, the checklist item will be checked off.

This works best when the CTA action for your Item doesn’t directly take the user to the page — if you do this, you might as well use a CTA clicked condition. Instead, use this one when your checklist item describes how to get to the page in question, but doesn’t take the user there directly. This way, the completion rewards the user’s quest to find the page.

Element clicked

It’s also possible to track element clicks and use them to trigger item completions. To do this, you can record a button press using our click recording tool — click the little icon to the right of the element selector to get started.

This can be paired with other nudges to build powerful user onboarding experiences. For example, you can set the CTA action to trigger a tour that walks users through a flow. Let’s say the final step of that flow involves pressing a button, like “Submit”. You can make clicking on that element the condition that checks off the checklist item.

When an event is tracked

Using events, it's possible to trigger checklist item completions when the user performs an action within your app or within CommandBar. These can include events being fired from an analytics tool, or custom events you create specifically for CommandBar. Events can capture more nuanced milestones, like when a user uses a feature or creates content in your product. If you have them, they are often the right choice for completion conditions.

When conditions are met

This is the most general trigger, and allows you to trigger item completions using complex conditions incorporating Who/Where/When conditions. Explore this option if you can’t figure out how to construct your completion condition using the other approaches.

Action executed

Another trigger can be an action execution. This allows your users to trigger completions for checklist items by executing actions, from Spotlight or Copilot. Since actions can also perform actions within your app (using requests or callbacks), this trigger can be easy to set up, and will also perform actions within your app.