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.
1. Repeat Visitor Collection Is Disabled
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.
2. URL Restrictions Are Too Narrow
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.
3. Low U.S.-Based Website Traffic
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.
4. Identification Rate Expectations
For RB2B Pro subscribers, average performance is as follows:
Person-Level Identification: ~40–45% of U.S. traffic is resolved at the individual level, with direct contact details.
Total Identification (Person + Company): ~70–80% when company-level identification is included.
Actual results may vary based on traffic quality, use of VPNs or proxies, and visitor behavior.
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.
5. Domain Exclusion List Is Filtering Useful Traffic
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.
6. Script Tied to Cookie Policy Acceptance
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.
What to do:
RB2B only requires cookie disclosure (not consent) for U.S.-based users.
If your company policy allows it, remove the requirement for user acceptance to run the script.
If you're using CookieYes Cookie Consent, RB2B integrates automatically—just ensure the banner is configured to encourage acceptance.
More guidance: CookieYes + RB2B Integration Overview
7. Server-Side Caching Is Blocking Script Execution
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.
8. WordPress Plugin Interference
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:
Clear all plugin caches after implementing the script.
Check for plugin settings that delay or block JavaScript execution.
Whitelist the RB2B script or exclude it from optimization/minification if needed.
Summary: Top Troubleshooting Actions
To resolve low identification rates:
Ensure repeat visitor collection is enabled
→ Repeat Visitor SettingsConfirm URL restrictions aren’t too narrow
→ URL Restrictions GuideVerify that your audience is U.S.-based
→ What to Look for When Comparing RB2B Stats to Google AnalyticsUnderstand identification benchmarks (40–45% person-level, 70–80% total for Pro plans)
Check domain exclusion list
→ Domain Exclusion SettingsReview cookie banner behavior and script activation
Clear any server-side caches
Check plugin compatibility (WordPress sites)