> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/getting-started/user-start.md).

# User

Understanding how to define and manage users is essential for executing more effective marketing actions with Hackle.

This guide provides a quick overview of Hackle's user concepts and how to use them — written for marketers.

### User Identification

Hackle identifies users based on unique identifiers and tracks their behavior.\
This allows you to accurately understand the behavioral flow of each individual user.

For a detailed explanation of user identifiers, refer to [User Identifier](https://docs.hackle.io/en/getting-started/user-identifier.md).

### User Properties

User Properties are specific pieces of information that each user has.\
By using these properties, you can segment customers more precisely and deliver personalized messages.

User Properties can be stored once at a specific point in time (e.g., sign-up date) or continuously updated (e.g., membership tier).

This information makes it possible to create specific target groups such as "female users in their 30s with VIP status."

**User Property Examples**

<table><thead><tr><th width="170.3671875">Category</th><th>Examples</th></tr></thead><tbody><tr><td>Demographic Information</td><td>Age, gender, region, etc.</td></tr><tr><td>Membership Information</td><td>Tier (e.g., VIP, Gold), membership join date</td></tr><tr><td>Service Usage Information</td><td>Average monthly purchase count, last visit date, initial sign-up date</td></tr></tbody></table>

### User Group (Cohort)

Based on user identifiers, properties, and events, you can create Cohorts that meet specific conditions.\
Cohorts become the core target for marketing campaigns.

You can design and run personalized campaigns — for example, running a Re-engagement Campaign targeting a churned user Cohort to encourage return visits, or offering exclusive benefits to high-value customers.

For a detailed explanation of cohorts, refer to [Cohort Introduction](https://docs.hackle.io/en/cohort/cohort.md).

**Cohort Creation Examples**

<table><thead><tr><th width="170.14453125">Category</th><th>Examples</th></tr></thead><tbody><tr><td>Churned Users</td><td>Users who have not visited within a specific period (e.g., the last 14 days)</td></tr><tr><td>High-Value Customers</td><td>Users who have purchased a specific product 3 or more times</td></tr><tr><td>Potential Customers</td><td>Users who have not yet converted to paid after a free trial ended</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hackle.io/en/getting-started/user-start.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
