Skip to main content

Verifying Your Script Installation

The built-in script verification tool serves primarily as a convenience to assist with the installation process. Importantly, the script will automatically verify itself the moment it transmits the first byte of data, making manual verification a helpful but not mandatory step. Additionally, the RB2B installation debugger serves as a definitive validation tool, providing a reliable pass/fail status for script installation.

To confirm the successful installation of your RB2B tracking script, please follow these steps:

  1. In your dashboard, click on Script from the sidebar menu.

  2. Locate your domain and click the Test script button next to the Unverified label to begin the validation process.

What to Expect When Verifying Your Installation

A pop-up window showing your website will briefly appear as our services verify the installation.

Do not close the pop-up window. Closing the pop-up will cause the verification to fail.

If we are not able to verify the script installation, click here to troubleshoot.

If you're confident that there are no issues with your script installation and it hasn't been verified yet, wait 5 minutes and try again.

Options For Testing Your Script Installation

Using the Debugger for Validation

The RB2B installation debugger is the primary tool for determining whether the script is correctly installed. Follow these steps:

  • Open the RB2B debugger tool.

  • Check if the debugger indicates that the script is installed and functioning correctly.

  • Address any issues flagged by the debugger, such as Content Security Policy (CSP) errors or consent gating problems.

  • Treat the debugger’s pass/fail status as the definitive indicator of installation validity, even if other tools or UIs show conflicting messages.

1. Testing Your Primary Domain

By default, RB2B will test against the domain that you have set as your Primary Domain on your account.

Best practice is to have set your Primary Domain as a naked domain, meaning it doesn't have www. or any subdomains in front of it. This will allow the script to automatically work on any subdomains on which it is installed.

Without making any changes, click Yes, Continue to perform the script verification test and wait for the results of the test.

2. Testing a Subdomain

To test a particular subdomain, simply add the subdomain to the field before your domain. When added, RB2B will automatically add a period in front of your domain for you.

Example: To test app.retention.com, add app in the subdomain field.

When ready, click Yes, Continue to perform the script verification test and wait for the results of the test.

3. Testing a Page on Your Primary Domain

To test a particular page on your Primary Domain, simply add the page slug to the field after your domain.

Examples:

  • To test retention.com/settings add settings in the page field.

  • To test retention.com/settings/user add settings/user in the page field.

When ready, click Yes, Continue to perform the script verification test and wait for the results of the test.

4. Testing a Page on a Sudomain

To test a particular subdomain, simply add the subdomain to the field before your domain and add the page slug to the field after your domain.. When added, RB2B will automatically add a period in front of your domain for you.

When ready, click Yes, Continue to perform the script verification test and wait for the results of the test.

Error Messages

Did this answer your question?