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.
The Solution: Identifying Web Activities via Web Tag
Our solution allows 6sense Users to leverage their HubSpot MAP activity data in 6sense to attribute activities to Contacts.
How it Works: Associating Cookies to Contacts
We use the 6sense Web Tag to capture the user’s 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 Web Tag installed.
6sense Web Tag 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 Web Tag settings. Can be performed by an Admin User.
Navigate to the Web Tag settings and enable the toggle titled Capture Cookies by MAP.
Outcome:
Cookie toggle flipped.
Click Next to finish Web Tag deployment process.
Wait up to 4 hours for website cache to clear.
Web Tag begins to capture MAP cookies.
Onboard “Web Activities” object and run standard permission check. Can be performed by an Admin User.
Navigate to HubSpot MAP Integration settings and onboard the new Web Activities object.
Outcome:
HubSpot MAP new object onboarded.
Cookies captured from Web Tag filtering into new object.
For existing users: Onboard new object automatically.
For new users: Onboard as part of regular onboarding.
Wait for 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 deanonymized.
Outcome: New activities performed by contacts known in HubSpot MAP will be properly deanonymized in 6sense.
FAQ
Q: Which customers are eligible for this?
A: Customers with HubSpot MAP and Advanced Packages (ABM Advanced, SI Enterprise, SI Enterprise Lite) and have Web Tag 2.0 installed.
Q: Does this solution apply to MAPs outside of HubSpot MAP?
A: No, as other MAPs support this functionality natively.
Q: Does this change any legal requirements?
A: The data is already stored in HubSpot MAP, so 6sense is not changing the way in which it legally processes data.
Q: Where does this change surface?
A:
Contacts & Leads
Sales Intelligence
CRM & MAP Engagement Charts
segment Performance Reports
MAP: Scoring of Leads & Contacts
Q: Do competitors have a similar solution?
A: No.
Q: Are there any pricing or packaging changes?
A: No.
Q: Are there any places the activities will not be de-anonymized?
A: Activities will still be anonymous in Legacy Sales Intelligence.
Q: What happens if a customer rejects cookies?
A: The solution is predicated on HubSpot MAP cookies on a user’s browser.
Q: Is the HubSpot cookie considered 1st, or 3rd party cookie?
A: Since it is placed by a system owned by the customer, it is a 1st party cookie.
Q: Will previous activities be deanonymized?
A: No, deanonymization collection starts when the Web Tag toggle is flipped.