Checkpoints exist to find out how far users get in your story and what paths they take. Checkpoints can’t be seen by users, because they are a configuration element.
Characteristics:
Any number of checkpoints can be placed at any location within a story. Each of them must have a distinct name.
Function:
Checkpoints can be used to sum up which users have taken which path. The number of times a checkpoint was reached is counted, regardless of whether it was by the same user or not.
This is how to use checkpoints in 2 simple steps:
Example use case: Integrate checkpoints after decisions
After every decision, a checkpoint can be placed. This is how you will learn how many users chose what option.
1️⃣ Integrate and name a checkpoint
Via drag & drop, the -widget can be placed directly after a decision. Because the checkpoint in the following example was placed directly under «I'm looking for your Enterprise Solution», it makes sense to call it «Looking for EP». Like this, you will later find out how many users chose this option through your KPI dashboard.
2️⃣ Analyze your checkpoints
In the story overview, you can open the data about the checkpoints of each story through the 
KPI icon. «Absolute» is the number of times the checkpoint was reached. «Conversion» shows how many users who started the story have crossed the respective checkpoint.