Playbook Analytics

Modified on Mon, 7 Jul at 11:01 AM

Playbook Analytics section in Portal provides an overview of how users are engaging with Playbooks and the Journeys inside them. This section offers insights into the performance of the Playbooks, such as the number of completed Playbooks, number of Journeys launched from Playbooks or the Journey and User Overall Completion.



Filtering the Analytics data


The top bar in each Analytics section allows users to filter the data based on various Segments, adjust the time period and display the data related to the content that has been removed.




Summary


The Summary section in Playbook Analytics shows following numbers:

Engaged Users - how many users were working with the Playbooks within the selected time period


Playbooks Completed - how many Playbooks were completed by unique users (this number does not stand for unique Playbooks - please, find more details in the Example below


Example:
There are 2 Playbooks created in the site content.
User 1 completed Playbook 1

User 2 completed Playbook 1

User 3 completed Playbook 2
Then the number of completed Playbooks equals 3.


Journeys launched from Playbooks - how many Journeys belonging to the Playbooks were started within the selected time period



In the Summary section, users can find also graphical view of the Analytics data in two charts:


 



Playbook List


The table "Playbook  list" brings the overview of all Playbooks together with the information about how many users were working with each specific Playbook within the selected time range.


In percentage, there is information about how many users completed each Playbook so far till specified end date (All-Time column), and how many of them completed the Playbook with the selected time range (In-Timeframe column).



If you click the Playbook name in the above table, you are redirected to the Playbook Detail Analytics section of that specific Playbook.



Playbook Detail Section


In the Detail section, users can find Analytics data related only to that particular Playbook for the specified time period (and optionally for the selected Segment).


At the top of the Detail section, there is a name of that particular Playbook and all the filtering options as on the main Playbook Analytics page (Segment filter, Time period filter, Show deleted content checkbox).



The Summary section shows:

  • the number of Engaged Users who were working with that particular Playbook within the specified time range (and within the selected Segment)
  • the number of users who completed successfully the whole Playbook
  • the Summary data in graphs





Journey List


This is the table of all Journeys inside that specific Playbook and it shows following data for each Journey:

  • Journey name - the name is clickable and after clicking, user is redirected to the Journey Detail Analytics page for that particular Journey
  • Engaged Users - how many users were working with the Journey
  • Completion (In-Timeframe) - how many % of the users completed the Journey in the selected time range
  • Completed Users (In-Timeframe) - how many users completed successfully the Journey in the selected time range
  • Completed Users (All-Time) - how many users completed the Journey so far till specified end date


Users Completion


This table brings the overview of the particular Playbook completion per user. It contains:

  • User name
  • Completion Date - it is getting filled with the date once the user completes the whole Playbook for the first time (the date is empty until the Playbook Completion is 100%)
  • Completion (In-Timeframe) - how many % of the Journeys inside the Playbook were completed by this user within the selected time range
  • Completion (All-Time) - how many % of the Journeys were completed by this user so far till the specified end date







Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article