← Back to Knowledge Base
Affect Performance Team
|News|Nov 17, 2026

RB2B Improves Visitor-to-Company Matching and Launches Profiles API

In October 2026, RB2B introduced several updates to its website visitor identification platform. The changes focus on matching identified people to their current employers, providing programmatic access to visitor profiles through a new API, and fixing domain exclusion and webhook issues. For B2B marketers, these updates affect how visitor intelligence is associated with target accounts and passed into CRM, analytics, and sales systems.

Improved Visitor-to-Employer Matching

On October 14, 2026, RB2B updated the process that links identified individuals to records of their current employers. This matters because identifying a person does not necessarily mean their company has been identified correctly. A contact data provider might still associate someone with a previous employer, causing a visit to be attributed to the wrong target account.

RB2B says the update produces a modest increase in visitor resolution rate and a more meaningful improvement in people-to-company matching accuracy. The company did not publish numerical test results, the validation sample size, or an independent accuracy assessment. These are vendor claims, not a verified improvement measured in percentage points.

ABM teams should still verify important account associations before using resolved visitor data to personalize outreach or prioritize an opportunity.

Profiles API: Programmatic Access to Identified Visitors

On October 5, 2026, RB2B introduced the Profiles API for retrieving identified website visitors directly into customer systems. Previously, profiles were primarily accessed through the RB2B interface, CSV exports, and third-party integrations. The new endpoint makes recurring data pulls possible.

Profiles are retrieved with GET https://app.rb2b.com/api/v1/profiles. Responses use JSON and sort profiles by most recent site visit. Requests support limit, cursor, since, and until parameters. The default page size is 25 profiles, with a maximum of 100 per request. A next_cursor value enables pagination until all matching records have been retrieved.

The API exposes up to 90 days of history. For older historical records or an initial bulk transfer, RB2B recommends CSV Export. Profiles API is request-based rather than an event push; the separate Webhook Integration is intended for real-time notifications when new profiles are identified.

Available Profile Fields and API Limitations

Depending on data availability, a profile may include a person's name, job title, business email, LinkedIn URL, employer, company website, industry, employee count, and estimated company revenue. It can also include geographic attributes, visit time, Referrer, Captured URL, and profile tags.

Marketing teams can join visited-page information to identified companies in a warehouse, while sales teams can match visitor profiles against CRM contacts and target accounts.

The API returns the available fields for each profile. It does not let users request only selected fields, search for a person by email or LinkedIn URL, or filter directly by industry, revenue, company size, or profile type. Those operations require downstream processing. The endpoint is read-only: profiles cannot be created, updated, or deleted through it.

Synchronizing Visitor Data With CRM and Analytics

An integration can poll the API on a recurring schedule and pass a since parameter to retrieve profiles whose most recent website visit occurred after the prior synchronization. The retrieved data can be matched to CRM companies and contacts, incorporated into ABM audiences, or analyzed alongside campaign and opportunity data in a warehouse.

The since and until filters are based on the profile's last visit, not the date on which RB2B originally identified the person. This distinction matters when building incremental ingestion: a previously known visitor who returns should not be excluded simply because the profile was first seen in an earlier period.

RB2B specifies a limit of 60 requests per minute per API key, with an additional per-IP limit. At 100 profiles per response, the theoretical ceiling is 6,000 profiles per minute, before practical constraints and retries. For large historical loads, the vendor recommends CSV Export and using the API for ongoing incremental synchronization.

Profiles API Access, Authentication, and Rate Limits

Profiles API is available on eligible paid premium RB2B plans and to OEM Partner Program participants. Free and Starter subscriptions do not include API access.

Account settings provide an API key that can be copied, regenerated, or deleted. Only one key is active at a time. Regenerating it invalidates the old key, so connected systems must be updated. Requests can authenticate with the Api-Key header or Authorization: Bearer.

API access is also tied to subscription status. Ineligible plans, canceled subscriptions, or overdue payments return HTTP 403. Exceeding a request limit returns HTTP 429 with a Retry-After header that tells an integration when to retry.

Domain Exclusion List and Webhook Fixes

On October 5, RB2B fixed an issue affecting the Domain Exclusion List, which is used to exclude an organization's own employees, existing customers, and other unwanted company visits. The list now correctly enforces its limit of 250 domains.

On October 2, RB2B also corrected an issue that could introduce an unwanted trailing space into a website URL in a webhook payload. That kind of formatting defect can break exact-match URL or domain joins in downstream systems.

A further October 5 fix addressed Hot Leads tags that use company revenue requirements.

About RB2B and Its Role in Account-Based Marketing

RB2B provides website visitor identification for B2B companies, resolving organizations and, where supported by the available data, individual visitors. It combines visitor activity with professional and business attributes and supports integrations with CRMs and sales automation workflows.

The October updates address two connected requirements: more accurate people-to-company association and more flexible access to the resulting profiles. Both are useful for account-based marketing, but inferred company identity remains a data-matching result, not proof of employment or purchase intent. Teams should validate critical associations and follow applicable privacy and outreach requirements before taking action.

Trust Us Transform Your Performance Marketing.

Turn identified B2B website traffic into qualified opportunities. We connect visitor intelligence, target-account segmentation, CRM data, and campaign attribution so your team can measure which accounts move toward revenue.

Build Your ABM Measurement Strategy

Sources