> 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/usage-data.md).

# Usage data

Usage Data gives you an overview of your subscription performance. It connects directly with the values shown in Billing and expands them with detailed breakdowns. Projections highlight whether usage is on track or likely to exceed your plan, and historical records make it possible to compare consumption across different subscription periods.

Usage Data also shows the actions behind that performance. Depending on your subscription type (Credits or Monthly Active Users), it details how much of the allocation has been used and which tasks or users contributed to it. The data updates in near real time, so you can monitor the progress of your campaigns as activity occurs.

## Tables

There are several types of tables in Usage Data.&#x20;

### **Overview table**

The first table aggregates actions performed during the subscription period. Each row includes:

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

* Platform (e.g., Twitter, Web, Web3)
* Task name
* Execution count
* Credits spent (for credit-based subscriptions)\
  This gives you a grouped summary of activity, showing how often each task was completed and how many credits it consumed in total.

### **Detailed task log**

The second table provides a chronological log of every single task performed. Each row includes:

<figure><img src="/files/5eCeqIPg4dTsZeo1Cd4C" alt=""><figcaption></figcaption></figure>

* **#** – the sequence number of the action
* **Platform** – where the task was executed
* **Task** – the specific task type (e.g., Connect a Wallet, reCAPTCHA check, Follow on X)
* **Credits** – the cost of that individual task in credits
* **Date** – the exact timestamp of when the task was executed

This log gives you a granular view of usage, making it possible to audit activity and track exactly when and how credits were spent.

## **Graphs**

### **Credits usage graph**

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

* Green area: credits used in real time.
* Orange line: projected usage until the subscription ends.
* Yellow line: subscription credit limit. This shows if you are likely to exceed your plan.

### **Task type graph**

<figure><img src="/files/6eKdXQtqNnfj3rcUqEHD" alt=""><figcaption></figcaption></figure>

* Displays how many times each task type was executed.
* Tasks can be enabled or disabled for comparison.

### Filtering and time ranges

You can filter by campaign, subscription period, or custom date range. Resetting filters returns the view to the active subscription.

#### History

Past subscriptions are listed in a history table.&#x20;

This history allows you to compare previous subscriptions and track how your usage has changed over time.


---

# 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/usage-data.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.
