How to check if Usermaven tracking script is installed correctly?

When it's your first time installing Usermaven, we take you to the dashboard once the data from your site hits our servers so that you don't get an empty dashboard. Usually, the data populates in 2 to 3 minutes but if it takes longer, it's time to find the root cause of this problem.

Here are some of the ways to troubleshoot your Usermaven integration:

1. Open a new incognito or private browser window and load your website or app page where you installed the tracking script.
2. Make sure that you don't have an ad-blocker installed (especially if you aren’t using pixel whitelabeling). Ad-blocker might be preventing the Usermaven tracking script from loading in your browser.
3. Make sure that the page you're loading has the Usermaven tracking script on it. A simple way to verify this is by viewing the source code of your website. Here's how:
   1. Visit your website's home page or any other page where the tracking pixel should be available.
   2. Use a keyboard shortcut to view the source code of your site. Press cmd+u on a Mac or ctrl+u on Linux and Windows. Alternatively, you can right-click anywhere on your page and click "View Page Source" (the wording may be slightly different depending on your web browser).
   3. Press cmd+f on a Mac or ctrl+f on Linux and Windows to search. Type data-tracking-host to search for the Usermaven script.
   4. If you see Usermaven's tracking script in the code, it means the script is installed. However, if you don't see the code then it might not have been installed properly. Or, if you used a 3rd party plugin/framework like GTM or Next.js, the code will not appear in the source code, then you can troubleshoot with the next points mentioned in this document.
4. Check if there are any errors in the browser's developer tools " Console" tab. Here's how:

   1. Visit your website's home page or any other page where the tracking pixel should be available.

   2. Open the developer tools by pressing the key F12 on Firefox or Chrome. Alternatively, you can right-click anywhere on your page and click "Inspect" (the wording may vary depending on your web browser).

   3. Look into the "Console" tab in the developer tools for any errors related to Usermaven. If you see an error related to the Usermaven script, it means that something's not right with your implementation. We have some troubleshooting options further down this article.

   4. Then click on the "Network" tab in the developer tools. It will be empty, so you would need to reload the page. After you refresh the page you will start seeing some data in the "Network" tab. You should find the lib.js in the list. The Usermaven script should display status 200 as shown in the image below.

      

5. Please ensure that the script you used is exactly the same script as listed in your Usermaven's onboarding step or Workspace Settings > Setup (especially if you are using multiple workspaces).
6. Does your site use a Content Security Policy (CSP)? If it does, you need to add usermaven.com specifically to the allowed domains.
7. Are you using Cache? Purge it and perform point #1 again.
8. If you’re using Wordpress, exclude our script from any caching, minifying, or javascript combining plugins because it is the most common issue with Wordpress, Some plugins like WPRocket and SiteGround Optimizer break our script until you add it to their exclusion list. Deactivate these plugins to see if they are causing a conflict.