> 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/use-cases-and-tutorials/click-tracking.md). # Click Tracking Use this page as the starting point for click tracking in JENTIS. If you want to create a click-based trigger, start with [JENTIS Click Trigger Details - Selectoraction](/developer-guide/triggers/jentis-click-trigger-details-selectoraction.md). This guide covers how Selectoraction triggers work and how to define the right CSS selector. If you want to capture data from the clicked element, such as button text, `href`, CSS classes, or parent element values, use [Click Trigger Properties](/use-cases-and-tutorials/click-tracking/click-trigger-properties.md). If your click tracking does not fire as expected, check [Click Tracking Not Executed](/developer-guide/troubleshooting-and-common-errors/click-tracking-not-executed.md). This is the best starting point for selector issues and missed click events. If the click leads to a page change and data gets lost during navigation, read [Page Navigation Events - Optimizing Data Tracking on Page Unload](/use-cases-and-tutorials/page-navigation-events-optimizing-data-tracking-on-page-unload.md). If you need guidance for form submits and similar interaction patterns, continue with [Form Submit, Click and Other Actions](/use-cases-and-tutorials/events-and-custom-states/form-submit-click-and-other-actions.md). --- # 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.jentis.com/use-cases-and-tutorials/click-tracking.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.