Organization-Level Statistics

The Home page of the Capriza Dashboard provides an overview of Zapp usage and performance throughout your organization as a whole.



It is important to note that:

  • All stats on the Home page are for the past 14 days, unless specified otherwise.
  • All Zapp-related stats on the Home tab are only for Zapps marked as Production Zapps. Please see the Adoption tab for Zapp-specific stats across all versions.
  • Users marked as ‘Capriza-affiliated’ (e.g. for testing purposes) do not contribute to any data shown on the Home tab. Users can be marked as ‘Capriza-affiliated’ by the Capriza Customer Success team.


The following sections provide a breakdown of what each statistic measures.




Health indicates the rate of successful Zapp runs, which are defined as runs that did not fail with an error such as a Context Not Found error and during which the user managed to get to the first page of the Zapp (either the login page or, if the login info is cached, the following page). The higher the percentage, the better the performance of your Zapps overall.



Clicking on the "Details" button opens a modal with the percentage and absolute number of runs with errors in total and per Zapp.



Unique Users


Users is meant to indicate the total number of unique users across Zapps in the past 14 days (number at the top). The five column graph provides a longer term view of unique users, displaying the unique users per week for the past five weeks when each column is moused over.



Unique users is calculated via different methods and is a combination of metrics since not all customers distribute Zapps the same way. The calculation method per distribution method is as follows:

  • WorkSimple Unique Users - For Zapps that are distributed via WorkSimple or require the user to authenticate to the Capriza service, we use the unique username that the user logs in with. This includes a Capriza-issued username, password, and any SAML/SSO-integrated logins.

  • Browser Unique Users - Zapps can also be distributed via the browser so that they do not require the user to authenticate to the Capriza service (i.e. the first page the user interacts with is the first page of the Zapp). In this case, Capriza uses cookies to count unique users. Every browser used to access a Zapp is issued a unique cookie and counted as a unique user. Depending on how the user accesses Zapps via browser, he or she may be counted as one or more users. Consider the following scenarios:
    • If the user uses three Zapps from the same browser on the same device, Capriza counts them as one user.

    • If the user uses three Zapps from three devices, Capriza counts them as three users.

    • If the user uses three Zapps from three different browsers on the same device, Capriza counts them as three users;

    • If the user uses incognito mode when using a browser, Capriza counts every run as a new user as a new cookie is issued for every run.

      If your organization has users that use all of the above, the total user count is an aggregation of all the above methodologies. Deduping is done where Capriza is certain it is the same user.

Clicking the details button displays a breakdown of unique users accessing the Zapp via WorkSimple v. browser as well as the percentage of users that have used the Zapp more than once (for all time).

You can also download a CSV file of the raw data by clicking the download icon in the bottom right hand corner of the Unique Users card.

The CSV includes two columns:

  • Last Visit - A timestamp that indicates when the user last logged in;
  • Identity - The email address that logged in successfully.

Note: if there is a discrepancy between the Home page data and the downloaded CSV, it is because the Home tab only aggregates and refreshes data every 6 hours in order to optimize database and Dashboard performance. The Home page, therefore, does not include the most recent runs/users.



This box displays the total number of times your Zapps have been run, as well as the percentage change between the total runs this week and last week.

Runs are calculated by measuring and aggregating the number of times any Zapp was executed. This includes Zapp runs where CNFs occur or where the user just sees the splash or login screens.


Runs by Device

  • This chart displays a breakdown of different device types that your users use to run your Zapps. Hovering over a wedge in the chart displays the exact number of users for a specific device type. The pie chart itself reflects the number of runs per device (not the number of devices, users, etc.).


You can also download a CSV file of the raw data. The CSV file will contain two metrics for each device type:

  • Total Runs
  • Runs on mobile

Device types falling in the "Other" category are detailed in the CSV file.


Note: Data does not include devices where the user has logged into WorkSimple but not run a Zapp.


Performance by Geography


The map provides a view into Zapps performance across different geographical areas.


Each dot on the map represents a cluster of runs in a certain geographical area and the aggregate performance of those runs in the past 14 days. As you mouse over each dot, the data to the left of the map indicates the average network time, application time (the time it takes Capriza to connect to the backend application), and the overall time it takes the user to get to the first page of the zapp.


Note that these numbers are not cumulative and should not be added. They happen mostly in parallel.



You can also click on each dot on the map for more details about those Zapp runs, including a breakdown of runs per Zapp for the particular location.



Clicking on "Live Map" will show a more detailed map with Zapp runs occurring in real time and provide the ability to zoom into a specific region. By default, the last 12 hours are displayed, but this time window can be narrowed to as little as one hour by dragging the slider on the bottom of the screen.



Mousing over each dot on the Live Map reveals the average Network, Application, and Time to First Page for that region as well as the Worst Time observed in that region within the selected time period.



Production Zapp Usage


Additional usage information about your organization's individual Zapps is located below the geographic statistics.


The Production Zapp Usage chart displays usage information (either unique users or number of runs based on the selected filter) for the past several weeks for each zapp.


This table shows runs and users based on the definitions above. Each week is a 7-day time period calculated every Sunday (midnight GMT). The trend arrows are calculated based on the changes between 2 weeks ago and last week (not on the current week), thus comparing full 7 days.



Underneath the chart, individual Zapp performance, user flow, and feedback information can be viewed.



The performance information is provided across the past 14 days and indicates the network time, the time it takes to connect to the backend application, and the overall time it takes to show the user the first page of the Zapp.


Note that these numbers are not cumulative and should not be added. They happen mostly in parallel.


The User Flow chart provides a view into how users move from one page of the Zapp to another. Clicking on Configure Pages allows you to select the pages the represent the main flow of the Zapp and the concentric circles indicate how many users move from one page to the next. This is similar to a fallout chart or a user funnel. Please see the User Flow Report Setup article for more information on configuring this report.


Hovering over each concentric circle provides additional details about each step in the flow, such as the number of visits, the percentage of the overall number of runs of the Zapp and the time it took on average to get to that page, along with a small thumbnail of the page itself.



The Feedback section shows the last few feedbacks that were sent by users.  You can click on "More" to navigate to the Feedback tab for that particular Zapp.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.