--- title: "Analytics" canonical: "https://support.appfire.com/space/RS/3159032812/Analytics" format: markdown --- > Macro (aura-html) Use the Analytics dashboard to understand how QueueZero is being used, the outcomes it contributes to, and how usage changes over time. Analytics is available to Organization Owners and Organization Admins. ## Why use the Analytics dashboard? The QueueZero Analytics Dashboard is more than just a reporting tool; it is a strategic asset for team leads and administrators. By leveraging these insights, you can: - Identify exactly where your AI spend is concentrated and ensure you are getting maximum value for every token. - Bridge the gap between plan generation and task execution to identify bottlenecks in your development process. - Use efficiency metrics to understand which knowledge sources (such as documentation or repository context) are driving the most successful outcomes. - Move away from guesswork and use concrete metrics to justify AI adoption and fine-tune your team’s configuration for better results. ## Open Analytics 1. Open QueueZero standalone. 2. From the side menu, select **Analytics** ![Appfire BacklogZero Analytics dashboard showing value metrics](media://2dc95174-7689-401b-b7c3-610d488563f9) ## 1. Filters Use the filters at the top of the page to narrow the data. Available filters include: - **Date range** - **Space** - **Work item type** The selected filters apply to the metrics and reports shown on the page. ## 2. Value Use the **Value** tab to understand the outcomes to which QueueZero has contributed. Value metrics may include: | **Metric** | **Description** | | --- | --- | | **Hours saved** | Estimated engineering time saved by using QueueZero. | | **Value generated** | Estimated monetary value of the engineering time saved. | | **Memory layer** | Estimated tokens avoided by reusing information QueueZero had already learned. | | **Plans accepted** | Number of generated plans that were accepted. | | **Acceptance rate** | Percentage of generated plans that were accepted. | | **Work resolved** | Number of work items QueueZero helped resolve. | | **PRs raised** | Number of pull requests created by QueueZero. | | **Multi-repo resolutions** | Number of resolutions that involved more than one repository. | > 📝 **Hours saved** and **Value generated** are estimates of engineering productivity. They are not AI usage or AI spend. ### Adjust ROI assumptions Click **How is this calculated?** under *'Hours saved'* or *‘Value generated’,* or click **ROI Calculator TUNE & EXPLORE** button to open the **ROI Calculator **(Figure 2, below). ![Appfire BacklogZero ROI Calculator](media://b0364253-00b9-44aa-9a99-e87a752b497a) The ROI Calculator shows how QueueZero estimates hours saved and value generated. It breaks the calculation down by work item complexity and lets you adjust the assumptions. You can adjust: - Hours per Easy work item - Hours per Medium work item - Hours per Complex work item - Engineer hourly rate QueueZero recalculates the estimates using the selected filters and assumptions. ## 3. Activity Use the **Activity** tab to review how teams are using QueueZero. ![Appfire BacklogZero Activity metrics](media://15a06b7f-c1b8-4f55-9c3b-82a5b60e00d1) Activity metrics may include: | | | | --- | --- | | **Metric** | **Description** | | **Plans generated** | Number of implementation plans created by QueueZero. | | **Plan versions** | Number of plan attempts or regenerated plans. | | **Average plan versions per work item** | Average number of plans generated for each work item. | | **Knowledge pages indexed** | Number of documentation pages indexed for space context. | | **PRs raised** | Number of pull requests created by QueueZero. | | **Failed runs** | QueueZero runs that did not complete successfully. | Use activity metrics to understand how often QueueZero is used and where teams may need better work item details, repository setup, or documentation context. ### Activity by space The **Activity by space** card shows a breakdown of several metrics by each space: - **Plans generated** - The number of plans generated across all work items in the space. - **Plans accepted** - The number of plans accepted across all work items in the space. - **Acceptance rate** - Plans accepted divided by plans generated. - **PRs raised** - The number of PRs raised across all work items in the space. ### Refine PR The **Refine PR** card shows how refinement progresses through stages such as **Prepared**, **Plan generated**, **Applied**, and **Completed**. It also includes metrics such as apply success, plan reverts, post-apply CI results, and median time to apply. ### Refine sessions The **Refine sessions** card summarizes refinement activity, including the number of sessions, how many reached a proposal, interaction counts, and information about assumptions gathered during refinement. Some refinement analytics are displayed only when enough relevant data is available. ### Refined vs unrefined The **Refined vs unrefined** card compares outcomes for work items that were refined before resolution with those that were not. The comparison can include: - resolution success rate, - pull request merge rate, and - plans generated per work item. This card appears only when QueueZero has data for both refined and unrefined work items. ## 4. Adoption Use the Adoption tab to understand who is using QueueZero and how usage changes across the organization. The Adoption tab is separated again into 4 tabs - **Trends**, **Leaderboards**, **Cohorts**, and **Weekly Digest**. ![Appfire BacklogZero Adoption tab showing usage metrics](media://d81c21da-58fd-4613-88b1-3e33e58359be) ### Trends Use **Trends** to review weekly adoption metrics and compare usage over time. You can view the Trend chart by **Organization**, **Space**, or **User**. When viewing by Space or User, you can compare multiple series, change the metric being charted, and group the data by different dimensions. Summary data for the selected group includes PRs created, PRs merged, the percent merged, and the Issue resolve rate. > ℹ️ **Issue resolve rate** cannot always be displayed depending on the group displayed and the date range selected. The Trends tab also includes the section **QueueZero share of repository PRs**, which calculates the percentage of PRs across all connected repositories that were created by QueueZero. This card includes a table of all repositories and their line item statistics for PRs created, QueueZero PRs created, and additional measures. > 📝 **Note**: The total number of PRs are read live from GitHub and Bitbucket when the dashboard loads. If the connection to a repository fails, the card itself will display an error, but the remaining cards on the page will load. > 📝 > 📝 Click **Retry** to attempt to load statistics from failed repositories again. ### Leaderboards Leaderboards can rank **Individuals** or **Teams** using metrics such as: - pull requests created, - pull requests merged, - merge rate, - execution success rate, and - refinement sessions. Individual leaderboards identify users by name and are visible only to users who have access to Analytics, such as Organization Owners and Organization Admins. ### Cohorts The **Cohorts** view groups people and spaces based on their recent usage: - New - Returning - Retained - Dormant - Seen (authenticated to QueueZero) but not yet used Select a cohort to review the members included in it. ### Weekly digests Weekly digests provide stored summaries of completed weeks, including an **Executive summary** that you can copy for reporting. A new organization may not have any digests yet. Digests appear only after a completed UTC ISO week has been recorded. ## 5. Consumption The **Consumption** tab is available only for organizations configured to display monetary AI usage. For most organizations, AI usage is reported in tokens. Monetary figures are available only when monetary usage is enabled for the organization, such as when the organization uses its own AI provider account. As a result, you may not see the **Consumption** tab at all. When available, the tab includes: | | | | --- | --- | | **Metric** | **Description** | | **Overview** | Total spend, prompt, cache, and response token usage, and average cost per work item resolved. | | **Cost over time** | Spend over the selected date range, broken out by various model tasks. | | **All usage by work type** | Spend by QueueZero task type - code generation, plan generation, etc. | | **Top cost contributors** | Highest cost plans in the active range. | | **Cost by space** | Cost breakdown by QueueZero space including token usage. | Consumption metrics can be used to analyze your spending by the relevant activities and identify activities or spaces that are over-spending or under-spending. ![Appfire BacklogZero Consumption tab showing usage statistics](media://970843df-c401-4060-a401-ac3050a1142d) ## 6. Export CSV Use **Export CSV** to download the current analytics data. The exported file follows the filters currently applied on the page. Use it when you need to share usage data, review trends outside QueueZero, or include QueueZero activity in internal reports.