Turn Off Excluding IP Addresses from Form Submissions

[JMendez3]

When it comes to Forms and receiving submissions, there should be an option to turn off excluding submissions based on IP addresses. Form submissions are different from traffic. 

Or at the very least, there needs to be an option to export excluded submissions when exporting the full submissions list. Even if they're separated by tabs. 

Use Case Example: We created an RSVP form for an upcoming event that includes clients and employees. A few employees filled out the form when they were in the office, which meant their IP address was one of the ones included in our excluded list (since we're trying to filter out internal traffic from external). But in this case, we need to see their RSVPs with the full list. They shouldn't be excluded. Now we're having to manually add them in, which won't be sustainable with a much larger list size in the future. 

[JMendez3]

Hi everyone,

Thanks for taking the time to submit and vote on this idea.

I’m Jenny, the Product Manager for Forms & CTAs.

We recently released a setting that gives more control over how excluded IP submissions are handled (based on this feature request), but I recognize that it doesn’t fully solve the use case described here - especially around ensuring these submissions appear in your reporting and exports.

This is an area we see opportunities to improve, and we’ll be considering this request as we review upcoming roadmap work.
I’ll share an update once we have clearer direction.

Thanks again for the feedback - I’ll keep this thread updated.

Thanks,
Jenny Mueller

[auto-mate]

Argh - just bumped into this - unexpected. 
Is this a new "feature" - I don't remember seeing this before.

At least this is really annoying. We have the same as the OP with a lot of internal tools connected to Hubspot.
Traffic suppression should be seperated from form submission!!!

[auto-mate]

Found a workaround for this.

To enable IP-supressed form submitters to enrol in workflows:
If you add a starting enrollment criterion - even "Recent conversion" is known - and combine it with Form submission = XYZ - then IP-supressed form submitters will join the workflow.
This is a bit odd - but it works!

Better would be to enable us to choose in settings if IP supression applies only to to traffic reports - or also to forms!

[JMendez3]

@auto-mate nice! Can you clarify where you're doing this enrollment criterion in Hubspot? Is it in Lists? 

[auto-mate]

@JMendez3 Have not tried in a dynamic list - only in Workflow enrolment criteria.

 

[lynmartin]

This is a strange quark! I understand the importance of filtering them out, but we need the option to bypass it and download all the submissions. The website traffic filtering needs to be separate from the form submissions. Please find a fix for this! 

[TopKat]

Yes please. At least give us the option of whether we want to filter internal submissions out or not. Exclusing them by default is not veyr user-friendly.

[JMuba89]

We need this option

[kcostello]

Bump! This has been very annoying when trying to do internal tesing. Don't remember this being a problem before....

[Amarck]

This must be something new. We havent had this problem before. Please do something about this. 

[Maelle-RENNES]

"This must be something new. We havent had this problem before. Please do something about this." +1

[christa]

Agree with the recent comments that this feels like something new as we didn't have this problem with our internal form submissions until recent. I was surprised to see this in the forum from Jan. 2025

Either way, it is a HUGE disruption to our cross team and cross department processes at our ORG. It is completely unreasonable to believe we can manually release a spam form submission in a timely manner, especially in the use cases we have. 

[PThor]

This is very important to our team's use of Hubspot - please make it happen!

[PThor]

This is very important to my teams, please make it happen!

[auto-mate]

The basic problem here still causes us a lot of hassle. Submissions to internal forms are now quarantined almost at random in the spam submissions, depending on if someone is in the office, remote working, at an event, on mobile etc etc.

Please please please separate excluded traffic from form submissions!

In the meantime I am looking for workarounds to try to build alerts if there are internal form submissions - for our internal only forms I think the only way is to use hidden populated fields. Spam submissions can't be listed or found in any other tools to e.g. build alerts easily.

[Savouré]

We had never encountered this issue before, it’s causing significant internal problems. We really need this option.

[PatrickSJ]

This issue needs to be resolved. Our teams depend on forms for a number of critical internal processes, and this has caused significant disruption.

For instance, we use an internal employee form to update key properties for high-value customers. Only after a manual audit did we realize that recent updates were not being applied because those internal submissions were being excluded.

[auto-mate]

Bump this for the breakfast crowd! This is now causing me daily pain. 

[FFlodgaard]

Bump, this change this needs to be reverted or fixed ASAP.

[PThor]

Has someone from Husbpot replied to this thread?  This is calling into question a primary (and formerly reliable) aspect of our Hubspot usage.  Should we be shopping around or is there a fix planned for this (and WHEN)?  

[ManuelC]

Totally on your side with this. It makes our internal testing prodecure more complex... and I also never had this before in the past. It must have been added in the last few weeks.