HubSpot Non-HubSpot Forms Guide

When you use HubSpot on your website, you can automatically capture submissions from many existing forms without rebuilding them. This guide explains how non-HubSpot forms work, which forms are supported, and how to troubleshoot common tracking issues so you can confidently manage lead capture across your entire site.

What Are Non-HubSpot Forms?

Non-HubSpot forms are web forms created outside of the HubSpot forms tool, for example with your CMS, a plugin, or custom code. When you enable non-HubSpot form collection, the HubSpot tracking code detects supported forms on your pages and sends submissions into your CRM as contacts.

You can then view, segment, and report on these contacts alongside submissions from native HubSpot forms.

How HubSpot Detects Non-HubSpot Forms

The HubSpot tracking code scans each page that it loads on your website. It looks for HTML form elements that match supported patterns and then listens for successful submission events.

When a visitor submits a supported form, the tracking script packages the field values and sends them to your HubSpot account as a form submission.

Requirements for Detection

• The HubSpot tracking code must be installed correctly on the page.
• The form must be present in the HTML when the page loads or after a supported script renders it.
• The form needs at least one email-type field so HubSpot can create or update a contact.

If these conditions are met and the form vendor is supported, submissions should appear in your CRM automatically.

Supported Non-HubSpot Form Types

HubSpot can track many common embedded forms, especially those that output standard HTML. While the list of fully supported providers can change, most basic forms that render as regular HTML are eligible.

Commonly Compatible Scenarios

• Native CMS contact forms that produce simple HTML.
• Custom-built forms using standard form tags.
• Forms that submit using a traditional page reload, or AJAX forms that trigger a normal submission event.

Some complex or highly customized setups may not be compatible; in those cases, consider recreating the form as a native HubSpot form or using an alternate integration method.

Limitations of Non-HubSpot Forms in HubSpot

Even when detection works, non-HubSpot forms do not offer the full feature set of native forms. Understanding these limitations will help you decide when to switch to HubSpot forms instead.

Feature Gaps to Consider

• No drag-and-drop editing from within HubSpot.
• Limited styling control from the CRM interface.
• Some advanced options, such as progressive fields, may not be available.
• Submission analytics can be less detailed than for native forms.

Because of these constraints, HubSpot recommends using native forms for mission-critical lead capture whenever possible, while relying on non-HubSpot form collection mainly to cover existing forms during a transition period.

How Submissions Are Stored in HubSpot

Every successful non-HubSpot form submission is logged in your CRM as a form submission event. Contacts created or updated by these forms behave similarly to those created by standard HubSpot forms.

Field Mapping Behavior

• HubSpot attempts to match each form field to an existing contact property by name.
• If there is no clear match, the value may not map automatically and might require a custom property and mapping change in the future.
• Email fields are used as the primary identifier to create or update contacts.

Because of this, consistent naming between your website forms and your HubSpot properties helps reduce data-cleanup work.

Enabling Non-HubSpot Form Collection

Before HubSpot can track these forms, you must enable the non-HubSpot forms feature in your account settings and ensure your tracking code is live.

Step-by-Step Setup

1. Install the HubSpot tracking code on every page where you have external forms.
2. In your account settings, turn on non-HubSpot form collection.
3. Save your changes and republish any cached pages if necessary.
4. Submit a live test through one of your website forms to verify that the submission appears in your CRM.

After configuring this, HubSpot will continue to monitor your pages and automatically collect new submissions from compatible forms.

Troubleshooting Non-HubSpot Form Issues

If you do not see submissions inside HubSpot, or data is missing from contact records, use the following checks to identify the cause.

1. Verify the Tracking Code

• Confirm the HubSpot tracking code is added once per page, just before the closing body tag.
• Make sure you are viewing the correct domain and environment where the code is installed.
• Use your browser console or developer tools to check for JavaScript errors that might block the script.

2. Inspect the Form Markup

• Ensure the form uses standard HTML form elements.
• Confirm the email field is present and correctly labeled as an email field.
• Avoid custom submission methods that bypass the normal form submit event.

3. Test a Fresh Submission

1. Open the page in a private or incognito window.
2. Fill in the form with a new email address.
3. Submit and wait a few minutes.
4. Search for the email address in your HubSpot contacts.

If the contact does not appear, compare your form implementation with the guidance in the official documentation and adjust accordingly.

Best Practices for Using HubSpot with External Forms

To get consistent, reliable data from non-HubSpot forms, plan your implementation around a few simple best practices.

Standardize Field Names

• Align field labels and internal names with your existing contact properties in HubSpot.
• Document which website fields map to which properties.
• Use the same naming patterns across all your external forms.

Minimize Form Variants

• Limit the number of slightly different forms that capture the same information.
• Where possible, switch high-value pages to native HubSpot forms for deeper analytics.
• Use existing templates and consistent structure to simplify troubleshooting.

When to Replace Non-HubSpot Forms with Native HubSpot Forms

Non-HubSpot form tracking is ideal as a bridge solution, but there are times when fully adopting HubSpot forms is the better option.

Good Reasons to Migrate

• You need advanced features such as progressive profiling or smart fields.
• You want fine-grained style control from within the form editor.
• You require comprehensive conversion analytics and testing on critical landing pages.

By gradually replacing legacy forms with native HubSpot forms, you can improve tracking quality and simplify ongoing optimization.

Additional Resources for HubSpot Form Management

For a deeper technical explanation of how non-HubSpot forms work and the latest compatibility notes, review HubSpot’s official FAQ on the subject in the knowledge base at this article on non-HubSpot forms.

If you want expert help auditing your current setup or planning a migration to native HubSpot forms, you can consult a specialist agency such as Consultevo for strategy and implementation guidance.

By understanding how HubSpot handles non-HubSpot forms, you can capture more leads accurately, maintain cleaner data, and move toward a more consistent and fully integrated form strategy across your entire website.

Need Help With Hubspot?

If you want expert help building, automating, or scaling your Hubspot , work with ConsultEvo, a team who has a decade of Hubspot experience.

Scale Hubspot

“`