This document contains the instructions about setting up integration of N.RICH with Hubspot. Please consult your N.RICH Representative in case of questions or information requirements
1. Provide N.RICH with the following integration keys
[Estimated time: 2 min]
...
1
...
HubSpot Hub id
...
2
...
HubSpot API Key
...
How to test
...
N.RICH system will verify whether the keys work as expected.
...
Purpose
...
Enabling the use of Hubspot API for N.RICH system. N.RICH uses only the necessary data related to targeting and enabling its system functionalities. N.RICH does not store any personally identifiable information (PII). For more information, please review: http://n.rich/privacy-notice
2. Add the custom field, N.RICH Engagement Score under the contact on Hubspot
[Estimated time: 2 min]
...
Instructions
...
The type of the field must be Integer
...
Custom field name
...
N.RICH Engagement Score
...
How to test
...
Once set-up N.RICH system will automatically verify whether the field has been properly created.
...
Purpose
...
Engagement scoring logic defined in within N.RICH's system will be stored on this field
3. Add the separately delivered N.RICH Smart Engagement Tag to Hubspot landing page templates
[Estimated time: 2 min / template]
...
Instructions
...
Tag should be placed just above the closing </body> tag
...
How to test
...
Send N.RICH a link to a Hubspot landing page template based on which N.RICH representative can verify the tag.
...
Purpose
...
Website tag is used for two purposes 1) being able to remarket to the visitors of the landing page and 2) being able to sync N.RICH cookies with Hubspot cookies. This sync is mandatory for lead scoring integration.
4. Add N.RICH Smart Engagement Email Tag to Hubspot email templates
[Estimated time: 2 min / template]
...
Instructions
...
The tag is a transparent pixel that won’t be visible for the recipient. The tag should be placed into the footer of the email body
...
N.RICH Smart Engagement Email Tag for Hubspot
...
<img src="https://nrich.io/analytics?address={{contact.email}}" />
...
How to test
...
Send your N.RICH representative an email directly from Hubspot in order for N.RICH to verify the tag.
...
Purpose
...
Email tag is used for generating the necessary data for identifying the company of the prospect when they interact with N.RICH widgets.
5. Define the engagement scoring model for N.RICH system
[Estimated time: 30 min]
...
Instructions
...
Score needs to be defined for the following events:
- Engagement (Start of scrolling)
- Reading (Scrolling 50% and spending 10s or more time with content)
- Completing (Scrolling 100% and spending 10s or more time with content)
- CTA click (Clicking a CTA)
The score is cumulative ([1]+[2]+[3]+[4]) and it is first recommended to define the total score for all sequential interactions (e.g. 20) and then defining the individual scores. A common approach is to score the sum of all aforementioned events equivalently to filling a form. Typical scoring weights include: 1 - 1 - 1 - 1 and 1 - 1 - 2 - 2 (Engagement - Reading - Completing - CTA click)
...
How to test
...
Once engagement has been tracked, the functionality can be verified by checking prospects with greater than zero value for N.RICH Engagement Score. Due to the time required for the cookie syncing process, it may take up to a month from the start of the program to get first prospects with actual score.
...
Purpose
...
Enables integrating N.RICH engagement into the lead scoring / qualification processes.
6. Integrate N.RICH Engagement Score into the lead scoring automation rules
[Estimated time: min]
...
Instructions
...
As the final it is recommended to integrate N.RICH Engagement Score into the automation processes related to lead qualification so that total lead score = General Lead Score + N.RICH Engagement Score.
...
Purpose
...
Purpose
N.Rich Hubsopt CRM / MAP 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 MAP: 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 MAP: 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 MAP
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.
Hubspot MAP
If you only use Hubspot for marketing automation and not as CRM, you need to go to the Marketing Automation tab of N.Rich setup and add the Hubspot portal ID and API key.