This article provides general best practices and does not constitute legal advice. For specific guidance tailored to your situation, consult a qualified legal professional specializing in data privacy.
Integrating RB2B with your website requires strict adherence to privacy laws and user consent standards. A Consent Management Tool (CMT) is essential for ensuring legal compliance and enabling RB2B to function effectively. This guide outlines key best practices to help you integrate RB2B responsibly and in accordance with data protection regulations.
Use a Consent Management Tool at All Times
Always implement a Consent Management Tool when using RB2B. A CMT allows you to collect and manage user consent transparently, ensuring compliance with privacy regulations like GDPR, CCPA, and others. This not only protects user data but also builds trust with your visitors. For more information on recommended
Stay Compliant with Regional and Federal Privacy Laws
Regulations differ by region. For instance, the GDPR (EU), CCPA (California), and other laws each have unique consent requirements. Ensure your consent practices align with the legal obligations of the regions you serve. Regularly review changes to legislation that may affect your data collection processes.
RB2B does not have specific consent requirements. It is your responsibility to ensure your site is configured in line with the consent laws of each jurisdiction you operate in, and that RB2B only attempts to identify visitors at appropriate times.
RB2B does not require user consent to run — only cookie disclosure, in line with U.S. standards.
If your jurisdiction requires explicit consent before setting cookies, ensure the RB2B snippet only loads after consent is granted.
If you're using CookieYes, RB2B integrates automatically — just make sure your banner is configured correctly for your requirements.
For other cookie management tools, ensure your Privacy Policy clearly describes cookie use and that users have access to an opt-out mechanism.
Follow Internal Privacy and Consent Policies
In addition to legal compliance, align with your organization’s internal privacy policies. These may set higher standards than the law requires, and maintaining consistency supports your company’s values and public commitments regarding data ethics.
Understanding CCPA: Notification vs. Consent
Under the CCPA, businesses must notify users about cookie usage but can choose between:
Notifying users of cookie use (informational approach), or
Requiring active consent from users to accept or deny cookies.
If you choose the consent-based model, it’s critical that RB2B's tracking script only runs after users have accepted cookies.
Consent and Script Activation
If you implement a consent model requiring user opt-in:
Do not load RB2B’s tracking script until after consent is given.
This is essential for two reasons:
Legal compliance: Activating tracking before consent may violate privacy laws.
Functionality: The RB2B script depends on proper consent to collect and process user data accurately. Premature loading can lead to incomplete or unusable data.
Conclusion
Using a Consent Management Tool with RB2B is essential for legal compliance and effective tracking. Follow these best practices:
Always use a CMT
Align with applicable privacy laws and your internal policies
Load the RB2B script only after consent is obtained
These steps help ensure that your use of RB2B respects user privacy, avoids legal pitfalls, and maximizes the value of the data you collect. As always, consult legal experts to ensure full compliance with all relevant regulations.