# Testing & Debugging

#### Setting up the Debug Panel

After setting up the web tracking SDK, the best way to debug it is by going on the site it was installed on and setting the following config, by using the browser console:

```
ce.enableDebug(true)
```

This will set a temporary local cookie( expiring after 7 days), that enables the CrossEngage Debug Console, which will be visible after a hard refresh of that website in the bottom right corner. Please note that this configuration will only affect your own browser in which this cookie is set. 

You can then access the debug panel by simply clicking on the shown panel. 

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

We also always automatically show all executed tracking calls.&#x20;

#### Using the Debug Panel

You can use the debug Panel to:&#x20;

* Access/View the current **SDK configuration**
* **Monitor the triggered Events** and have a detailed view of the event payloads, responses as well as the order in which the events have been sent
* **Trigger Events and User updates -** allowing you to quickly test and also imitate user behaviour


---

# 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://documentation.crossengage.io/data-and-engagement-platform/web-tracking/web-tracking-v2/testing-and-debugging.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.