If you’re coming from RB2B
RB2B documents three errors and asks you to hand-create two properties before some syncs work. Squid ID creates its properties for you and handles more failure modes automatically.| RB2B | Squid ID | |
|---|---|---|
| Manual property prerequisites | LinkedIn + Industry | None (auto-created) |
| Token refresh | Manual reconnect | Automatic |
| Rate-limit handling | Not documented | Automatic retry with backoff |
Why this matters. The connector is built to recover on its own where it can (refresh, retry, dedupe) so the list of things you have to fix by hand is short.
Contacts are not appearing
Work through these in order:- The connector is paused. Check the HubSpot card on Settings → Integrations and make sure the toggle is on.
- The visitor has no email. HubSpot contacts require an email, so a visitor we can’t resolve to an email is skipped. This is expected.
- Your targeting is too tight. If Sync is set to a specific ICP or a specific high-intent page, only those visitors sync. Set it to All identified visitors to confirm, then narrow again.
- A requirement is excluding them. “Require a company / LinkedIn” and the email-type setting are AND gates. Loosen them to test.
- Send is set to once. In once per visitor mode a person already synced won’t sync again. Switch to every identified visit if you expect repeat syncs.
Squid ID+ fields are empty
squid_mobile_phone, squid_personal_email, and squid_home_address (and the standard mobile/address fields) are populated only for records that are unlocked. Turn on Squid ID+ Automatic for the website, or reveal the record, and they fill in on the next sync.
A field I expected wasn’t updated
By design. On an existing contact Squid ID writes only itssquid_ properties and never overwrites standard fields your team manages. The standard fields (name, job title, mailing address) are set only when the contact is first created. See what HubSpot receives.
Duplicates
Squid ID matches contacts by email and upserts, so it does not create a second contact for an email that already exists. Duplicates in HubSpot usually predate the connection or come from a different email variant (for examplejane@acme.com vs jdoe@acme.com). Merge those in HubSpot.
Reconnect or disconnect
- Reconnect: open the HubSpot connector and connect again. The connector refreshes its own access token automatically, so you rarely need to do this, but a revoked app or changed permissions will require it.
- Disconnect: open the connector and click Disconnect. This removes the connection from Squid ID. To also remove it inside HubSpot, go to Settings → Integrations → Connected Apps there and revoke it.
Frequently asked
Does connecting overwrite my existing HubSpot data?
Does connecting overwrite my existing HubSpot data?
No. New contacts get the standard fields; existing contacts get only the
squid_ properties. Your team’s fields are never overwritten.Do I need to create any properties first?
Do I need to create any properties first?
No. Squid ID creates its
squid_ properties (and their group) automatically when you connect.Will it sync my historical visitors?
Will it sync my historical visitors?
No. The connector syncs visitors identified after you connect. It does not backfill past records.
Can I connect more than one website?
Can I connect more than one website?
Yes. The connection is per website. Switch the active site and connect each one; routing and actions are set per site.
Public app or Private App token?
Public app or Private App token?
Both work. The public app is one-click OAuth and is the normal choice. A HubSpot Private App token is an alternative for a single portal; paste it in the connector instead of using OAuth.
What about rate limits?
What about rate limits?
The connector respects HubSpot’s limits and retries on a rate-limit or server error with backoff. Mapping errors are not retried so they don’t loop.