Preview

Preview mode is always available while you're building your checklist. It's great for quickly walking through the content as an end-user would, allowing you to quickly review what your Checklist will look like, but it's limited to the view in the Appcues dashboard. For advanced testing, please keep reading.

Publish to a staging environment

Publishing is the best way to test your content. If you have a staging/internal environment that you can use, then you can publish the Checklist in that environment.

What you can do with publishing to an internal environment

• Test whether user properties/events are working correctly.
• See how the Checklist interacts with your app.
• Test Flows triggered from the checklist

To publish to an internal environment:

First, add your staging environment to the Available Domains list in your settings (must be admin).

Then, in your ‘Page targeting’ settings for your Checklist, choose your internal or staging environment from the domains list:

After that, you can then publish your Checklist. Doing so will publish the Checklist safely to just the internal environment, where your end-users won’t be able to see.

This approach does put the Checklist live, but it requires you to have a safe internal environment. If this doesn't exist, there is another approach that consists of testing it live for yourself or a set of internal testers. We'll cover that below.

Publish to internal testers or yourself (Restrictive Publishing)

If you're lacking an internal/staging environment, another approach that will still allow you to test Checklist live is creating a segment containing your internal testers and then publishing your Checklist targeted only for that group. (See our Segments Overview guide for more info on segments.)

What you can do with restrictive publishing

• Allow only your team or yourself to see the Checklist.
• Test whether user properties/events are working correctly.
• See how the Checklist interacts with your app.
• Test Flows that are triggered by the Checklist.

To target the Checklist to your internal testers:

You can create a Segment to define your internal testers. Here's an example using specific email addresses your testers might have:

You could also target with "Email || contains || @yourcompanynamehere.com", or target just their User IDs in your system, all depending on which property you’d like to use. You can find your User ID if you open the Appcues debugger on any page in your application where Appcues is installed. You can learn more about the Appcues Debugger and how to open it in this article.

Repeated checklist testing

On top of seeing the checklist live in your app, it's also recommended that you test how the checklist items are behaving and if they're checking off correctly.

In order to keep testing your checklist items or a checklist that you dismissed, use the Reset User Profile feature.

How to use it:

• Find your user in the Users page
• Once in your user's profile, select Reset User Profile.

This option resets all flows, experiences, and tracked events for the removed user.  The next time the user logs in or is processed with an identify(); call, their profile will be automatically recreated in an empty state ready for testing.