Summary
IP filtering is essential for keeping marketing analytics clean, but it currently prevents HubSpot Surveys from capturing any responses submitted from internal users. This creates a gap for teams that rely on surveys for internal processes (e.g. RFP retrospectives).
Problem
When IP filtering is enabled, any survey submission from an excluded IP address is completely omitted from survey analytics and reporting.
This means:
- Internal stakeholders cannot submit trackable survey responses
- Test submissions do not appear in reporting
- Survey dashboards are incomplete or unusable for internal workflows
In practice, this forces teams to:
- Temporarily disable IP filtering (risking inaccurate marketing data)
- Use external tools instead of HubSpot Surveys
Proposed Solution
Introduce a way to override IP filtering specifically for surveys, such as:
- A survey-level setting:
“Include responses from excluded IP addresses” - OR an option to flag submissions as:
- Internal (included in survey reporting, excluded from marketing analytics)
- External (standard behaviour)
- OR more granular controls to define which tools (e.g. forms vs surveys) respect IP filtering
Value
This would:
- Enable internal use cases without compromising marketing data integrity
- Reduce reliance on workarounds (external tools)
- Increase adoption of HubSpot Surveys across sales, marketing, and operations teams
- Keep more data inside HubSpot rather than fragmented across platforms
Closing Thought
IP filtering and survey functionality shouldn’t conflict—both serve important but different purposes. Providing a controlled way to include internal survey responses would significantly improve usability for cross-functional teams.