Skip to main content

Overview

Field mapping is built into each native CRM integration and is configured from that integration’s settings page in your workspace. Field mapping is available on all native CRM integrations, including:
  • HubSpot
  • Salesforce
  • Dynamics

Using the field mapper

1

Open field mapping

Go to Settings → Integrations, then select Configure next to your CRM to open the field mapper.
2

Add a new mapping

Select Add mapping to create a new row.
3

Select the Blinq field

In the Blinq field column, choose the field you want to export. You can select any of the supported Blinq fields: a standard contact field or a custom form response.
4

Select the CRM field

In the CRM field column, choose the destination field in your CRM.
5

Save

Select Save to apply the mapping. New contacts sync using the updated configuration.

Field mapping requirements

First name, last name, and email are required fields in the field mapper. These can’t be removed or edited.
Text-based fields are the most widely supported custom field type. Other types are also supported, including dropdown menus and checkboxes from custom lead forms, and additional field types available on specific CRM platforms. Most field types, including checkboxes and dropdowns, can be mapped into a text field. You can’t always map a text field into a checkbox or dropdown.

Supported Blinq fields

Two groups of Blinq fields can be mapped to your CRM:
  • Standard contact fields: a fixed set of card and contact fields:
    • First name
    • Last name
    • Job title
    • Company name
    • Primary email
    • Secondary email
    • Phone
    • Mobile phone
    • Website
    • LinkedIn
  • Custom form responses: any custom field or question from a custom lead form, including text, dropdown, and checkbox responses.

Field mapping defaults

When a CRM integration is created, Blinq loads a default set of field mappings as a baseline. You can customize this configuration after setup using the field mapping menu.
The default mappings differ by CRM. Not every Blinq field is mapped by default on every integration, so review the loaded defaults after setup and add any mappings you need.

Removing a field mapping

To remove a mapping, select the delete icon on the row you want to remove, then save your changes. The required fields (first name, last name, and email) can’t be removed.

Need help?

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