> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/developers/profiling.md).

# Profiling

Profiling collects and analyzes behavior data to customize content. Umbraco Engage allows CRM integration to enhance visitor profiles without built-in methods.

Profiling is tracking and analyzing visitor behavior to build detailed visitor profiles.

This involves collecting data from website interactions to understand user preferences and customize content and marketing strategies accordingly. Profiles are dynamically updated as users interact with the site, allowing for more personalized and targeted marketing efforts over time.

## [External Profile Data](/umbraco-engage/developers/profiling/external-profile-data.md)

In Umbraco Engage, you can integrate data from external systems with visitor profiles. Although Umbraco Engage does not provide built-in methods for adding this data, you can store it in any format.


---

# 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.umbraco.com/umbraco-engage/developers/profiling.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.