> 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/click-tracking-debug-with-all-clicks-as-a-last-resort-measure.md).
# Click Tracking - Debug with All Clicks as a Last Resort Measure
If all the solutions provided before are still unhelpful, you can use the following workaround to find the root cause.
In this case you can create a “catch all” trigger that will activate on all clicks on your website. Connecting this to a tag will provide you a “scanner” tag that displays the variable values that might not be what they should be. Generally, JENTIS tags only activate (and also display in the preview) if the trigger conditions are met and a state is executed, which can lead to situations where nothing appears in the preview, even though something is expected to pop up on a particular click.
Here is a configuration of such a “catch all” trigger:
This trigger is set to the state “SELECTORACTION” for all click-actions with the CSS selector value `*`. All clicks are registered with this one.
It is also a good idea to select the variable in question (which might not be working as expected) in the trigger condition. Variables will only be evaluated if they are actively used, even for the preview.
Now connect this to a tag and start a preview session. In this example, we will use a generic “Google Analytics event tag.” When a click is processed on the website, it will always pop up on your screen. In this tag, you can now preview the trigger conditions and actual variable values, regardless of whether the exact trigger conditions you are looking for are met.
\\
---
# 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/developer-guide/troubleshooting-and-common-errors/click-tracking-not-executed/click-tracking-debug-with-all-clicks-as-a-last-resort-measure.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.
