Create Leads in HubSpot

Pre-requisites: To Create new leads in HubSpot, you would need to have ‘Write’ permissions to the Integrations resource set.

You can create leads in HubSpot by mapping your HubSpot Lead object with Insent through Field Mapping in Insent. Field mapping allows you to define and map fields to the Insent Lead object and keep your HubSpot instance updated with the freshest and most contextual lead information. 

This article will discuss how you can create Leads in HubSpot whenever a new lead is created in Insent through Field mapping. This is the second article in a four-part series to get started with HubSpot.

  1. Integrate Insent with HubSpot
  2. Create Leads in Hubspot
  3. Target Visitors based on Hubspot Lists
  4. Push Insent Chat Log to HubSpot as an Activity

Field Mapping

Go to Settings → Integrations and locate the Field Mapping tab.

The Field Mapping tab allows you to map all your fields from HubSpot to the Insent Lead object.

You can view the list of existing mapped fields in the Field Mapping tab.

Insent will automatically map all the available default Insent fields with HubSpot Fields as soon as the HubSpot integration is successfully setup. To learn more about the list of default Insent fields available please refer to the appendix section of the Field mapping article.

Add source fields to be mapped to the Insent field object from the ‘Add Field’ button. 

After clicking the ‘Add field’ button, a pop-up screen will open up. You can map fields from HubSpot to the Insent field object on this screen. We view a list of all HubSpot source fields that can be mapped to Insent.

You can choose a default Insent field from the Insent field name dropdown or create a custom field from the same dropdown to map your HubSpot fields.  

Choose the source fields from HubSpot and list them in the order of priority. You can map one or more fields to an Insent field. 

Click 'Save' to complete mapping fields. You should see a notification that your field mapping is successful. 

The fields are mapped in the order of priority in the field mapping pop-up. The number listed next to each field under the ‘Source field name’ indicates the order of priority, the number  1 indicates 1st priority, 2 indicates 2nd priority, etc.

The order of priority influences which field is prioritized by Insent for targeting and personalization. More on priority rules later in the article.

Note: You can map a HubSpot source field to only one Insent field at a time. 

Note: In case you currently use other MAPs like Pardot or Marketo or CRMs like Salesforce, you can map fields from different MAPs or CRMs to the same Insent field and define priority rules that dictate which source fields are prioritized. 

What is the 'Overwrite' option next to each field?

Turning on the ‘Overwrite’ option enables you to write data collected in Insent to your HubSpot fields.Choose whether you would like to write data to HubSpot or other sources by turning on the ‘Overwrite’ option for each source field. This would allow you to enrich your MAP/CRM platforms with the latest data you capture in Insent. 


'Overwrite' option should always be turned on for the HubSpot Email Source field. If 'Overwrite' is not enabled, then no other mapped HubSpot fields will be written back, and lead creation will not be successful.

New Leads created in HubSpot through Insent are created with the following Original Source attribution:

  • Original Source: Offline sources 
  • Original source drill-down 1: INTEGRATION
  • Original source drill-down 2: Insent Integration APP

Required field mapping for lead creation in HubSpot 

You should map the Hubspot Email (Lead) field to the Insent Email field and enable the ‘Overwrite’ option for the HubSpot Email (Lead) field to be able to create new leads in HubSpot. 

Priority Rules - Field Mapping

Insent allows you to define the order of priority that governs how data is read from HubSpot and other sources. The data available in the first priority field will be considered by default for targeting and personalization through the mapped Insent field.

If the source field in the first priority is empty, then the source field value in the second priority will be read by the Insent field object and used for targeting. Similarly, if the first and second priority fields are empty, the third priority field is read and used for targeting.

Priority rules in Insent help ensure that your highest quality data is used for visitor segmentation in the Audience tab, where you can use accurate information for targeting visitors.

Mapping multiple fields and arranging them in the order of priority will ensure that the right data is used for personalization through Greeting messages or Condition-based rules in the Conversations builder.

Note: You can currently map a MAP or CRM source field to only one Insent field.

You can identify an existing source field in the Field Mapping tab through the filter option.

How Insent Reads the Hubspot Cookie

Loom VIdeo

Each time somebody visits your website, Insent will look up their cookie data to identify them based on different tools you use, such as HubSpot, Marketo, or Pardot.

When an anonymous visitor lands on your website, they are tracked anonymously by HubSpot even before they become a lead. When the visitor submits a form through Insent, a lead is created automatically in HubSpot, and the Insent cookie for the lead is written back to HubSpot.

Cookies are mapped to ensure HubSpot retains the Orginal Source and Traffic Activity for a particular lead. This will help your organization ensure that all leads coming in through Insent retain all of their attribution data.

To learn more about how Insent resolves the Cookie data, please refer to the article on Cookie resolution in Insent.

After Field Mapping: What Happens?

Identity Resolution based on HubSpot Cookie

  • The identity of a visitor is resolved based on the HubSpot Cookie.
  • Visitor data is automatically populated to the mapped Insent fields based on the Lead information in HubSpot.

Identity Resolution based on Email submitted in Insent

  • When a visitor manually submits an email through Insent, their identity is resolved from HubSpot.
  • Information about the identified visitors is read from the integrated platforms, and the data is read based on priority rules set up in the field mapping.

Reading data from HubSpot

  • HubSpot fields are read in the order of priority that they are mapped to an Insent field.
  • HubSpot fields will be read even if 'Overwrite' is disabled for a specific source field.

Writing data to HubSpot

  • Mapped Insent fields are updated immediately as soon as new data is captured by the bot or through a visitor profile update by an agent.
  • Mapped Dynamic Insent fields are updated in the HubSpot in 60-second intervals.

List availability in Audience

  • Static and Smart Lists are available immediately in the Audience rules list after the integration process is complete.
  • HubSpot Lists can be used for audience targeting in Insent.

Quick Recap

  • Field mapping in Insent helps you map source fields from HubSpot to the Insent Lead object.
  • Map multiple source fields to an Insent field and set up priority rules to dictate which field should be prioritized by Insent for targeting and personalization.
  • You can map HubSpot fields to only one Insent field at a time. 
  • Choose to write your source field data in HubSpot based on your visitor touchpoints with Insent. You will need to turn on ‘Overwrite’ if you want to write data to HubSpot.
  • Insent HubSpot Cookie mapping ensures that HubSpot retains attribution data such as Traffic activity and Original Source.

Please feel free to connect with our Customer Success team for any further questions on or Chat with us!

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us