> 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-accessing-target-url-fails.md).

# Click Tracking - Accessing Target URL Fails

To capture the URL from a clicked element within a complex HTML structure, such as a button containing an icon or text, use the following method.

This code efficiently retrieves the `href` value by iterating through the elements until it locates the root anchor (`<a>` tag).

Simply create a "Client Side" variable with "Client Side JavaScript Code," ensuring access to the `href` value regardless of the nested structure.

{% code lineNumbers="true" %}

```javascript
function(contextObject){
  var result;
  if(contextObject && contextObject.element){
    var targetElement = contextObject.element;
    if (targetElement.tagName.toLowerCase() === "a") {
      result = targetElement.href;
    } else {
      // Traverse up the DOM tree to find the parent anchor
      while (targetElement && 
             targetElement.tagName.toLowerCase() !== "a" && 
             targetElement.tagName.toLowerCase() !== "body") {
        targetElement = targetElement.parentElement;
      }
  
      // If an anchor is found, log the href
      if (targetElement && targetElement.tagName.toLowerCase() !== "body") {
        result = targetElement.href;
      }
    }
  }
  return result;
}

```

{% endcode %}


---

# 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/click-tracking-accessing-target-url-fails.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.