RB2B

Considerations When Controlling RB2B's Functionality With Your Cookie Policy Banner

When using RB2B on a website that requires cookie consent, the tracking script must respect the consent model defined by your consent management tool. Loading the RB2B script only after users accept cookies ensures compliance with privacy regulations while preventing tracking errors that can occur when scripts run before consent is granted.

Load the RB2B script only after consent

Why this matters

Privacy regulations require websites to obtain permission before setting cookies that collect personal data. If your site uses a cookie banner or consent manager, the RB2B tracking script should only load after a visitor has accepted cookies. This ensures both legal compliance and reliable visitor identification.

How to achieve it

  • Display a cookie consent banner when visitors arrive on your site
  • Block RB2B’s tracking script during the initial page load
  • Load the RB2B script only after the visitor accepts cookies
  • Allow the script to write cookies and begin tracking after consent

Quick win

Open your site in a private browser window and confirm the RB2B script does not load until cookies are accepted.

Implement consent-based script loading

Why this matters

Proper implementation ensures that tracking scripts activate only after the user has provided consent. This prevents compliance issues and avoids situations where visitor identification fails because the script executed before consent was granted.

How to achieve it

Initial page load

  • Do not load the RB2B script when the page first loads
  • Display a cookie consent banner requesting permission

User interaction with the banner

  • Detect the consent event when the visitor clicks “Accept”
  • Dynamically load the RB2B script after acceptance
  • Allow tracking and cookie writing after consent

Verification

  • Test the implementation using private browsing
  • Confirm the script activates only after consent
  • Check that RB2B cookies appear only after acceptance

Quick win

Use your browser’s developer tools to verify that the RB2B script loads only after the consent event fires.

Avoid loading the script before consent

Why this matters

A common mistake is loading the RB2B script immediately but delaying cookie creation until the user accepts cookies. This approach can break script functionality and prevent proper visitor identification.

Problems with this approach

  • The script may expect cookies to be written during execution
  • Delaying cookie creation can disrupt the identification process
  • If consent occurs after execution, the script may not retry identification

Best practice

Do not load the script at all until the visitor accepts cookies.

Quick win

If your banner currently loads scripts immediately, update it to block RB2B until consent is granted.

Configure your consent management tool correctly

Why this matters

Many websites rely on third-party consent management tools to control cookie behavior. These tools must be configured correctly to ensure RB2B tracking activates only when permitted.

How to achieve it

  • Add RB2B to the list of scripts controlled by your consent tool
  • Ensure the script is blocked until consent is granted
  • Confirm that consent preferences trigger script activation

Quick win

Review your consent manager settings to confirm RB2B is included in the scripts controlled by the banner.

Example: Using CookieYes

Why this matters

Some consent platforms automatically manage script activation, making implementation easier.

How it works with CookieYes

  • Install the RB2B script normally on your website
  • CookieYes detects and pauses RB2B until consent is granted
  • Tracking activates automatically after the visitor accepts cookies

Additional benefit

CookieYes can also allow RB2B to recognize user opt-outs automatically.

Quick win

If using CookieYes, confirm RB2B appears in the platform’s managed scripts list.

Troubleshooting tracking issues

Why this matters

If RB2B fails to identify visitors or appears inactive, the issue is often related to script placement or consent configuration.

How to troubleshoot

  • Confirm the RB2B script is installed correctly
  • Verify the consent banner controls script execution
  • Test the site in a private browsing window
  • Check that cookies appear only after consent is granted

Quick win

Run a test visit in incognito mode to confirm the script activates after accepting cookies.

Transparency and opt-out

Why this matters

Providing visitors with clear control over their data improves trust and strengthens compliance with privacy regulations.

How to achieve it

  • Ensure your privacy policy explains tracking technologies
  • Include the RB2B opt-out link where appropriate
  • Allow visitors to modify consent preferences at any time

Quick win

Verify that your privacy policy and cookie banner clearly explain how tracking technologies are used.