> This page is for Applications Protection.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.humansecurity.com/llms.txt.

# Troubleshooting

**I don't see all the relevant traffic from the server**

* Check that the Sensor and server are installed on all relevant pages and backend XHRs
* Check for subdomains
* Check if the fraudulent traffic is happening on a 3rd party vendor. If so, find a way to get live reporting on those actions. Usually, a webhook calling our API can resolve this.

**I don't see the user ID on all the relevant traffic**

* Make sure the relevant cookies are not removed before being transmitted via the Enforcer

**There are multiple versions of a user ID**

* Check if different formats (numbers vs. UUID) were used to create the user ID
* Check your routes and pages for a missing hash. A missing hash causes both hashed values and real values (potential collision, PII) to be sent.
* Check if an internal user ID is sent, instead of a slug
* Check if correct custom parameters are set
* Check if the Sensor collects correct fields