# Click Tracking not executed - CSS and HTML issues

A common issue with click tracking occurs when HTML elements are complex. Let's examine an example:

The button in this website's footer contains three elements:

<figure><img src="/files/ek5DeOlc7eNRhzEePRwx" alt=""><figcaption></figcaption></figure>

* \<button ...>
  * \<i ...> (icon)
  * " Yes " (text)

Or, if you inspect it with developer tools, it looks like this:

<figure><img src="/files/JE2J9b78LvwpayL0MAk8" alt=""><figcaption></figcaption></figure>

Now, if you create a click-action trigger that activates on elements with the CSS selector ".btn yes", it will only select the button itself, not the icon or the text. Therefore, clicking on the icon may not trigger the click action because the browser reports the click on the icon instead of the button. Finding the correct CSS selector can be frustrating.

Here are some tips to help you work more effectively:

* Use "**OR**" conditions within the CSS selector input field in JENTIS, separated by commas. For example, instead of only "**.btn yes**", you can add "**.btn yes, .fal fa-thumbs-up**" to include the icon as well.
* Use "> \*" operators to select all child elements of the target, e.g., ".btn yes, .btn yes > \*". This way, you select the button or its child elements.

With these tips, you should be able to better identify and assign the correct action trigger to your elements.


---

# Agent Instructions: 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:

```
GET https://docs.jentis.com/developer-guide/troubleshooting-and-common-errors/click-tracking-not-executed/click-tracking-not-executed-css-and-html-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.