If you've installed and verified the RB2B tracking script but are seeing fewer profiles than expected, several common configuration or environmental factors may be limiting identification. Use this guide to systematically evaluate and resolve potential issues.

RB2B can often identify a visitor only after multiple sessions. Disabling repeat visitor collection significantly reduces identification rates by removing opportunities to enrich partial data or complete a match.

What to do:
Check your Repeat Visitor Collection settings. Unless you have a specific business reason, this feature should remain enabled to maximize data quality and volume.

RB2B allows customers to limit tracking to specific URLs or patterns. If these restrictions are applied too narrowly—such as only on confirmation pages—you may unintentionally block data collection across most of your site.

What to do:
Review your URL Restrictions and ensure they include all high-intent or high-traffic pages (e.g., product pages, blog posts, pricing pages). Broader coverage generally improves performance.

RB2B exclusively identifies U.S.-based visitors. If your traffic is primarily international, RB2B won’t attempt to track or resolve those visitors.

What to do:
Review your traffic by geography in tools like Google Analytics. If needed, consider adjusting your targeting strategies to drive more U.S. traffic to key pages.

For RB2B Pro+ subscribers, average performance is as follows:

Actual results may vary based on traffic quality, use of VPNs or proxies, and visitor behavior. Discrepancies may also arise due to differences in tracking methodologies between RB2B and other tools, such as Google Analytics, which may report inaccurate locations or subsets of pages.

What to do:
Make sure your expectations align with these benchmarks, and recognize that return visits and complete sessions are often necessary to trigger a full identification.

RB2B gives you the option to exclude traffic from specific domains (e.g., your own internal IP ranges or development environments). However, overly broad exclusions could suppress valid visitor data.

What to do:
Review your Domain Exclusion List to ensure you’re only filtering traffic that’s truly irrelevant or non-actionable.

If you’ve configured the RB2B script to trigger only after users accept your cookie policy, this may delay or prevent identification—especially if users ignore or reject the banner.

However, a broader understanding of cookie consent laws, particularly in the U.S., can help refine how RB2B interacts with user data. U.S. regulations generally require clear disclosure of cookie use and an option to opt out, rather than explicit consent. Consider these legal principles when configuring your cookie banners. In the United States, most jurisdictions emphasize providing notice to users about cookie usage and offering an opt-out mechanism, rather than requiring explicit consent. This approach contrasts with stricter regions like the European Union, where explicit consent is mandatory.

More guidance: CookieYes + RB2B Integration Overview

Additionally, it is acceptable under U.S. law to include the RB2B opt-out link in the Privacy Policy rather than directly in the cookie banner. This approach simplifies compliance while still providing users the necessary mechanisms to opt out. This placement not only meets compliance requirements but also ensures that users can easily find and manage their preferences without cluttering the cookie banner.

Server-side caching can cause outdated pages to load, preventing new scripts (like RB2B) from being included.

What to do:
Clear your server cache after installing or updating the RB2B script. If unsure, contact your hosting provider or web developer to confirm that the live version of your site contains the tracking code.

If you're using WordPress, performance plugins like WP Rocket, W3 Total Cache, or Autoptimize may block or defer the RB2B script due to caching, minification, or deferred loading settings.

What to do:

To resolve low identification rates: