Skip to main content
New Idea

Guide Engagement Analysis - Change the Logic of "Completion Rate" Calculation

Related products:PX Analytics
  • January 25, 2022
  • 1 reply
  • 43 views
GameChangerAdmin
heather_hansen
bradley
ltsponhour
benwanlessmenlo
+12
  • GameChangerAdmin
    GameChangerAdmin
  • heather_hansen
    heather_hansen
  • bradley
    bradley
  • ltsponhour
    ltsponhour
  • benwanlessmenlo
    benwanlessmenlo
  • romihache
    romihache
  • jkolle
  • Sruthimalla
    Sruthimalla
  • alizee
    alizee
  • anirbandutta
    anirbandutta
  • Elana Cipin
  • Chae Stewart
  • bytor104
    bytor104
  • dayn.johnson
    dayn.johnson
  • silasramsden
    silasramsden
  • alexander.mahan
    alexander.mahan
  • aoleson01

Hi everyone, 

When checking the performance of guide engagements, we feel that it would be more useful to be able to observe the data as a funnel (on user level). In the current setup, we are able to see the total number of times each step was viewed and the “completion rate” is then calculated based on those numbers. In example:

  • let’s imagine that 10 users started the guide and only 1 of them completed it (saw the last step of the guide)
  • and let’s imagine that the mentioned user completed the guide 10 times (while the other 9 users started the guide only once and never completed it)

With the current setup, the “completion rate” of this guide would be calculated as:

  • (10 times completed)/(19 times started)=52,63%

And the question is - when estimating the performance, usefulness or design of a guide, are we more interested in this information or in the information about the share of users who started and managed to complete the guide (1/10=10% in the above example).

1 reply

  • Author
  • Contributor ⭐️⭐️⭐️⭐️
  • 30 replies
  • February 10, 2022

Just to add a screenshot of a silly situation related to the request:

 

And this could also be prevented if the funnel was actually representing unique users (like any other funnel) instead of “total views per step”. A funnel shouldn’t look like this :)


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings