Known Web Activity in HubSpot MAP is not available in 6sense. Instead, the activity is marked as “anonymous,” rather than attributed to the known user. This page describes the 6sense solution to leveraging Known Web Activity.
Identify web activities using WebTag
6sense users can leverage their HubSpot MAP activity data in 6sense to attribute activities to Contacts.
Prerequisites
HubSpot MAP integrated
6sense products, either Revenue Marketing with the Predictive add-on, SI Enterprise, or SI Enterprise Lite
Associate cookies to contacts
Use the 6sense WebTag to capture your HubSpot cookie, then match the cookie ID to a HubSpot Person. This associates the activity to a person.
Setup
Contact is identified in HubSpot via Form Fill.
HubSpot places a cookie on the user’s browser.
ID capture
Contact navigates to a page with the 6sense WebTag installed.
6sense WebTag collects cookie ID.
6sense sends cookie ID to HubSpot MAP.
HubSpot returns a HubSpot Person ID (HubSpot Person = SFDC Contact).
Surface activity data
6sense associates the web activity with the HubSpot Person ID.
6sense surfaces contact’s web activity as normal.
Example: de-anonymized activities on the timeline
Onboarding Process for Users
Enable “Capture Cookies by MAP” toggle in WebTag settings. Can be performed by an Admin user.
Go to the WebTag settings and enable the Capture Cookies by MAP toggle.
Outcome:
Cookie toggle flipped.
Click Next to finish WebTag deployment process.
Wait up to 4 hours for website cache to clear.
WebTag begins to capture MAP cookies.
Onboard “Web Activities” object and run standard permission check. Can be performed by an Admin user.
Go to HubSpot MAP Integration settings and onboard the new Web Activities object.
Outcome:
HubSpot MAP new object onboarded.
Cookies captured from WebTag filtering into new object.
For existing users: Onboard new object automatically.
For new users: Onboard as part of regular onboarding.
Wait for the 6sense pipeline to run.
Once the pipeline has run once, the new data for HubSpot MAP Activities will be visible across 6sense activation.
Note: Only new activities will be de-anonymized.
Outcome: New activities performed by contacts known in HubSpot MAP will be properly de-anonymized in 6sense.
FAQ
Does this solution apply to MAPs outside of HubSpot MAP?
No, as other MAPs support this functionality natively.
Does this change any legal requirements?
The data is already stored in HubSpot MAP, so 6sense is not changing the way in which it legally processes data.
Where does this change surface?
Contacts and Leads
Sales Intelligence
CRM and MAP Engagement Charts
Segment Performance Reports
MAP: Scoring of Leads & Contacts
Do competitors have a similar solution?
No.
Are there any pricing or packaging changes?
No.
Are there any places the activities will not be de-anonymized?
Activities will still be anonymous in Legacy Sales Intelligence.
What happens if a customer rejects cookies?
The solution is predicated on HubSpot MAP cookies on a user’s browser.
Is the HubSpot cookie considered 1st, or 3rd party cookie?
Since it is placed by a system owned by the customer, it is a 1st party cookie.
Will previous activities be de-anonymized?
No, de-anonymization collection starts when the WebTag toggle is flipped.