Why Is My Tracking Script Not Firing After Installation? (Cache and GTM Publishing Issues)

Why Is My Tracking Script Not Firing After Installation? (Cache and GTM Publishing Issues)

If you have installed the Visual Visitor tracking script but your dashboard is showing zero visitors, one of the following issues is most likely the cause:

 

·       Cache not cleared: 

 WordPress sites using caching plugins (WP Rocket, LiteSpeed, W3 Total Cache) or Shopify CDN caching may serve the old version of your page to visitors even after you paste the script. Always purge or clear your entire site cache immediately after installing or updating the script. Then wait 15-20 minutes for CDN propagation.

·       GTM container not published:  

If you are deploying Visual Visitor via Google Tag Manager, adding the tag inside GTM is not sufficient on its own — you must click Submit > Publish inside GTM to push the container live. A common error is saving a workspace draft without actually publishing.

·     Tag trigger misconfigured:

Inside GTM, confirm the trigger for the Visual Visitor tag is set to All Pages (Page View trigger). If the trigger is set to a specific page URL or event, the script will not fire site-wide.

·       Cookie consent blocking: 

 If your site uses a cookie consent banner (OneTrust, Cookiebot, Osano, etc.), the Visual Visitor script may be blocked until a visitor accepts cookies. See the article "Why Is My Tracking Script Blocked by a Cookie Consent Banner?" for solutions.

·       Content Security Policy (CSP) blocking: 

 Some websites enforce a CSP that restricts which external scripts can load. See "How to Allow the Visual Visitor Script in Your Content Security Policy."

 

Verification steps:

 

1.     Open your site in a browser in Incognito / Private mode.

2.     Open Developer Tools (F12) and go to the Network tab.

3.     Reload the page and search for your script in the network requests.

4.     If no request appears, the script is not firing — review the items above.