If you’re coming from RB2B
RB2B can drop visitors into Reply too, but without ICP filtering or premium contact data, and through a less direct path. Squid ID adds only the visitors that match your ICP, with the work email as the contact and Squid ID+ data attached.| RB2B | Squid ID | |
|---|---|---|
| Connection | Webhook / Zapier | Native (direct API) |
| Who’s added | All visitors | All, by ICP, or by high-intent page |
| Premium contact data | Not provided | Mobile, personal email, address via Squid ID+ |
Why this matters. Reply runs the cadence; Squid ID makes sure only the right people enter it, with the data to personalize. The work email is the contact, and the company, LinkedIn, and (when unlocked) personal email and mobile come along as fields.
Connect Reply.io
1
Get your API key
In Reply.io, go to Settings → API & Webhooks and copy your API key.
2
Paste it
In Squid ID, go to Settings → Integrations and click Connect on the Reply.io card. Paste the key; Squid ID verifies it before saving.
3
Pick a sequence
Choose the Reply.io sequence visitors should enter, then set routing, requirements, and frequency, and Save.
What’s sent
The workemail as the contact (created if new), plus firstName, lastName, title, company, domain, phone, and linkedInProfile. Context and Squid ID+ data ride as customFields: squid_icp, squid_is_icp_match, squid_landing_page, and, when unlocked, squid_personal_email, squid_mobile_phone, and squid_home_address.
The work email is the contact address. The personal email (when ID+ is unlocked) is a custom field, not the send-to address, so cold outreach goes to the work inbox by default.
Pause or disconnect
- Pause: Use the toggle on the Reply.io card to stop sending without losing the key or settings.
- Disconnect: Open the connector and click Disconnect.