If you're unable to confirm your script installation using the built-in verification tool in the RB2B dashboard, you can manually verify that the script has been properly added to your website by following these steps:
Step 1: Open Your Browser's Developer Tools
To begin manual verification, you’ll need to access the Developer Tools panel in your browser. This panel allows you to inspect the underlying code and resources loaded on your website.
This step is also crucial for validating the correct implementation of the RB2B script on your website.
How to open Developer Tools
Mac: Press
Command + Option + Ion your keyboardWindows: Press
Ctrl + Shift + IorCtrl + Alt + IAlternatively, you can right-click anywhere on your webpage and select "Inspect" or "Inspect Element" from the context menu.
Step 2: Navigate to the Console
Once Developer Tools is open, locate and click on the Console tab. This tab allows you to run JavaScript commands and view output directly from your website.
Note: If the Console tab isn’t visible, you may need to expand the list of tabs (usually found at the top of the Developer Tools panel) to find it.
Step 3: Check If RB2B's Script Is Running
To confirm that the RB2B tracking script is properly installed and functioning:
Click into the command line input at the bottom of the Console.
Type
reb2band press Enter on your keyboard.
This will return a JavaScript object that includes key status indicators related to your installation and account configuration.
If the expected result is not returned, environmental factors like browser caching or server setup could be causing the issue; clearing the browser cache and retrying is recommended. Additionally, if you are using a script management tool like Google Tag Manager, publish a new version to ensure the changes take effect. If you are using a single-page application or custom routing, ensure the RB2B script reinitializes on every route change or page view, as failing to do so can prevent events from being tracked on subsequent views.It is important to note that any visitor data missed during periods when the script is inactive or misconfigured cannot be recovered. Ensuring the script is always active is crucial to avoid permanent data loss.
If functioning as expected, it should return:
Proxy(Array) {methods: Array(2), factory: ƒ, identify: ƒ, collect: ƒ}
What It Means If You See Uncaught ReferenceError: reb2b is not defined
If you see the following error in your browser’s Console: Uncaught ReferenceError: reb2b is not defined this means that the RB2B tracking script is either:
Not installed on the page, or
Installed incorrectly, with a syntax error or modification that is preventing it from running.
It is also possible that although the built-in test tool reports a failure, the script could still be actively recording visitor data. Double script installations or legacy scripts from previous trials can also cause conflicts. Ensure only the correct script is installed and remove any outdated or incorrect scripts. Additionally, limitations in your RB2B plan or the geographic location of your traffic may affect tracking functionality. Entry-level plans may have restricted identification capabilities, particularly for international visitors. Consider upgrading your plan if higher identification rates are critical for your business.Missed data from periods when the script was inactive or misconfigured cannot be recovered. To maintain accurate visitor analytics, ensure the script remains active and properly configured at all times.
How to Resolve This
To fix the issue:
Double-check that the script has been added to your site — preferably in the
<head>or just before the closing</body>tag.Ensure the script has not been altered during copy-paste. Even small formatting changes can break the script’s functionality.
Confirm that the script is loading from the correct source URL and that it’s not blocked by any browser extension, ad blocker, or firewall.
Check for lazyOnload restrictions in the script settings and remove them to ensure the script loads properly with the site.
Additionally, if the verification tool indicates a failure, but the script is correctly implemented, it may still function correctly to collect visitor data. If multiple accounts are associated with scripts, merge the new account into the previous one and subscribe the merged account to the appropriate plan to avoid conflicts. Daily recap emails are only sent if at least one visitor is recorded on a given day. If no visitors are detected, no email will be generated. Ensure your website is receiving traffic to trigger these notifications.
We recommend referencing the following resources:
These provide detailed instructions for proper setup and help you ensure the script is correctly implemented and recognized by your site.
Tip: After making changes, refresh your website and check the Console again for any remaining errors.
Common Script Installation Issues and Best Practices
Common Issues
Double script installations can cause conflicts; ensure only the correct script is installed.
LazyOnload restrictions may prevent scripts from loading; remove these restrictions.
Legacy scripts from previous accounts or trials can interfere; remove outdated scripts.
Cache-related issues may persist; clear browser and server caches and publish updates in script management tools.- Single-page applications or custom routing may require the RB2B script to reinitialize on every route change or page view to ensure proper tracking.
Plan limitations can restrict identification capabilities, particularly for international traffic; consider upgrading if necessary.- Tracking script deactivation can interrupt data collection; ensure the script is always active to avoid data gaps.
Domain configuration mismatches, such as discrepancies between "www" and non-"www" domains, can prevent the script from functioning; update script settings to match your live domain.
Best Practices
Regularly verify installed scripts to avoid duplicates or legacy scripts.
Monitor and update scripts using tools like Google Tag Manager.
Clear caches after making changes to ensure updates are reflected. By following these practices, you can maintain a functional and conflict-free website.- Configure the RB2B script to reinitialize on every route change or page view, especially for single-page applications or custom routing.
Set realistic expectations based on your RB2B plan’s capabilities and upgrade if higher identification rates are critical.- Regularly verify that the tracking script is active and correctly configured to ensure continuous data collection.
Monitor and update domain configurations in the script settings to reflect any changes to your website's domain or platform.
Identify and address factors that could lead to script deactivation, such as platform updates or manual errors.