All Collections
Getting Started
Script Verification
Common Issues Impacting Script Verification in the Dashboard
Common Issues Impacting Script Verification in the Dashboard
Updated over a week ago

The built-in script verification tool serves primarily as a convenience to assist with the installation process. Importantly, the script will automatically verify itself the moment it transmits the first byte of data, making manual verification a helpful but not mandatory step.

When attempting to verify your script using the dashboard, you might encounter some hurdles that can prevent successful verification. Two of the most frequent issues are:


If your URL undergoes a redirect, it can remove the query string that's crucial for the verification process. This absence will lead to a verification failure. It's essential to ensure that the URL used for verification remains stable without any redirects that might strip away necessary parameters.

Domain Structure

The distinction between top-level domains and subdomains plays a significant role in script verification. For instance, if your script is intended for a top-level domain like, but you've installed it on a subdomain such as, the verification process might not succeed. This discrepancy occurs because the verification tool checks for the script on the top-level domain ( rather than the subdomain where it's actually installed. However, it's important to note that while this may affect verification, your script will still function correctly on the subdomain.

Solution: Manual Script Functionality Check

A quick way to tell whether your script is operational, simply check if user profiles are being collected. If you observe profiles being gathered, your script is functioning correctly and you're ready to proceed.

Did this answer your question?