You’ve probably run into this before: your team relies on forms built in Webflow, WordPress, or a custom application. Rebuilding each one inside HubSpot? That’s slow, frustrating, and often impossible when your forms depend on specific JavaScript or back-end logic. But without a sync with HubSpot, your pipeline misses key data—and your revenue teams are left guessing.
Even if you’ve tried to connect outside forms, you’ve likely hit walls. HubSpot’s tracking can break down when forms don’t support embedded cookies or custom fields. The result? Incomplete contact records, duplicated leads, and a CRM that slowly drifts out of sync with the real actions users take.
This guide shows you how to route external form submissions directly into HubSpot CRM using the form API—without the need to rebuild your front end. You’ll get a clear understanding of how HubSpot handles non-native form data, how to structure API calls, and how to confirm submissions land exactly where they should in your contact database.
Beginner’s Guide to Using Non-HubSpot Forms with the HubSpot Tracking Code
Within the HubSpot platform, “non-HubSpot forms” refer to form submissions collected on websites or apps outside of HubSpot’s built-in form tool—yet still sent into HubSpot’s system.
When enabled under Settings > Marketing > Forms > Non-HubSpot Forms, this feature allows HubSpot’s tracking script to recognize and log basic HTML form submissions from webpages where the HubSpot tracking code is present.
For most HTML-based forms, detection happens automatically. HubSpot interprets the form fields and tries to match them with default contact properties. But if your forms use dynamic rendering (like with React, Vue, or JavaScript injection), or you want total control, you’ll need to use the HubSpot Form API to send form data via a secure HTTP request.
Either way, this feature ensures that external form submissions enrich your CRM—the way native HubSpot forms do—without forcing you to change how your forms are built.
How It Works Under the Hood
- Automatic form detection via HubSpot tracking code
When the HubSpot tracking script is present, and you’ve enabled non-HubSpot form capture, HubSpot listens for submit events on your site. It reads the field names and values, maps them to contact properties, and posts the form data to the associated contact. If HubSpot recognizes the visitor via email or cookie, it updates the existing record. Otherwise, it creates a new one.
- Form API submission via manual POST request
For more structured control, developers use HubSpot’s form API endpoint:
https://api.hsforms.com/submissions/v3/integration/submit/:portalId/:formGuid
This method is ideal when your forms are dynamic or hosted within JS apps.
You’ll include:
- Form GUID and Portal ID: To tie submissions to a specific location in your HubSpot account.
- Fields array: Each form field with a name and value.
- Context object: Contains metadata like hubspotutk (tracking cookie), page URL, IP, and page title.
- Legal consent data: Required for GDPR compliance to ensure lawful contact creation.
Successfully submitting returns returns a confirmation response and populates the contact record with full-form activity, visible in timelines.
For advanced marketing ops, optional parameters let you tag submissions with a specific lifecycle stage, campaign, or source—making attribution and segmentation much easier later.
Main Uses Inside HubSpot
Marketing lead capture from external sites
If you build your funnels in tools like Webflow, WordPress, or Unbounce, you don’t have to migrate everything into HubSpot just to track leads. Non-HubSpot forms let you keep your front-end as is while syncing prospects to your CRM.
Example: Your team runs a webinar landing page in Webflow. The signup form sends First Name, Email, Company, and Job Title to HubSpot via the form API. A workflow takes over: the contact is added to the webinar list, receives a confirmation email, and has their lifecycle stage marked as Lead—all automatically.
Sales and pricing inquiry forms
Sales teams often need flexible, logic-driven forms that adapt to user input—something HubSpot’s native builder can struggle with. Keeping your modern forms and still capturing sales-ready leads is possible with API integration.
Example: A React-based pricing form collects custom product selections and contact details. It validates the inputs and then submits the form via the HubSpot API. The contact record is created or updated, and a task is triggered for the sales rep to follow up the same day.
Support requests and feedback
Customer support often lives in separate portals. Whether it’s feature feedback or bug reports, you can route these submissions into HubSpot’s Service tools using the same API setup.
Example: A logged-in customer fills out a bug report in your product portal. The form includes an email address, a product ID, and a high-urgency flag. The form data lands in HubSpot under their contact record and triggers a workflow that creates a ticket and pings your support Slack channel.
Partner or affiliate signups
If you’re managing partnerships or affiliates through custom web apps, you can bring that entire process into HubSpot without migrating your platform.
Example: Partner prospects apply using a form on partners.company.com. That submission goes to HubSpot via the API and is tagged with a custom “Partner Prospect” stage. Now, the partnerships team can track funnel velocity, measure follow-up time, and view conversion rates—all inside HubSpot.
Common Setup Errors and Missteps
Not installing HubSpot’s tracking code
If the tracking code isn’t on the page, HubSpot won’t see forms no matter how well they’re built.
Make sure the tracking code is placed in your site’s global footer before enabling non-HubSpot forms.
Field name mismatches
If your form uses field names that don’t align with HubSpot property internal names, the data might not show up—at all or in the right place.
Fix this by either renaming your external field inputs or mapping them directly during your API call.
Missing the hubspotutk in API context
If you forget to include the user’s tracking cookie, HubSpot may create new contact records even for existing users.
Always grab the hubspotutk from cookies and pass it in the context object to keep your CRM data clean.
Skipping GDPR-compliant consent
If you operate in regulated markets and don’t include a proper legal basis or consent data, HubSpot may block the submission or log it out of compliance.
Make sure your payload includes the legal consent structure HubSpot’s expecting.
Step-by-Step Setup or Use Guide
Before you begin, double-check that you have Admin permission in HubSpot, and either have API credentials ready or have embedded the tracking code site-wide.
- Enable non-HubSpot form capture
Go to Settings > Marketing > Forms > Non-HubSpot Forms and turn the toggle on.
- Install the HubSpot tracking code on your site
From Settings > Account Setup > Tracking Code, copy the script and place it right before the </body> tag of each page with forms.
- Test automatic form detection
Submit a form on your site. Then check Marketing > Lead Capture > Forms to see if HubSpot recorded the submission as a non-HubSpot form.
- Confirm or adjust field mapping
Under the new form listing, make sure your form inputs map correctly to HubSpot contact properties.
- If you’re using the API, create a HubSpot form first
Go to Marketing > Lead Capture > Forms > Create Form > Embedded Form. You’ll use its GUID and your Portal ID in your API call.
- Craft your API call
POST to the form endpoint with:
- The correct fields array
- A context object containing hutk, pageUri, and pageName
- Legal consent object (if necessary)
- Run a test submission
Use a tool like Postman or your web app to submit a test request. Check the contact record activity pane to confirm the submission shows and maps as expected.
- Automate the follow-up
In Automation > Workflows, set up triggers for your new form. Build actions like sending a notification, assigning an owner, or setting a lifecycle stage.
This process ensures all parts of your external submission—tracking, legal consent, field mapping, and follow-up—are reliable and audit-friendly.
Measuring Results in HubSpot
- Form Submissions Report
Navigate to Reports > Analytics Tools > Forms and view submission volume by form. Yes, non-HubSpot forms appear right next to native forms. - Campaign and source attribution
Make sure UTM parameters are passed through the URL or hidden fields. HubSpot logs this data in each contact’s “Original Source” or “Latest Source” property. - Contact Property Completion Analysis
Build a custom report to audit completion rates of fields like name, company, and phone. It’s an easy way to catch if your API mapping dropped any data. - Workflow engagement dashboards
Want to know if your non-HubSpot leads are converting? Track entrance rates into workflows by submission, and review performance metrics like email opens or deals created.
Key checkpoints:
- Give every external form a unique ID or naming convention
- Check contact records weekly for score consistency and deduplication
- If using the API, review server logs and errors regularly to catch operational bugs
Short Example That Ties It Together
Picture your dev team building a product demo request form inside a React app. You want every submission to create or update a contact in HubSpot, but you can’t (and don’t want to) rebuild the form inside the CRM.
Your developer creates a HubSpot form to provide a consistent endpoint, then sets up an API call from the front end. The payload includes fields such as Name, Email, and Company, along with the visitor’s tracking cookie.
As soon as someone submits the demo form, HubSpot logs the activity, enriches the contact record, and triggers a workflow to notify Sales and assign ownership. Later, your marketing ops team checks the analytics dashboard to validate the lead volume and refine conversion paths—all without touching the original app code.
How INSIDEA Helps
If you’re juggling WordPress forms, embedded portals, or custom apps—and your CRM data is slipping through the cracks—INSIDEA helps you close the gap.
We configure, test, and maintain your HubSpot form API setup so your teams get complete, dependable contact records every time someone submits a form—no matter where it’s hosted.
Get strategic and technical support across:
- HubSpot onboarding: Set up your portal, properties, and automation from day one
- HubSpot maintenance: Keep your records organized, workflows error-free, and data flowing smoothly
- Workflow optimization: Build automations that follow your actual sales and marketing motion
- Reporting analytics: Create dashboards that surface what’s working (and what’s not)
- API configuration: Ensure external forms sync cleanly, with consent and tracking intact
Ready to simplify your CRM sync and stop losing leads? Connect with our automation experts, or check out INSIDEA’s HubSpot consulting services.
