> 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/event-management/properties/event-property.md).

# Event Property

Event Properties are detailed information left alongside an event. If a user triggered a product click event, information such as the clicked product's ID, category, price, and brand would apply. If a user scrolled on a specific screen, the scroll length could be recorded in pixels or as a percentage. This kind of detailed information is called a property.

Properties collected in Hackle can be checked on the event detail page and are divided into two types as follows:

* **Custom (User, Event) Properties**: Property information sent by Hackle customers for detailed analysis of event data.
* **Hackle Properties**: Auto-collected properties such as osName (operating system, e.g., Android, iOS), browserName (browser, e.g., Chrome, Safari, Whale), and language (e.g., ko-kr, eng).

{% hint style="warning" %}
Property description

You can enter and modify a description related to a property at any time in the Properties tab on the event detail page. You can also use this area to enter examples of collected property values. However, for properties that are commonly used across multiple events, modifying the property description in one event will update the property description for all events that include that property at once, so be cautious when making changes.
{% endhint %}

![3024](/files/cdvNhLWn2NDUXSF6KWNY)

## Property Count Limit

The maximum number of Custom (User, Event) properties allowed per workspace is as follows:

* User properties: 1000
* Event properties: 1000

Property data that exceeds the maximum allowed value cannot be queried.

***


---

# 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.hackle.io/en/event-management/properties/event-property.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.