# Exclude specific contacts (e.g. employees) from registering data/usage?

**URL:** <https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386>\
**Category:** Lists, Lead Scoring & Workflows\
**Created:** [June 14, 2017, 6:43pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386 "2017-06-14T18:43:52Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robb](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/robb/32/24930_2.png) [@Robb](https://community.hubspot.com/u/Robb)\
**Post date:** [June 14, 2017, 6:43pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/1 "2017-06-14T18:43:52Z")

</div>

I think there is a way to indicate contacts who you don’t want to count as page views, get notified when on site, in metrics, etc. For example, someone in our own company.

Where can I find that setting?

Thank you for your help!

---

<div class="post-metadata">

**Author:** ![tms0003](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tms0003/32/37588_2.png) [@tms0003](https://community.hubspot.com/u/tms0003)\
**Post date:** [June 15, 2017, 5:53pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/2 "2017-06-15T17:53:08Z")

</div>

Hi Robb,

You’re right that there’s a way to do this -- and luckily it’s pretty easy to do.

- In the Marketing side of the software, just go up to the “Reports” tab and click on “Reports Settings.”
- Then, scroll down to the “Exclude traffic from these IP addresses” section.
- Enter in all IP addresses from which you want to exclude traffic. This should include the IP address for your company, the IP addresses of any vendors who might be visiting your site, etc.
  - If you don’t know your IP address, you can ask your IT team or go to [ipchicken.com](http://ipchicken.com)
  - In the case of vendors, etc., you would most likely need to just ask them for their address. If you want to be a bit stealthy about it, you could also potentially find this by looking at form submission details.

- Click “Save” to save the IP address

HubSpot will then filter out traffic from that IP address moving forward. Unfortunately, I don’t believe there’s a way to have HubSpot retroactively filter out IP addresses.

---

<div class="post-metadata">

**Author:** ![Robb](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/robb/32/24930_2.png) [@Robb](https://community.hubspot.com/u/Robb)\
**Post date:** [June 15, 2017, 6:11pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/3 "2017-06-15T18:11:49Z")

</div>

Perfect. Thank you!

---

<div class="post-metadata">

**Author:** ![GarthMJ](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/garthmj/32/63860_2.png) [@GarthMJ](https://community.hubspot.com/u/GarthMJ)\
**Post date:** [June 16, 2017, 10:09pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/4 "2017-06-16T22:09:22Z")

</div>

I’m looking for the exact thing too.

Two things:

1. There is no report tab for those on the starter package
2. Secondly, it would be really nice to be able to flag a user as don’t track via thier profile. Particularly in the Returning Contact dashboard report.

---

<div class="post-metadata">

**Author:** ![edjusten](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/edjusten/32/14475_2.png) [@edjusten](https://community.hubspot.com/u/edjusten)\
**Post date:** [June 17, 2017, 9:18pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/5 "2017-06-17T21:18:25Z")

</div>

Hi @GarthMJ IP filtering is not available for Marketing Starter or Marketing Free. You’ll have to search your web platform to see if they can filter IPs.

Ed

---

<div class="post-metadata">

**Author:** ![GarthMJ](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/garthmj/32/63860_2.png) [@GarthMJ](https://community.hubspot.com/u/GarthMJ)\
**Post date:** [June 18, 2017, 6:10pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/6 "2017-06-18T18:10:18Z")

</div>

Don’t get me wrong @edjusten , I hear exactly what you are saying and I completely understand the point about start/free.

IMO IP filtering is a bad idea, particularly when many companies have road warriors or PPOE (DHCP) for their network connections. This would mean that you are continually updating the list of IP address to filter by.

However, IMO it would be a simply filter out employees from the list. For that matter you (Hubspot {HS}) is already kind a doing it now. Thing about it.

When someone connects to a website( [www.enhansoft.com](http://www.enhansoft.com)) you review the HS ID and tag it for enhansoft. You are also looking at the website cookie and seeing the User ID listed within the cookie, which you are assigning all web pages that the users look at to that user id. Since you are doing the latter, it would make sense that when you look up the HS user details that you ask for an Employee flag, If the flag existing, don’t recording the details of that page view. Which in turn means that the usage data will not show any userid which has been flagged as an employee.

For that matter, any user which has company’s domain name, “[Enhansoft.com](http://Enhansoft.com)” in my case, can automatically be flagged as an employee when the user is added to the HS CRM system.

Just to close this off, there is an IMO simple fix to this. Which I have described above.

---

<div class="post-metadata">

**Author:** ![edjusten](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/edjusten/32/14475_2.png) [@edjusten](https://community.hubspot.com/u/edjusten)\
**Post date:** [June 19, 2017, 2:16am UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/7 "2017-06-19T02:16:46Z")

</div>

All valid points. It’s beyond my technical knowledge to know if this is possible; this might be a good thread for the [Ideas Forum](https://community.hubspot.com/t5/HubSpot-Ideas/idb-p/HubSpot_Ideas) or our developers forum at [integrate.hubspot.com](https://integrate.hubspot.com)

Ed

---

<div class="post-metadata">

**Author:** ![GarthMJ](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/garthmj/32/63860_2.png) [@GarthMJ](https://community.hubspot.com/u/GarthMJ)\
**Post date:** [June 19, 2017, 2:38pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/8 "2017-06-19T14:38:27Z")

</div>

Feel free to move this post there, or this section of the thread here.

---

<div class="post-metadata">

**Author:** ![jgentes](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jgentes/32/29368_2.png) [@jgentes](https://community.hubspot.com/u/jgentes)\
**Post date:** [February 28, 2018, 8:05pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/9 "2018-02-28T20:05:23Z")

</div>

Related: Is there a different way to avoid form captures from these contacts or IP addresses? I’ve got our corporate IP listed as excluded, but we still receive form submission notifications.

---

<div class="post-metadata">

**Author:** ![edjusten](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/edjusten/32/14475_2.png) [@edjusten](https://community.hubspot.com/u/edjusten)\
**Post date:** [February 28, 2018, 10:37pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/10 "2018-02-28T22:37:04Z")

</div>

Hi. @jgentes Filtering only applies to the form submission total, you will still see submissions and receeive notifications. [Find out more here.](https://knowledge.hubspot.com/articles/kcs_article/reports/does-filtering-ip-addresses-include-test-form-submissions)

Thank you,

Ed Justen

---

<div class="post-metadata">

**Author:** ![jgentes](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jgentes/32/29368_2.png) [@jgentes](https://community.hubspot.com/u/jgentes)\
**Post date:** [March 1, 2018, 12:10am UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/11 "2018-03-01T00:10:47Z")

</div>

Thanks Ed, I appreciate the quick response!

Is there a way to use javascript to disable an individual form programmatically? I have the script injected into every page, but don’t want to track every form submission.

---

<div class="post-metadata">

**Author:** ![edjusten](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/edjusten/32/14475_2.png) [@edjusten](https://community.hubspot.com/u/edjusten)\
**Post date:** [March 2, 2018, 3:17pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/12 "2018-03-02T15:17:37Z")

</div>

Hi @jgentes There is not a way to do that as far as I know. I’ve certainly yet to hear of this as a use case scenario. Can you expand a bit on why you would want that to happen?

Thank you,

Ed Justen

---

<div class="post-metadata">

**Author:** ![jgentes](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jgentes/32/29368_2.png) [@jgentes](https://community.hubspot.com/u/jgentes)\
**Post date:** [March 2, 2018, 4:00pm UTC](https://community.hubspot.com/t/exclude-specific-contacts-e-g-employees-from-registering-data-usage/2386/13 "2018-03-02T16:00:23Z")

</div>

Sure, the competitive solutions to messaging are things like Drift and Intercom, which Hubspot can do as well by simply activating the messaging window within an application (rather than just on the external website).

It also makes sense to do this since the event tracking features require the code to be running in your app, and the only way to monitor retention metrics is through their activity within your app.

So leveraging the messaging feature that’s already essentially running in the app seems like a reasonable thing to do as a support feature for customers. The trick is that you really want to ‘show’ the chat feature when someone clicks a help icon, rather than having it always visible, although that’s also an option (which we’re doing now).
