When a HubSpot form is embedded on a WordPress page, the visitor can submit and see a success message while the contact never appears in HubSpot. The form layer reports success, but the record is lost between the two systems.
Fixstable · State
WordPress Form
What we believe is broken
A business owner tests their own form, gets the "thank you" message, and then finds no new contact in HubSpot. The lead is silently dropped with no error shown to the visitor.
A common cause is a stale or renamed HubSpot form ID in the embed code: the submission returns HTTP 200 at the form layer while HubSpot rejects the payload. This is a known failure mode, not a measured statistic.
The solution
Confirm the form ID in the embed matches an active HubSpot form, verify the form is not filtering contacts by email domain, and test with a fresh non-HubSpot email address to rule out a contact-creation filter.
1. Open the page and copy the HubSpot form ID from the embed.
2. In HubSpot, open Marketing > Forms and confirm that ID still exists.
3. Submit the form with a fresh test email.
4. Check HubSpot > Contacts for the new record.
5. If missing, review the form's submission settings and any workflow that may filter contacts.
Your form is submitting, but the contact is being dropped between WordPress and HubSpot — usually a stale form ID or a contact-creation filter.
What makes this data
Canvza's generic hubspot-form element is certified to bind to HubSpot forms and render on the Northstar demo (home, contact, and resources pages). The frontend returns HTTP 200 and the embedded form, fields, and submit control are all present. A real end-to-end submission is pending administrator QA identity and has not yet been recorded.
A "silent drop" is a submission that succeeds at the form layer but never creates a record in the destination system — no error is shown to the visitor.
The visitor submits, the contact appears in HubSpot, and the follow-up sequence fires automatically.