> 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/marketers-and-editors/introduction.md).
# Introduction
The Marketers and Editor section contains knowledge and tools required to leverrage Umbraco Engage effectively.
This section covers topics such as an introduction to the platform, its components, personalization, reporting, and more.
## [The Umbraco Engage Section](/umbraco-engage/marketers-and-editors/introduction/the-umbraco-engage-section.md)
Explore the Umbraco Engage section to access Analytics, A/B Testing, Personalization, Profiling, Reporting and global settings.
## [Workspace Views](/umbraco-engage/marketers-and-editors/introduction/workspace-views.md)
Discover how the Workspace Views enhance each node with different features for improved content management.
## [The Umbraco Engage Cookie](/umbraco-engage/marketers-and-editors/introduction/the-umbraco-engage-cookie.md)
Umbraco Engage uses a cookie to collect visitor data on your Umbraco website. Learn more about how it works in this section.
## [Profiling](/umbraco-engage/marketers-and-editors/profiling.md)
The Profiling section helps track visitor sessions, manage profiles, and differentiate between identified and unidentified visitors.
## [Settings](/umbraco-engage/marketers-and-editors/settings.md)
The Settings section covers setting up goals, blocking unwanted traffic, and managing the Engage configuration and permissions.
---
# 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/marketers-and-editors/introduction.md?ask=&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.
