At this time, RB2B does not support the ingestion of external suppression or exclusion lists, such as CSV uploads of IP addresses, domains, or user identifiers. This functionality is not currently on our development roadmap.
Why users ask about suppression/exclusion lists
This request typically comes from users who want to prevent certain types of traffic from being tracked or identified by RB2B. Common examples include:
Internal team members: Marketing, sales, or development staff who frequently visit the website and should not be counted or analyzed.
Test traffic: Visits generated during QA testing or internal reviews.
Low-intent traffic: Visitors landing on resource-heavy but conversion-light pages, such as careers pages, support portals, or blog articles.
Known contacts or partners: Individuals who have already been engaged and don't need further qualification.
While RB2B doesn't currently allow suppression via data uploads, there are tools built into the platform that can achieve similar outcomes.
Available Workarounds
1. Prevent Coworker Identification Tool
RB2B offers a built-in option to exclude internal teams from being tracked. This tool works by setting a cookie in the browser of your team members to prevent them from being identified or included in reporting.
How to use it:
Share a dedicated opt-out link (found in your RB2B dashboard) with your internal team.
When they click the link, the cookie is set, and RB2B will automatically exclude them from all future identification attempts on that browser/device.
Best for:
Sales, marketing, or engineering teams that frequently visit the site.
Ensuring internal testing and usage doesn’t skew lead data.
2. URL Restriction Tool
You can configure RB2B to ignore specific URLs or page paths on your website. This allows you to exclude traffic from areas of the site that are less relevant for lead generation or customer engagement.
Use case examples:
/careers/support/blog
How to use it:
In your RB2B dashboard, access the URL restriction settings.
Add full or partial paths you want to exclude.
RB2B will not attempt to identify any visitors who land on or primarily interact with those pages.
Best for:
Pages with high traffic but low buying intent.
Avoiding false positives from informational content or customer support.
Summary
While direct suppression list uploads aren't supported, RB2B offers practical tools to help you control which visitors are identified and included in your reporting. Between internal team suppression and page-level exclusion, you can tailor the tracking experience to focus on high-value traffic and avoid cluttering your data with irrelevant or already-known visitors.
If you have a more complex use case or are looking to implement advanced filtering logic, our support team is happy to consult on the best setup using existing tools.