> 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/tasks/web3-tasks/transactions-count.md).
# Transactions count
This task is useful for identifying active users, encouraging on-chain engagement, or rewarding loyal community members.
### Before you start
Make sure you have:
* A quest created within your campaign
* Knowledge of which blockchain networks your target users are active on
* A minimum transaction count threshold determined
### Create the task
Follow the steps in [Web3 tasks](/tasks/web3-tasks.md) to navigate to the task creation screen, select **Web3** from the Groups section, and choose **Transactions Count**.
### Task settings
**Completion points**: Set the number of points awarded when the user completes the task.
**Points multiplier (%)**: Add a percentage-based bonus to the total reward. For example, a 5% multiplier increases the final reward by 5%.
**Networks**: Select the blockchain network on which you want to track user transactions.
* Click the first dropdown to choose a network (e.g., Ethereum)
* Click the second dropdown to select Mainnet or Testnet
* Click **Add network** to track transactions across multiple networks
* Users must meet the minimum count across all selected networks combined
**Min Count**: Specify the minimum number of transactions a user must have made across all selected networks to be eligible for the task.
Example: If you enter "10", users who have made at least 10 transactions in total across any of the chosen networks will qualify. The count is cumulative across all networks you've added
**Time, h (optional)**: Set a time window in hours for counting transactions. If specified, only transactions made within this time period will count. Leave blank to count all transactions from the wallet's history
### **Helpful tips**
* Provide clear instructions on how users can check their transaction count on the specified blockchain network
* Be transparent about why you're tracking transaction count and how it relates to your campaign goals
* Consider setting different minimum counts for different networks based on typical activity levels
---
# 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/tasks/web3-tasks/transactions-count.md?ask=&goal=
```
`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.