← Back to blog

Leads Submitted But Missing in HubSpot? What to Check

Kazem Hegaze·CRM & handoff·
CRMdiagnosis
A confirmed form submission has no matching contact in the CRM.

The form submitted, the visitor saw a thank you page, and the contact is not in HubSpot. Somewhere between the browser and the CRM record, the lead stopped. This is a delivery problem, not a marketing problem, and it has a short list of usual causes.

Work down the chain in order. Each step tells you whether to keep going or stop.

1. Confirm the submission actually happened

Before anything else, prove a real submission exists. Submit the form yourself with a recognisable test address, on mobile and on desktop, and watch what happens after the click.

If your own test never lands either, you have a reproducible break and the rest of this list gets much faster. If your test lands but real leads do not, the problem is conditional: one device, one browser, one traffic source, or one field value.

2. Check whether the lead exists somewhere else

A missing HubSpot contact does not mean a missing lead. Check the form provider's own submission log, the notification inbox, and any spreadsheet or webhook receiver in the path. If the submission is recorded there, the form worked and the handoff to HubSpot is what failed. That narrows the search to one hop.

3. Look at the integration doing the delivery

Most form to HubSpot paths run through something: a native integration, a webhook, an automation platform, or a tag that fires the HubSpot API. Each has its own failure modes.

  • The connection expired. OAuth tokens have a lifetime. When one lapses, delivery stops silently and nothing in the marketing dashboard changes.
  • A required property is missing or invalid. If HubSpot rejects the payload because a property no longer exists, has a different internal name, or fails validation, the whole contact fails to create.
  • A field mapping changed. Someone renamed a form field. The integration still posts the old key, HubSpot ignores it, and depending on setup the contact either fails or arrives blank.
  • You hit a rate limit or quota. Bursts get dropped rather than queued in some setups.
  • The automation is paused. Workflows get paused for testing and not resumed.

4. Check the contact is created but not visible

This one wastes the most time. The contact exists, but you cannot see it, because:

  • It was created as a duplicate and merged into an existing record, so no new row appeared in the list you were watching.
  • It went to a different HubSpot account or portal than the one you are looking at, which happens after an agency reconnects the wrong account.
  • Your list or view is filtered by an owner, lifecycle stage, or source that the new contact does not match.
  • The contact exists but the associated deal or task did not, so the sales team says "no leads" while the record is sitting there.
  • A workflow that should have assigned an owner or created a deal never ran, because the contact had already been enrolled once and re-enrollment is off for that workflow, which is the default.
  • A cleanup job, an import, or a colleague deleted it. Check the recently deleted contacts list, since HubSpot lets you restore deleted contacts for a limited period.

Search by email address across all contacts before concluding it is missing.

5. Separate a real leak from a counting problem

If submits are also down in your analytics, the funnel broke earlier and the CRM is just the place you noticed. If submits are stable and only CRM records fell, the handoff is the break. That distinction decides who fixes it. The same logic applies one step earlier in the funnel, covered in form views are stable but submits dropped.

Where to look in HubSpot, step by step

Take one submission you know happened, with its email and approximate time, and walk it through these screens in order.

  1. Contacts search, with filters cleared. Search the exact email from the Contacts index after switching to the unfiltered "All contacts" view. Saved views hide records quietly. If the person may already have existed, also search by name and company, because a merge can leave the new address attached to an older record.
  2. The form's submissions. If it is a HubSpot form, open it under Marketing, Forms and look at its submissions. A submission there means HubSpot received the data, so the question becomes how the contact was created or shown. If a third party form posts through an integration, HubSpot usually has no record of a failed attempt, so the sending tool's log is the source of truth.
  3. The contact's activity timeline. Filter the timeline to form submissions. Compare the create date with the submit time, and check the source properties to see which integration or form created the record.
  4. Property history. On the record, view the history of lifecycle stage and contact owner. HubSpot shows what set each value and when, so you can see whether a workflow, an import or an integration changed it.
  5. Workflow history. For any workflow that should have assigned, notified or created a deal, open the workflow and check its enrollment history and action logs for that contact. Look for a contact that never enrolled, or an action that errored.
  6. Connected apps and the sending tool's logs. Under Settings, Integrations, Connected apps, confirm the delivering app is still installed. Then check the automation platform's run history for rejected requests, which usually name the failing property.

Reconcile the three counts

Form tool, ads platform and HubSpot will never show the same number. Explain each gap, and what is left over is the real leak. Count all three in the same time zone, or a form tool logging in UTC can shift leads across a day boundary.

Illustrative example, one week, one client:

SourceCountWhat explains the gap
Ads platform conversions140Attribution windows, view-through credit and duplicate pixel fires
Form provider submissions118The baseline for the handoff check
New HubSpot contacts8114 were repeat people deduplicated into existing records, 6 were tests or spam
Assigned to sales747 contacts had no owner because the routing workflow filtered on a lifecycle stage they did not have

After the explained gaps, 17 submissions remain with no record anywhere in HubSpot. All 17 came from one form after Tuesday afternoon. That is the leak: a question about one form, not a dispute about totals. To count returning people, filter contacts on "Recent conversion date" in the window rather than create date. Size the drop first with the lead drop checker.

Example

Illustrative scenario. An agency added a consent checkbox to a client's form and mapped it to a new HubSpot property. The property was created in the sandbox portal, not the live one. Every submission after that failed validation on the live side. The form kept showing its thank you message, so nothing looked broken for four days. The fix took ten minutes once found. Now every field change gets a live test submission traced into HubSpot by email the same day.

How Quarkad helps

Quarkad records every website form submit as a pending handoff and then checks whether a matching contact appears in HubSpot inside a verification window. Matching is exact where possible, using a submission key the Quarkad snippet writes into a custom contact property that is provisioned when you connect, and falls back to a hashed email matched inside the same window. Each submission ends up verified, verified late, failed, or unverified, so a missing lead is a recorded outcome rather than an anecdote from sales. See HubSpot CRM handoff monitoring.

Related

FAQ

Can I recover leads that never reached the CRM? Sometimes. If the form provider logged the submission, you can import it. If nothing in the chain stored it, the lead is gone, which is why time to detection matters more here than in most funnel problems.

Is a delayed contact the same as a failed one? No. Some integrations retry and the contact arrives late. Treat late delivery as its own category, because the lead is recoverable but the sales response was slow.

Why does HubSpot show fewer new contacts than form submissions when nothing is broken? HubSpot deduplicates contacts by email, so a returning person updates their existing record. Spam, tests and double submits also inflate the form count.

How long should I wait before calling a lead missing? Long enough to cover your slowest normal delivery. Direct integrations usually take minutes, queued automations longer. Anything after that is late, and anything absent is failed. The CRM handoff glossary entry covers how those outcomes differ.

Does one successful test submission prove the path works? Only for your values on your device. Partial failures often depend on a field value or browser. How to detect form to CRM breaks explains how to catch the cases a single test misses.

Leads Submitted But Missing in HubSpot? What to Check | Quarkad