Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.blinq.me/llms.txt

Use this file to discover all available pages before exploring further.

Every data point Blinq syncs to HubSpot: standard contact fields, custom properties, and meeting interaction records.

Custom properties created by the Blinq integration

Blinq automatically creates the following custom properties in your HubSpot account when you connect. You don’t need to set anything up manually.
Property nameWhat it containsPopulated when
Blinq TagsContact-level tags assigned in BlinqOn contact export (if tags enabled)
Blinq Workspace TagsWorkspace-level tagsOn contact export (if tags enabled)
Blinq Campaign TagsTags from campaigns the contact is part ofOn contact export from a campaign
Blinq CampaignsNames of campaigns the contact belongs toOn contact export from a campaign
Blinq CardDirect link to the contact’s Blinq cardOn every contact export
Blinq IDUnique Blinq identifier used for deduplicationOn connect (bootstrapped), on every export
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.

Contact fields

When you export contacts, Blinq applies the standard field mapping below.
Blinq fieldHubSpot field
First nameFirst name
Last nameLast name
Email (first/primary)Email
Phone numberPhone and/or Mobile
CompanyCompany name
Job titleJob title
WebsiteWebsite
AddressAddress
Blinq IDBlinq 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 pointHubSpot fieldValue
TimestampMeeting dateWhen the interaction occurred
TitleMeeting title”Interaction from Blinq”
BodyMeeting description”Interacted with {contact name}“
LocationLocationWhere the interaction took place
DurationStart / end timeInteraction time + 15 min default duration

Deduplication

Blinq prevents duplicate HubSpot Contact records using a two-step matching process:
  1. Blinq ID match: Blinq first searches HubSpot for a contact with a matching Blinq ID custom property.
  2. Email / phone fallback: If no Blinq ID match is found, Blinq falls back to matching by email address, then phone number.
If Blinq finds a match, it updates the existing HubSpot contact. If not, it creates a new one. If multiple HubSpot contacts share the same email address, HubSpot’s native duplicate resolution rules apply.

Need help?

For any questions or issues, contact Blinq support or email support@blinq.me.