If a HubSpot form submission is not showing, first identify which record is missing. The submission may be in HubSpot while the contact already existed, the contact may not have been created, or only the email alert may be missing. These are separate events with different fixes.
Start with the record that is actually missing
Do not start by changing the form or workflow. Check the form’s submission records first, then look for a contact and a notification. This sequence tells you whether the break happened at the form, contact, or alert stage.
| What you see | What it may mean | First check |
|---|---|---|
| No entry in the form’s submissions | The submission may not have been processed, or you may be looking at the wrong form or date range. | Confirm the form and time range, then compare an isolated test on its standalone page with the embedded version. |
| A submission exists, but no new contact appeared | The same person may already have a contact record, or contact creation may be blocked by missing email data or record history. | Search HubSpot by the submitted email and inspect the submission details and contact timeline. |
| A contact exists, but the team received no alert | The submission and notification are separate; notification settings may be off or the wrong people may be selected. | Check user notification settings and the recipient settings on that form. |
| The form entry exists, but no page or associated-object activity appears | Page tracking or the association context may be missing even though the submission itself was recorded. | Check the tracking code, form fields for the associated object, or the Forms API page context. |
1. Find the submission in the form, not only in Contacts
Open the correct form’s submission view and check the relevant date range, form name, and submitted email. If your team manages multiple HubSpot portals or similar forms, verify the portal and exact form before treating an empty result as a lost submission.
HubSpot counts submissions separately from contacts. One person can submit the same form more than once; HubSpot may record each submission while keeping one contact. A submission can also remain in the form analytics after its contact is deleted. That is why the total number of submissions can be greater than the number of contacts in a list filtered by that form. See HubSpot’s guide to troubleshooting form submissions.
Also check the form’s spam submissions area. A legitimate-looking form event may have been classified as spam and separated from the usual submissions view. HubSpot explains how to inspect and manage these records in Manage spam form submissions.
2. Search for an existing contact before expecting a new one
Search the CRM by the email submitted on the form. If that email already belongs to a contact, HubSpot can update the existing record instead of creating a second one. HubSpot may also associate a browser’s tracked submission with a contact that already has the browser’s tracking cookie. Review the contact’s recent activity and property history for the submission time.
If there is no contact, verify that the form uses HubSpot’s default Email property and that a value was submitted. When a form is designed to accept submissions without an email address, check the setting that allows those submissions to create contacts. HubSpot’s troubleshooting guide notes that a missing or unpopulated Email field, a disabled no-email setting, or a deleted contact can explain a “No contact record” result.
Do not create another contact manually just because one is not visible in a form-filtered list. First confirm whether the submission updated an existing record, belongs to a deleted record, or was separated as spam. Otherwise, a manual workaround can create duplicate records or hide the original cause.
3. Separate a broken embedded form from a CRM issue
If the form has no submission entry, compare the embedded form with its standalone page. HubSpot recommends opening the form’s standalone URL and making a controlled test submission. If that works but the embedded version does not, the page containing the embed is a likely part of the problem. Ask the site developer to inspect page scripts and attached stylesheets, then retest after a targeted change.
For a controlled test, use an address your team owns and note the exact time and form name. Avoid submitting real prospect details or repeatedly testing a live sales form: a test can update an existing contact or trigger internal automations. Compare the same form in its standalone and embedded locations so you can isolate the page from the form itself.
If the form is sent through the HubSpot Forms API, inspect the request separately from the browser embed. HubSpot identifies missing pageName or pageUrl parameters as a cause of a “No record” error, where HubSpot cannot determine where the submission occurred. This is a page-context problem; it is not the same as proving that no contact could have been created.
For page views that are absent after a submission, check tracking code, cookie consent, and analytics IP exclusions. HubSpot notes that a form submission can be recorded while a page view is not, for example when cookies are blocked or an IP address is excluded. Do not use a missing page view as the only test of whether the submission was captured.
4. Check email notifications as a separate path
If the submission appears in HubSpot but nobody received an email alert, inspect notifications rather than rebuilding the form. A user must enable form-submission notifications in their HubSpot notification settings, and the individual form must be configured for the users or teams who should receive them. Follow HubSpot’s steps for setting up form-submission notifications.
After checking those settings, compare the submission record with the intended recipient list. The record in HubSpot is the source of truth for whether the form was captured; the alert is a separate delivery path.
5. Check associated records and workflows separately
A submission on a contact does not automatically mean it will appear on every associated company or other object. For an activity to appear on an associated object’s timeline, HubSpot says the form must include a field for that object and the field must have a value when the form is submitted. Check the relevant association and field before changing the form’s contact fields.
If the contact and submission are present but a workflow did not run, treat that as a workflow-enrollment problem. Review its enrollment history and re-enrollment settings separately; a missing workflow action is not evidence that the form submission disappeared. See our guide to diagnosing a HubSpot workflow that is not enrolling contacts.
A short diagnostic sequence to keep
- Confirm the form entry. Search the correct form and time range, then inspect its spam submissions area.
- Search for the contact by email. A submission may have updated an existing contact rather than created a new one.
- Compare standalone and embedded behavior. If only the embedded form fails, inspect that page’s scripts and styles.
- For API submissions, inspect request context. Confirm the page name and URL are passed where required.
- Check notifications and workflows independently. Each is a separate downstream path after submission.
- Document one example. Record the form, timestamp, email you control, portal, result, and the first step where the expected record is missing.
Frequently asked questions
Why do form submissions outnumber contacts?
One existing contact can submit multiple times, and a deleted contact’s submission can still count in form analytics. Submission totals and unique contact totals measure different things.
Why did the form update a contact instead of creating a new one?
The submitted email may already belong to a contact, or the tracked browser may be associated with an existing contact. Search by email and review the record’s recent activity before creating another record.
Does a missing notification mean HubSpot lost the form submission?
No. Check the form’s submission record first. If it exists, review user notification settings and the form’s selected recipients as a separate issue.
Why is there no page view even though a submission exists?
Page-view tracking can be affected by cookies, consent, tracking-code behavior, or excluded IP addresses. HubSpot can record the form submission even when it does not record a page view.
Official references
- HubSpot: Troubleshoot HubSpot forms
- HubSpot: Manage spam form submissions
- HubSpot: Set up form-submission notifications
If form submissions are appearing in HubSpot but your team still cannot connect the form, contact, and sales follow-up, you can start with a Revenue Diagnostic.
How did this article land?
Choose one reaction. You can change it anytime.