Every data point Blinq syncs to HubSpot: standard contact fields, custom properties, and meeting interaction records.
Custom properties created by the Blinq integration
Don’t delete or rename these properties in HubSpot. Blinq uses Blinq ID for contact deduplication. Removing it creates duplicate contact records on re-export.
| Property name | What it contains | Populated when |
|---|
| Blinq Tags | Contact-level tags assigned in Blinq | On contact export (if tags enabled) |
| Blinq Workspace Tags | Workspace-level tags | On contact export (if tags enabled) |
| Blinq Campaign Tags | Tags from campaigns the contact is part of | On contact export from a campaign |
| Blinq Campaigns | Names of campaigns the contact belongs to | On contact export from a campaign |
| Blinq Card | Direct link to the contact’s Blinq card | On every contact export |
| Blinq ID | Unique Blinq identifier used for deduplication | On connect (bootstrapped), on every export |
| Blinq field | HubSpot field |
|---|
| First name | First name |
| Last name | Last name |
| Email (first/primary) | Email |
| Phone number | Phone and/or Mobile |
| Company | Company name |
| Job title | Job title |
| Website | Website |
| Address | Address |
| Blinq ID | Blinq ID |
| HubSpot Owner (matched from Blinq contact owner) | Contact Owner |
Meeting & interaction records
When you export contacts, Blinq also pushes their associated interactions to HubSpot as Meeting objects, linked to the contact record.
| Data point | HubSpot field | Value |
|---|
| Timestamp | Meeting date | When the interaction occurred |
| Title | Meeting title | ”Interaction from Blinq” |
| Body | Meeting description | ”Interacted with {contact name}“ |
| Location | Location | Where the interaction took place |
| Duration | Start / end time | Interaction time + 15 min default duration |
Deduplication
HubSpot uses email address as the unique identifier for contacts. When you export a Blinq contact, HubSpot matches it to any existing contact with the same email and updates that record instead of creating a duplicate.
If a matching contact is already managed by another source, Blinq leaves it unchanged rather than overwriting it.
Your CRM has the final say on every export. Duplicate and matching rules, required fields, and validation rules set up in your CRM can change how a record is matched, allow a duplicate to be created, or block an export entirely.
Need help?
For any questions or issues, contact Blinq support or email support@blinq.me.