> For the complete documentation index, see [llms.txt](https://docs.walletx.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.walletx.bot/copy-trading-academy/copytrading-dos-and-donts/4.-study-wallet-behavior-key-analytics.md).

# 4. Study Wallet Behavior - Key Analytics

## 📊 Trading Frequency:

* Look for active daily traders
* Easier to track and predict
* Monitor trading pauses
* Check linked wallet activity

## 💵 Buy vs. Sell Patterns:

* Verify balanced trading ratios
* Avoid pure accumulation wallets
* Look for consistent sell strategies
* Check profit-taking habits

## 👀 Portfolio Analysis:

* Monitor current token holdings
* Check for stagnant positions
* Verify portfolio turnover rate
* Avoid inactive/dormant wallets

## 🎯 Trading Preferences:

* Check if wallet trades pump.fun/non pump.fun
* Analyze market cap ranges (10k-1M+)
* Review token selection patterns
* Identify preferred trading platforms

📝**Pro Tip:** Use WalletX analyzer to quickly identify these key behavioral patterns in any wallet! 🎯

🧠**Remember:** We provide separate alpha channels for pump.fun and non pump.fun traders! 🚀


---

# 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.walletx.bot/copy-trading-academy/copytrading-dos-and-donts/4.-study-wallet-behavior-key-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.