Confirm HubSpot is connected under RB2B > Integrations. These settings only appear once the connection is live.

You'll need admin access in RB2B to change integration settings, and enough permissions in HubSpot to create contacts, companies, and custom properties.

Decide whether you're running a Signal-First approach (sync broadly, refine later) or a TAM-First approach (only sync contacts and companies matching a defined target list) before changing any setting below. Every recommendation on this page depends on which one you're running.

Settings changes apply going forward only. A contact or company that was ignored under a previous setting won't retroactively sync once you change the toggle.

Businesses that want to maintain visibility into account-level engagement even when individual visitor identification isn't possible.

Marketing teams tracking anonymous interest from known accounts, to inform account-based marketing (ABM) strategies.

Sales teams that want early signs of activity from target companies, even before a named contact is identified.

Analytics users who want a fuller picture of total company activity across the funnel, not just from identified leads.

Teams that only want data tied to fully identified individuals and prefer to avoid cluttering their CRM with anonymous or partial records.

Sales teams that prioritize clean pipelines and only work with fully qualified leads.

Operations teams managing tight CRM hygiene standards.

Businesses with strict data quality controls or compliance requirements that discourage storing partial records.

Users who want to collect and track data on all companies identified by RB2B, even if the company isn't already in their HubSpot database.

Teams focused on prospecting or expanding their database of potential business accounts.

Users who already have a comprehensive list of target companies in their HubSpot CRM and prefer to prevent the creation of new, non-targeted companies.

Teams aiming to limit their HubSpot data to pre-qualified or pre-approved companies to reduce clutter.

Users looking to collect information on all website visitors identified by RB2B, even if they're brand new to the system.

Businesses prioritizing comprehensive lead collection for broader engagement or outreach campaigns.

Users who prefer RB2B to update existing contacts only and avoid creating new ones. RB2B would still enrich known contacts with additional details and activity history (page views, other behavioural insights), but wouldn't add completely new entries.

Teams focused on maintaining a clean database, only capturing leads that have been pre-qualified or already engaged.

Users who want to collect contact information for all visitors, regardless of whether RB2B can identify the visitor's company. Useful for teams building lead pipelines even when company details are incomplete.

Businesses that rely on nurturing individual contacts over time, gradually enriching their data.

Users who require company association as a prerequisite for contact creation, e.g. sales teams that exclusively engage leads tied to specific target companies or industries.

Organizations concerned about cluttering their CRM with incomplete records lacking actionable data.

Businesses that want to capture and engage potential leads even when an email address is unavailable. Particularly useful for sales and marketing teams building comprehensive contact records based on other professional details, such as name, company, job title, and LinkedIn profile. Allows tracking of interactions, follow-up assignment, and outreach via other channels like phone or LinkedIn.

Companies that rely on email as their primary method of communication, or use automated email workflows in HubSpot. A contact created without an email address can disrupt existing automation, segmentation, or lead nurturing campaigns that require email-based identification.

Businesses that prioritize data cleanliness and want to avoid incomplete contact records.

The company genuinely doesn't exist in HubSpot yet. Company is skipped, and any contact tied to it may also fail to sync depending on [Without company].

The company does exist in HubSpot but under a different domain (subsidiary, rebrand, regional TLD, alias domain) that RB2B's match doesn't catch. RB2B treats it as new, ignores it, and the visitor never gets attached to the record already sitting in HubSpot.

If contact creation is pipelined through company creation (contact gets attached to a company record as part of the create step), skipping company creation can break the whole contact sync for that individual, not just the association. Worth confirming with eng whether contact sync depends on a company ID being present first.

Genuinely new person, never synced, no record created. Most common ticket, easiest to diagnose since it's all-or-nothing.

Person exists in another system (Salesforce, a spreadsheet, a different CRM) but not HubSpot specifically. RB2B correctly identifies them as new to HubSpot and ignores them, which can look like a data quality problem when it's actually working as configured.

Personal email domains (gmail.com, outlook.com, icloud.com) don't resolve to a company. Any contact identified primarily through a personal email gets skipped here even if [New contact] is set to create.

Company resolution fails due to IP masking: VPNs, mobile carriers, remote workers on residential ISPs. The individual is real and identifiable, but no company comes back, so they're dropped.

This setting is more specific than [New contact] and overrides it for this case. If a customer says "we're set to create new contacts but some are still missing," this is the first thing to check, since it silently carves a subset out of [New contact]'s create behaviour.

New visitor, no email ever captured: contact never created. This is the intended use of the Recommended default, avoiding records with no way to reach the person.

Returning visitor who already exists in HubSpot: email capture doesn't happen on every visit (depends on form fills, chat, intent signals). If the current identification event has no email, and the sync logic treats "no email" as a blocking condition before it attempts to match against an existing record, the update never happens, even though the person is already a known HubSpot contact. This is the scenario where RB2B effectively already knows the contact exists, but the missing email on this particular event trips the ignore rule before that knowledge gets used.

Practical effect: any visit or activity data tied to a no-email identification is lost for that contact, not just new-contact creation. Worth stating explicitly, since Ignore reads as being about record creation, not about blocking updates to contacts that already exist.

[Company creation] = Ignore and [Without company] = Create: contact gets created but with no company association. Not a missing-contact ticket, more a "why isn't this contact linked to their company" ticket.

[Company creation] = Ignore and [Without company] = Ignore: contact never syncs at all, and there's no company record either. Hardest to diagnose, since neither object exists in HubSpot to work backwards from.

[New contact] = Create, but [Without email] = Ignore, and the person's only identification events so far have been email-less: contact looks like it should exist per settings but never does, because it never clears the email gate to reach the create step.

Align With Your Strategy: If your goal is to expand your lead pool and prospect broadly, leaving these settings "on" is advantageous. However, if your priority is to focus on specific accounts or minimize data clutter, toggling certain settings "off" may be better suited for your needs.

Review Data Quality Regularly: Regardless of your settings, it's important to periodically review the data RB2B generates in your HubSpot CRM. This ensures you maintain high-quality records while identifying opportunities for deeper engagement with key leads or accounts.

Leverage Contact and Company Data: Use RB2B's insights to create targeted workflows, personalized marketing campaigns, or detailed sales reports in HubSpot. Enriching your CRM with actionable insights can significantly enhance the efficiency of your marketing and sales efforts.

Test and Refine Settings Over Time: Your business needs may change, so revisit and tweak these settings to ensure they continue to align with your objectives.

Manage Filters Effectively: Use RB2B's filtering options to ensure that only relevant contacts are synced to HubSpot. Regularly review and adjust filters to align with your evolving target audience and business goals.

Contacts Outside the Filter Are Syncing: This usually happens when the filter isn't correctly applied to the HubSpot integration. Edit the filter settings and ensure HubSpot is included in the restriction or target list. Save and apply the changes to resolve the issue.

Low Number of Synced Contacts: If only a small number of contacts are syncing, it may be due to restrictive filter criteria. Review and adjust the filter to ensure it aligns with your target audience.

Timezone Discrepancies: RB2B CSV exports use a day boundary of 00:00 UTC, while the RB2B Dashboard groups activity based on your account's local timezone. This can cause mismatches in data when comparing exports with dashboard views or HubSpot records. Aligning date ranges using the same timezone context can help resolve these discrepancies.

Company-Level vs. Person-Level Syncing: RB2B exports include both person-level and company-level visitors, but if your HubSpot integration is configured to sync only person-level contacts, company-level visitors will not be pushed. Update your integration settings to include company-level records if needed.

Manual-Only Syncing Workaround: While RB2B doesn't offer a native manual-only sync mode, you can create a filter with criteria that no real visitor would match (e.g., a tiny company size in an unlikely location). Configure the integration to auto-sync only profiles matching this filter. With no automatic matches, you can manually push reviewed profiles to HubSpot.