How to check if usermaven tracking script is installed correctly?

When you first install the tracking script, we aim to show you your website’s data on the dashboard quickly.

Troubleshooting your usermaven integration

Follow these steps to identify why data might not be reaching Usermaven:

1. Basic checks: Incognito and ad-blockers

• Open in Incognito/Private Mode: Load your website or app page (where the script is installed) in a new incognito or private browser window. This helps rule out browser extensions or caching issues.
• Disable ad-blockers: Temporarily disable any ad-blocker extensions in your browser. Ad-blockers can sometimes prevent tracking scripts like Usermaven’s from loading, especially if you’re not using pixel whitelabeling.

2. Verify script presence and execution (developer tools)

The browser’s developer tools are the most reliable way to confirm if the script is loading and if there are any errors.

1. Visit your page: Navigate to your website’s homepage or any specific page where the Usermaven tracking script should be active.
2. Open Developer Tools:
   • Chrome/Edge/Firefox: Press F12.
   • Alternatively, right-click anywhere on the page and select “Inspect” or “Inspect Element”.
3. Check the Network Tab for lib.js:
   • Select the “Network” tab in the developer tools.
   • You may need to refresh your webpage (Ctrl+R or Cmd+R) for data to appear.
   • In the filter bar of the Network tab, type lib.js or usermaven to quickly find the Usermaven script.
   • Look for an entry related to your Usermaven tracking host (e.g., track.usermaven.com or your custom whitelabel domain).
   • The script should show a status of 200 or 204. This indicates it loaded successfully. (Ensure the image above accurately reflects the lib.js request and a successful status)
4. Check the Console Tab for Errors:
   • Select the “Console” tab.
   • Look for any error messages, particularly those mentioning “Usermaven,” “CSP,” or “Content Security Policy.” Errors here can indicate problems with the script’s execution or conflicts.

3. Confirm script in page source (if not using GTM/frameworks)

If you’ve manually added the script directly to your HTML:

1. Visit your page: Go to the relevant page on your site.
2. View page source:
   • Windows/Linux: Press Ctrl+U.
   • Mac: Press Cmd+Option+U (or Cmd+U in some browsers).
   • Alternatively, right-click on the page and select “View Page Source.”
3. Search for the script: Press Ctrl+F (Windows/Linux) or Cmd+F (Mac) to open the search bar. Type data-tracking-host (or a unique part of your Usermaven script) to locate it.
4. Verification:
   • If found: The script is present in your HTML. Ensure it matches the one from your Usermaven settings (see next step).
   • If not found: The script may not have been added correctly to this page or at all.

4. Ensure correct tracking script

• Verify script details: Double-check that the tracking script installed on your website is exactly the same as the one provided in your Usermaven onboarding steps or found in Workspace Settings > Setup. This is crucial if you manage multiple Usermaven workspaces.

5. Address Content Security Policy (CSP) issues

• Does your site use a Content Security Policy (CSP)? If so, you must explicitly allow Usermaven domains. Add *.usermaven.com (and your pixel whitelabeling domain, if configured) to the appropriate directives in your CSP (e.g., script-src, connect-src).

6. Clear caches

• Website/Server Cache: If your website uses caching (e.g., server-side caching, CDN caching, caching plugins), purge all caches.
• Browser Cache: After purging website caches, perform a hard refresh in your browser (Ctrl+Shift+R or Cmd+Shift+R) or try step #1 (Incognito window) again.

7. WordPress specific: Plugin conflicts

If you’re using WordPress, conflicts with caching or optimization plugins are common:

• Exclude Usermaven Script: Configure caching, minification, or JavaScript combining plugins (e.g., WPRocket, LiteSpeed Cache, SiteGround Optimizer) to exclude the Usermaven script from their optimizations. The script usually includes usermaven.com or your whitelabel domain.
• Temporarily Deactivate: As a test, temporarily deactivate these plugins one by one to see if one of them is causing the conflict. Remember to re-activate them afterward.

Still having issues?

If you’ve gone through these steps and Usermaven is still not tracking data, please reach out to our support team for further assistance. Provide them with details of the troubleshooting steps you’ve already taken.