# Segmentation & Targeting

### User Persona

Our product is designed to scale crypto adoption among non-crypto users while also meeting the needs of experienced crypto enthusiasts. Our target audience is individuals aged 18 to 40, who are not high-risk, speculative futures traders but rather spot holders prone to FOMO (Fear of Missing Out).&#x20;

Moving away from centralized exchanges, they now value the importance of self-custody. These users seek a feature-rich, user-friendly app that gives them full control over their funds, enabling them to trade in DeFi without intermediaries and enjoy seamless, cost-effective fiat integrations, including personal IBANs and debit cards.

### Tailored Geographical Focus

Our app is available globally in 174 countries on Android and iPhone devices, supporting transactions with 120 local currencies. We are fully licensed and use direct marketing channels to acquire users from major world economies, enabling us to scale globally.&#x20;

With a focus on Web3 channels, we are targeting users in South Asia and Africa, while our Web2 marketing efforts focus on our native markets such as EU countries and the USA, where average revenue per user (ARPU) exceeds $100. This dual approach allows us to expand effectively.

<br>


---

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

```
GET https://monitok.gitbook.io/docs/overview/segmentation-and-targeting.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.