If you’ve installed the RB2B script but aren’t seeing any visitor data, your site’s Content Security Policy (CSP) may be blocking the script from running.
Step 1: Check for CSP Errors in Your Browser Console
Visit a page on your website where the RB2B script is installed.
Open your browser’s Developer Tools (press
F12or right-click and choose Inspect).Click on the Console tab.
Look for red error messages related to CSP, such as:
Refused to load the script because it violates the following Content Security Policy directive...Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource...
If you see messages like these, it means your CSP is restricting RB2B’s script or associated resources.
Additional messages might include CSP violations blocking required network calls or script execution errors.
Step 2: Get Required CSP Exceptions
Go to your RB2B dashboard.
Open the chat bubble in the bottom-right corner.
Ask the AI support agent for the CSP exceptions needed for RB2B to run properly.
You’ll receive a list of required domains, headers, and example configurations.
Step 3: Update Your Content Security Policy
Once you have the required details:
Update your site's CSP to include the provided exceptions.
If you're unsure how to do this, your web developer or hosting provider can help implement the changes safely.
Final Check
After updating your CSP:
Reload your website.
Reopen the Console to ensure CSP errors are gone.
Check your RB2B dashboard to confirm that visitor tracking is active.