If you use the HubSpot Integration, you most likely have properties there that you'd like to attach in Drift that are not there by default. These properties are important for your sales or marketing teams so you can create workflows in both Drift and HubSpot and to make sure that you're keeping all of the data on your prospects constant throughout your tech stack.

In this doc, we'll cover

• how to map Drift Attributes to HubSpot properties manually in your integrations settings
• how to use attributes for targeted reporting
• FAQ

The HubSpot Integration is available on our Premium Plans and above.

Mapping Drift and Custom Attributes to HubSpot Attributes

You can easily map existing Drift attributes or custom attributes you've created to HubSpot attributes! To do so, head to Settings > App Settings > Integrations >  Hubspot, or just click here! 

From there, find the Mapped Hubspot Attributes section. 
Here, you can select the Drift value that you'd like to map to a HubSpot value! 

To map a Numeric value in Drift (like CQL score), use the Calculated field in HubSpot!

You can also write in your own Static attribute as well - this be the value that passes over for every record. 

A common use case would be mapping the text "Drift" to the HubSpot "Lead Source"

Careful you're not mapping to a "Read Only" field in HubSpot or that HubSpot doesn't require a specific format.
(ex. Country = United States trying to map to a Country field that only accepts US)

Note!

If you are mapping to a Hubspot picklist, the value you send from Drift must exactly match the internal value of the field in Hubspot, not the label value.

 

Use Attributes for Targeted Reporting in HubSpot

Organizations may want to see which playbooks are creating the most leads in HubSpot. Below is a tip on how you can manage this with attribute mapping!

Let's use these playbooks as an example:

 

When editing each playbook, head over to the Goals section and find the Bot Qualified goal.

Here, you can create a new goal for when a lead is qualified by each individual playbook.

For this example, we would add Home, Pricing, Products, and Support Qualified goals, instead of Bot Qualified goals for all four.

Then, you can go to the Integrations section under Settings and map the Lead Stage to HubSpot!

This will cause Leads added to HubSpot to have a tag relevant to the playbook they engaged with.

FAQ

Q: How does the HubSpot drilldown field work with Drift? How is it populated?"
A: Updating this field is done on the HubSpot end (https://knowledge.hubspot.com/contacts/understand-source-properties) The drill-down properties are automatically set by HubSpot and cannot be updated manually. If you change a contact’s original source, the drill-down properties will be cleared.

Q: My custom datepicker field is not appearing, why?
A: Date properties (including date picker properties created in HubSpot) can only store the date—not the time. Drift requires a DateTime property. The only way to create a datetime property in HubSpot is by using the APIs, as any date picker property created in HubSpot is created as a date property.  For further details we suggest checking out this developer doc over at Hubspot.