> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/introduction-and-core-concepts/why-use-jentis.md). # Why use JENTIS? JENTIS provides a competitive advantage by transforming data into actionable intelligence. Businesses choose JENTIS for several compelling reasons: * **Improved ROI**: Optimize campaigns and allocate resources effectively by understanding what drives conversions and engagement. * **Improved User Experiences**: Poor quality data caused by browser restrictions, non-consent and ad blocking lead to misleading attribution and fragmented customer journeys. Use JENTIS to fix attribution and understand the full customer journey. * **Enhanced Decision-Making**: Gain deep insights into user behavior, enabling data-driven decisions that improve product development and marketing efforts. --- # 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.jentis.com/introduction-and-core-concepts/why-use-jentis.md?ask=&goal= ``` `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.