Purpose
N.Rich HubSpot CRM / MAS integration is used for the following purposes:
HubSpot CRM: pulling deal (opportunity) data from HubSpot to N.Rich. This data is used for measuring opportunity attribution (opportunity analytics), creating segments based on opportunity data and for generating Ideal Customer Profiles (ICP)
HubSpot CRM: pushing ABM engagement data and Intent data to HubSpot company object. This data becomes available as account properties and can be used for example for account prioritisation, reporting, or sales outreach personalisation.
- HubSpot CRM: Showing N.Rich ABM engagement on company timeline. Timeline engagement is useful for tracking the overall journey of the account, although this data can't be used as a basis of creating lists or workflows.
- HubSpot MAS: Syncing HubSpot contact-level cookie id's with N.Rich cookie id's. HubSpot contacts have a cookie id if they have either submitted a HubSpot form or clicked a HubSpot marketing email (clicking Sales emails doesn't create a HubSpot cookie). Cookie sync is used to associate the ad and website engagement tracked on N.Rich to the contact on HubSpot.
- HubSpot MAS: Pulling form submissions and email engagement data to N.Rich intent reports. HubSpot engagement data is used as a component of N.Rich intent reports scoring model.
Setting up
HubSpot CRM and MAS
If you use HubSpot as both CRM and Marketing Automation Platform, you need to integrate HubSpot only from the CRM setup of N.Rich and there is no need to integrate from the Marketing Automation tab in this case. HubSpot integration can be done by simply clicking on INTEGRATE button on N.Rich setup (Setup / CRM /HubSpot CRM) and authenticating with a HubSpot API user.
Here are the steps that you need to ensure when creating the user:
For security reasons, instead of using shared credentials and a shared user, it is recommended to create a dedicated user for N.Rich
The HubSpot user must have read and write access to HubSpot API including Companies, Contacts, Deals objects as well as any objects used for identifying product-association of opportunities.
Account properties
Intent reports
...
Type
...
Field name
...
Field label
...
Description
...
Text
...
nrich_IntentReportName
...
Intent report name
...
Intent report name
...
Number
...
nrich_CompositeIntentScore
...
Composite intent score
...
Composite account intent score (weighted third party and first party intent data based on intent report settings)
...
Number
...
nrich_HighIntentContactsNum
...
High intent contacts
...
Number of contacts (cookies) with high intent score)
...
Number
...
nrich_HighIntentTopicsNum
...
High intent topics
...
Number of topics with > 60 as the intent score
...
Text
...
nrich_IntentLocation_1
...
Intent location 1
...
Top location for intent
...
Text
...
nrich_IntentLocation_2
...
Intent location 2
...
2nd location for intent
...
Text
...
nrich_IntentLocation_3
...
Intent location 3
...
3rd location for intent
...
Text
...
nrich_IntentTopic_1
...
Intent topic 1
...
Highest scoring intent topic (available only if third party intent data is used in report and available for the account)
...
Text
...
nrich_IntentTopic_2
...
Intent topic 2
...
Second highest scoring intent topic (available only if third party intent data is used in report and available for the account)
...
Text
...
nrich_IntentTopic_3
...
Intent topic 3
...
Third highest scoring intent topic (available only if third party intent data is used in report and available for the account)
N.Rich ABM and website engagement
...
Type
...
Field name
...
Field label
...
Description
...
Date
...
nrich_LastEngagementDate
...
Last ABM engagement date
...
Last date with one or more ABM Engagements: video views, article readers or clicks
...
Date
...
nrich_LastClickDate
...
Last ABM click date
...
Last N.Rich click (and visit) date. Clicks are recorded using N.Rich tag on the website, so every click also means a visit.
...
Date
...
nrich_LastWebsiteVisitDate
...
Last website visit date
...
Last website visit date (any website visit, not just ABM)
...
Number
...
nrich_EngagedContacts
...
Contacts with ABM engagement
...
Number of ABM engaged unique cookies from the account. Aggregated to the time frame user has selected
...
Number
...
nrich_ClickedContacts
...
Contacts with ABM clicks
...
Number of clicked unique cookies from the account. Aggregated to the time frame user has selected
...
Number
...
nrich_VisitedContacts
...
Contacts with website visits
...
Number of visited unique cookies from the account from any channel. Aggregated to the time frame user has selected
...
Number
...
nrich_TotalClicks
...
Total clicks
...
Total ABM clicks. Aggregated to the time frame user has selected.
...
Number
...
nrich_TotalVideoViews
...
Total video views
...
Total ABM video views. Aggregated to the time frame user has selected.
...
Number
...
nrich_TotalArticleReaders
...
Total article readers
...
Total ABM article readers. Aggregated to the time frame user has selected.
...
Number
...
nrich_TotalEngagements
...
Total ABM engagement
...
Total ABM engagements. Aggregated to the time frame user has selected.
...
Number
...
nrich_TotalWebsiteVisits
...
Total website visits
...
Total website visits from any source. Aggregated to the time frame user has selected.
Setting up the account properties
Account properties need to be set up manually on SFDC. From integration perspective it is essential that the each of the above mentioned field names are available as account properties. Also, it is recommended to group the fields as follows:
Hubspot MAS
...
| The article is now available here: | https://n.rich/en/knowledge-base/hubspot-integration |