> For the complete documentation index, see [llms.txt](https://docs.claimr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claimr.io/data-analytics/issues-analytics.md).

# Issues analytics

## **What is Issue analytics?**

Issue analytics provides a detailed overview of user-reported problems encountered while completing tasks within claimr⚡️, specifically for VAPs remarketing companies. It allows you to monitor and analyze user-submitted reports to identify and resolve potential task-completion issues.

## **How your users see this**

When users, aiming to **complete** tasks, encounter issues, they can report them.

The **Report an issue** link appears after three unsuccessful attempts to **complete** a task.

<figure><img src="/files/pMVRX4cQF1bNoOfj2lJV" alt="" width="316"><figcaption></figcaption></figure>

Clicking **Report an issue** opens a modal window where users can:

* Leave their email address.
* Provide a short issue description.
* Attach files.

<div data-full-width="false"><figure><img src="/files/FXhJAuFC1kL8t562DtH2" alt="" width="375"><figcaption></figcaption></figure></div>

## **Use this data to**

* **Identify task completion barriers:** Spot patterns and trends in user-reported issues preventing task **completion**.
* **Improve task clarity:** Address issues to minimize user frustration and ensure smoother task **completion**.
* **Enhance user experience:** Resolve problems promptly to improve overall satisfaction with the task **completion** process.
* **Monitor task integrity:** Ensure tasks are being **completed** correctly and effectively.

## **Accessing Issues analytics**

1. Log in to your claimr account.
2. Select the relevant campaign.
3. Click on the **Analytics** tab.
4. Select **Issues** from the submenu.

## **Issue dashboard**

Once you select **Issues**, the dashboard will open, displaying a table of all reported issues. This table provides a summary of each issue and allows you to quickly assess the situation.

<figure><img src="/files/yfD9jkggbtS2b9vJ9TBS" alt=""><figcaption></figcaption></figure>

**Table elements:**

* **Reporter:** The username or identifier of the user who reported the issue.
* **Date:** The date and time when the issue was reported.
* **Task:** The name or identifier of the task the user was attempting to complete.
* **Status:** The current status of the reported issue.
* **Title:** A brief title or summary of the issue provided by the user.
* **Summary:** A short description of the issue provided by the user.

To open each issue report for detailed information, click on the respective row in the table.&#x20;

## Issue details modal

Clicking on a row in the dashboard table opens a modal window containing all the details of the reported issue.

### General information

<figure><img src="/files/FI8fPLNGREIsVsIyTlMa" alt="" width="375"><figcaption></figcaption></figure>

* **Date:** The date and time when the issue was reported.
* **Title:** The title or summary of the issue provided by the user.
* **Description:** The detailed description of the issue provided by the user.
* **Attached files:** Any files (e.g., screenshots) attached by the user.

### **Task section**

<figure><img src="/files/aGYawd913OB78d1t9hqa" alt="" width="375"><figcaption></figcaption></figure>

* **Name:** The name of the task the user was attempting to complete.
* **Status:** The status of the task at the time the issue was reported (e.g., "Failed").
* **Set task as completed:** A button allowing you to manually mark the task as completed if you determine the issue does not prevent successful completion.

### **Reporter section**

<figure><img src="/files/s9gNgOvJEvpAvFe3rJpz" alt="" width="375"><figcaption></figcaption></figure>

* **ID:** The unique identifier of the user who reported the issue.
* **Name:** The username of the user who reported the issue.
* **Email:** The email address of the user who reported the issue.
* **User details:** A button or link to view more detailed information about the reporting user.

{% hint style="info" %}
For more details about all User information in claimr, visit [User information](/data-analytics/user-information.md).&#x20;
{% endhint %}

### **Trace section**&#x20;

This section provides a breadcrumb trail of the user's activity leading up to the reported issue. You can recreate the user's steps and identify the source of the problem.

<figure><img src="/files/olPdgIVzRKJTbJf2xtST" alt="" width="375"><figcaption></figcaption></figure>

* **Group:** The group associated with the task. This helps identify the specific set of tasks or users involved.
* **Quest:** The quest associated with the task. This helps pinpoint the specific campaign or sequence of actions the user was attempting.
* **Task:** The name of the task the user was attempting to complete.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.claimr.io/data-analytics/issues-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.