The RB2B Installation Debugger checks whether your RB2B tracking script is correctly installed and running on your site. This article explains every result you may see — what it means, and what to do about it.
Overall Result Banner
Once all checks are complete, the validator displays one of three top-level results:
Type | Reason | Information | Fix |
Pass | Installation verified | Everything looks good! Your RB2B script is installed correctly and you're ready to go. | No fix required. |
Warning | Script requires user interaction | The script was found, but only after simulated user interaction. Performance will be hindered. Review the checks below to resolve this and ensure your install is optimized. | Suggested fix(es) will be provided. |
Fail | Installation issue detected | One or more checks failed. The specific cause is shown in the individual check results below. | Required fix(es) will be provided. |
Note: The debugger does not affect the Verified/Unverified status in your dashboard. That status updates automatically as soon as RB2B detects a visitor, so it may still show "Unverified" temporarily until your first visitors are recorded.
Status Color Reference
Each check result is color-coded for quick scanning:
Pass | Green — the check passed with no issues. |
Warning | Amber — the script was found but something may limit performance. Action recommended. |
Fail | Red — the check failed. Action required for the script to work. |
Info | Blue — informational only. No action needed. |
Individual Checks
The validator runs up to seven checks in sequence. Each check returns a status of Pass, Warn, Fail, or Info. The sections below explain every possible outcome.
1. WWW Redirect Check
Detects whether your URL redirects between the www and non-www version of your domain. This check is only shown when a redirect is detected.
Type | Reason | Information | Fix |
Fail | WWW redirect will break the script | The URL you submitted redirects to the non-www version, but your RB2B account authorizes the www domain. These are treated as different domains, so the script will fire but visitor identification will not work. | In your RB2B account, go to your Script page, delete the www domain, click "+ Add Domain", add the non-www version, and make it active. |
Info | Redirected to www version | The URL you submitted redirected to the www version. Validation was performed on the www version. Because you authorized RB2B on the naked domain, the script will function correctly on the www version and any subdomains as well. | No fix required. |
If this check is not shown in your results, no redirect was detected and no action is needed.
2. Consent Management Platform (CMP) Detection
Checks whether a Consent Management Platform — such as a cookie consent banner — is present on the page. This check is always shown.
Type | Reason | Information | Fix |
Info | No consent banner detected | No CMP was found. The script should load freely without a consent gate. | No fix required. |
Info | [CMP Name] detected | A consent management platform was found on this page. The validator will proceed to test how the script behaves in relation to the consent flow. | No fix required. |
Many jurisdictions require users to be notified of cookie usage. We strongly recommend adding a consent management tool if your site is accessible to users in those regions.
3. CMP Consent Flow
Only shown when a CMP is detected. Tests whether the RB2B script loads before or after a user accepts cookies.
Type | Reason | Information | Fix |
Pass | Script loads before consent | The script fires before the user has accepted cookies. Depending on your compliance requirements, this may be intentional — worth double-checking with your legal team. | No fix required. |
Pass | Consent flow working correctly | The validator clicked Accept on the consent banner and the script loaded as expected. The script is correctly gated behind consent — users who accept will trigger the script; those who decline will not. | No fix required. |
Warning | Couldn't click the consent button automatically | The validator couldn't automatically interact with the consent banner. This doesn't necessarily mean there's a problem — some CMPs use custom or iframe-based banners that are harder to interact with programmatically. | Test the consent flow manually in your browser to confirm the script loads after a user accepts. |
Fail | Script didn't load after consent | The validator accepted consent via your CMP but the script still didn't appear. | Check that the script is mapped to the correct consent category in your CMP, and verify there are no misconfigurations in your tag manager. |
4. Script Detection
The primary check. Scans the page DOM and all network requests for the RB2B script tag. This result drives the overall pass/fail status.
Type | Reason | Information | Fix |
Pass | Script found | The script tag was detected on this page on initial load. Installation is in place.
| No fix required. |
Warning | Script only loads after user interaction
| The script wasn't present on page load, but appeared after the validator simulated scrolling and mouse movement. This will significantly limit visitor identification — anonymous page views (the most common type) won't be captured at all.
| Load the script unconditionally on page load, rather than triggering it on user interaction. |
Fail | Script not found
| The validator scanned the page DOM and all network requests but couldn't find any matching script tags.
| Common causes: the script hasn't been installed yet; it was installed recently but your site cache hasn't been cleared; or it's behind a consent gate the validator couldn't unlock. Try clearing your site cache after installing. If you're using a consent manager, ensure the script loads after consent is granted. |
5. Malformed Snippet Check
Only shown when the script tag is not found during detection, but a broken or corrupted version of the RB2B snippet is detected in the page source.
Type | Reason | Information | Fix |
Fail | Snippet found but appears malformed | One or more issues were found in your RB2B snippet that would prevent it from running.
| Expand the check card in the validator for per-issue detail and suggested fixes. |
Common issues the validator detects:
Curly or smart quotes used instead of straight quotes in the script tag
Script src URL broken across multiple lines
Missing or extra characters in the script src
Incorrect protocol or domain in the script src
If you copied the snippet from a rich text editor (e.g. a Word document or email), it may have automatically converted straight quotes to curly quotes. Always copy the snippet directly from your RB2B dashboard.
6. Script ID Check
Only shown when a Script ID was provided to the validator AND the script was found on the page. Confirms that the correct account's script is installed.
Type | Reason | Information | Fix |
Pass | Script ID matches | The expected script ID was found in the script src. The correct account's script is running.
| No fix required. |
Fail | Script ID mismatch | The script is installed, but the script ID doesn't match. A different account's script may be running. If another team member set up RB2B, you may need to merge accounts or use their existing setup. | Check your tag manager or hardcoded snippet to confirm the correct script ID is being used. |
7. Content Security Policy (CSP) Check
Checks your site's Content Security Policy HTTP headers to ensure the domains required by the RB2B script are allowlisted.
Type | Reason | Information | Fix |
Pass | No CSP issues
| No Content Security Policy violations were detected. Either no CSP header is present, or the required RB2B domains are already allowlisted.
| No fix required. |
Fail | CSP is blocking your script
| Your site's Content Security Policy is preventing the RB2B script from loading. The script will not be able to identify visitors until this is resolved.
| Expand the check card in the debugger to obtain the necessary entries for your CSP headers. |