Prevalence: ★★★★★
It’s common for websites to use cookie policy banners that block scripts, including the RB2B tracking script, until the user accepts the policy. If you're using such a banner, ensure that the RB2B script is set to fire after the policy is accepted.
Additionally, if a visitor declines the cookie banner, RB2B cannot proceed with identification, as it is designed to respect user privacy.
Reminder: Users sometimes overlook this setting and forget to update their software to ensure that RB2B runs after the user accepts the policy. If the RB2B script runs before a visitor interacts with the cookie banner, cookies cannot be set initially. Even if the visitor later accepts cookies, identification typically won’t occur until a subsequent page view, often resulting in more company-level identifications but fewer person-level identifications.
Best Practices for Optimizing Identification Rates
To maximize RB2B’s visitor identification capabilities:
Ensure Prompt Interaction: Design cookie banners to encourage immediate user interaction. Clear and concise messaging can help users make quicker decisions.
Positioning and Visibility: Place the cookie banner prominently on the page to ensure it is noticed and acted upon promptly.
Educate Users: Provide brief explanations about the benefits of accepting cookies, such as personalized experiences or improved functionality.
Impact on Collection Rates
It's important to understand that linking RB2B’s functionality to cookie acceptance may result in fewer identified visitors, as only those who accept the policy will be tracked. While this setup complies with privacy regulations, users should be aware that they may see lower-than-average collection rates as a result.
This distinction is important because delayed consent often results in more company-level identifications but fewer person-level identifications, further impacting the overall collection rates.