> 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/developer-guide/troubleshooting-and-common-errors/click-tracking-not-executed.md).

# Click Tracking Troubleshooting

Use this hub to diagnose click tracking issues faster.

Start with the symptom that matches your setup.

### Find the right troubleshooting path

* Nothing happens when you click, and no preview event appears: go to [Click Tracking not executed - Further Troubleshooting](/developer-guide/troubleshooting-and-common-errors/click-tracking-not-executed/click-tracking-not-executed-further-troubleshooting.md).
* The trigger works only on parts of a button or link: go to [Click Tracking not executed - CSS and HTML issues](/developer-guide/troubleshooting-and-common-errors/click-tracking-not-executed/click-tracking-not-executed-css-and-html-issues.md).
* The click is detected, but the target URL is missing or wrong: go to [Click Tracking - Accessing Target URL Fails](/developer-guide/troubleshooting-and-common-errors/click-tracking-not-executed/click-tracking-accessing-target-url-fails.md).
* You need a broad debug setup to inspect every click: go to [Click Tracking - Debug with All Clicks as a Last Resort Measure](/developer-guide/troubleshooting-and-common-errors/click-tracking-not-executed/click-tracking-debug-with-all-clicks-as-a-last-resort-measure.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/developer-guide/troubleshooting-and-common-errors/click-tracking-not-executed.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.