# HubSpot CRM
SaaSMonk has a bi-directional Hubspot sync to make sure that Hubspot stays as your source of truth.
{% hint style="info" %}
Our approach to making sure that this integration is successful is iterative. We recommend you start with reads, and consult with our support team on enabling specific writes since the needs for these vary vastly from company to company.
{% endhint %}
## Reading data from HubSpot to SalesMonk
SalesMonk reads customer CRM data in order to populate additional fields within our platform with relevant CRM information. It also enables our customers to:
* Create segmenting based off of CRM data - needed in scenarios where you want your reps to be notified when an account that they own comes to your website
* Filter out your current customers in so that you're only messaging true prospects.
* See the data surfaced in all the relevant places - Slack, in the visitor and company detail pages, and so on.
We currently show the following CRM fields inside SalesMonk dashboards and Slack notifications:
* Company
* Name
* Website
* \# of contacts
* Owner
* Contact
* Name
* Email
* Lifecycle stage
* Owner
* Deal
* Amount
* Close date
* Deal pipeline
* Deal stage
* Last activity
* Owner
## Writing data from SalesMonk to HubSpot
When SalesMonk identifies a company or an individual visiting your website, we will add that company as a Company record in HubSpot and add that individual as a Contact record in HubSpot.
**Please note that writes need to be enabled in consultation with our Support team - we'll make sure that only the right fields and contacts/companies are getting mapped to HubSpot.**
In addition to adding a Company record and/or a Contact record to HubSpot, SalesMonk also writes over a set of custom SalesMonk fields. These essentially serve as a way to get all of SalesMonk's valuable website traffic data into your CRM automatically.
{% hint style="info" %}
We distinguish duplicate records by checking domains for companies and emails for individuals.
{% endhint %}
If we identify a duplicate, we will not create a new Company or Contact record, and instead write over the data from the custom fields to the Company and Contact records.
### Company
SalesMonk adds these fields to the Company object:
1. SalesMonk Created
1. True if this account didn’t exist in your CRM before and SalesMonk created this account
2. SalesMonk: Company
1. URL Link to the account page in SalesMonk, e.g.
3. SalesMonk: Last Seen
1. Date any visitor from this account was last seen on your website
4. SalesMonk: Pages Visited
1. List of URL page paths visitors from this account visited
5. SalesMonk: Segments
1. List of SalesMonk Segments that this account matches
6. SalesMonk: Total active time
1. Total active seconds spent on your website of all visitors from this account. Active means the visitor was moving their mouse, scrolling, clicking. Does not include time where the visitor just leaves the tab open in the background
7. SalesMonk: Total pages viewed
1. Total number of page views (non-unique) from all visitors from this account.
1. E.g. if visitor A views /pricing, clicks /home, clicks /pricing, that’s 3 pages viewed.
8. SalesMonk: Total sessions
1. Total number of sessions from all visitors from this account. A new session is started when a visitor comes to your site, and ends when the visitor closes the tab or if they become inactive and stop scrolling/moving/clicking anything on your site for over 30m.
1. E.g. visitor A goes to your site, scrolls around, closes tab. 4 hours later, visitor A goes to your site again and clicks around. That’s 2 sessions.
9. SalesMonk: UTM Campaigns
1. List of all utm\_campaign values from any visitors from this account
10. SalesMonk: UTM Contents
1. List of all utm\_content values from any visitors from this account
11. SalesMonk: UTM Mediums
1. List of all utm\_medium values from any visitors from this account
12. SalesMonk: UTM Sources
1. List of all utm\_source values from any visitors from this account
13. SalesMonk: Visitor count
1. Number of unique website visitors from this account
### Contact
SalesMonk adds these custom fields to the Contact object:
1. SalesMonk Created
1. True if this lead didn’t exist in your CRM before and SalesMonk created this lead
2. SalesMonk Contact
1. URL Link to the visitor page in SalesMonk, e.g. [https://app.saasmonk.ai/contact/details/XXXX](https://app.saasmonk.ai/account/XXXX)
3. SalesMonk Last Seen
1. Date this visitor was last seen on your website
4. SalesMonk Total sessions
1. Total number of sessions from all devices of this visitor. A new session is started when a visitor comes to your site, and ends when the visitor closes the tab or if they become inactive and stop scrolling/moving/clicking anything on your site for over 30m.
1. E.g. visitor goes to your site, scrolls around, closes tab. 4 hours later, visitor A goes to your site again and clicks around. That’s 2 sessions.
5. SalesMonk UTM Campaign
1. Last utm\_campaign value
6. SalesMonk UTM Content
1. Last utm\_content value
7. SalesMonk UTM Medium
1. Last utm\_medium value
8. SalesMonk UTM Source
1. Last utm\_source value
We also add in the following in the **Activity** **timeline** for the contact:
1. Chats initiated by the contact
2. Meetings booked by the contact
### Deal
SalesMonk adds these fields to the Deal object:
1. SalesMonk Created Account
1. True, if the Account associated with this Opportunity is "SalesMonk Created: True"
## HubSpot integration FAQs
**Question**: If a match isn't found in HubSpot, what records are created and what are the default values?(Owner, Status, etc.)
**Answer**:
Creating a Company:
* Company Name
* Company Owner
* Assigned to the HubSpot user who did the HubSpot integration in SalesMonk
* Website
* All the SalesMonk fields mentioned above
Creating a Contact
* Name
* Email
* Contact Owner
* Assigned to the HubSpot user who did the HubSpot integration in SalesMonk
* All the SalesMonk fields mentioned above
***
**Question:** What's the methodology SalesMonk uses to identify whether a Contact/Company already exists in HubSpot?
**Answer:** We look at the unique identifiers for companies and individuals. These are the domains of the companies and the emails of the people. Note that for companies we match based on just domain of the website field (we strip any “[http://www.”](http://www.xn--ivg/) and any URL paths)
***
**Question:** Will SalesMonk edit any of our CRM fields?
**Answer:** No. We only write to the customer SalesMonk fields.
***
**Question:** If SalesMonk identifies the account or the contact to be a duplicate, will it still write over the SalesMonk data to the custom fields of the Company record and/or the Contact record?
**Answer:** Yes. If we identify the company or the individual that has visited your website to already be in your HubSpot, we will not create a new Company record or Contact record. However, we will still write over all of the data into the SalesMonk custom fields for those existing Company records and/or Contact records.
***
**Question:** At a high level, how can I easily find whether a Company or Contact record was created by SalesMonk?
**Answer:** You’ll see "SalesMonk Created” is “True” if we created the Company or Contact record.
***
**Question:** Is there an option to create customer field mappings for records created by SalesMonk?
**Answer:** This requires a custom integration - please contact our support, we'd be happy to make this happen for you!
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.salesmonk.ai/integrations/hubspot-crm.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.