Skip to main content
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.
Blinq automatically creates the following custom properties in your HubSpot account when you connect. You don’t need to set anything up manually.

​
Contact fields

When you export contacts, Blinq applies the standard field mapping below. To customize which fields Blinq syncs and how they map, see Blinq field mapping.

​
Meeting and interaction records

When you export contacts, Blinq also pushes their associated interactions to HubSpot as Meeting objects, linked to the contact record.

​
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.