# User Segmentation and Profiling

## Overview

For each chain, we maintain an extensive collection of labeled smart contracts. These contracts are categorized into different types that correspond to specific user archetypes.

By analyzing the historical interactions of users with these contracts, we can determine the profiles that apply to each user.

The profile in which a user is most active becomes their main profile, which serves as the primary basis for our analyses.

### Profiling Methodology

1. **Data Collection**: We collect historical interaction data of users across multiple chains, focusing on their engagements with the labeled contracts.
2. **Profile Assignment**:
   1. **Multi-Profile Identification**: Users may interact with contracts across different archetypes, indicating multiple applicable profiles.
   2. **Main Profile Determination**: We identify the profile in which the user has been most active. This becomes their main profile and is used predominantly in our analyses.

### User Profiles

We have defined five primary user profiles. These profiles were developed based on common labels and classifications within the web3 space:

* DeFi Degen: Users heavily involved in decentralized finance (DeFi) activities, such as yield farming, liquidity provision, and interacting with DeFi protocols.
* dApp User: Individuals who regularly use decentralized applications (dApps) for various purposes beyond financial use cases, including social media, utility tools, and more.
* NFT Enthusiast: Users who actively engage with non-fungible tokens (NFTs), including collecting, trading, and participating in NFT marketplaces.
* Gamer: Those who participate in blockchain-based games, including play-to-earn models, virtual worlds, and other on-chain gaming platforms.
* Trader: Users primarily focused on trading activities, such as frequent buying and selling of cryptocurrencies on CEXs and DEXs.


---

# Agent Instructions: 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:

```
GET https://docs.forse.io/getting-started-education/data-analytics/list-of-data-metrics/user-segmentation-and-profiling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.