Key Takeaways
- Choose one intentional route for each form submission to reach HubSpot. Overlapping integrations can create duplicate activity and confusing records.
- Map each field to the correct property and decide which existing values a new enquiry may update.
- Test the website, CRM record, assignment and notification together. A confirmation message alone does not prove delivery.
- Contact matching and duplicate submissions are different problems; investigate them separately.
- Keep monitoring and a recovery process for failures, with access and data retention appropriate to the information collected.
To connect WordPress forms to HubSpot reliably, start by defining what should happen to a valid enquiry. Identify the capture method, the fields to store, the contact to create or update and the person who needs to act on it.
Then test that complete journey. Installing a plugin or seeing a green tick in an integration screen does not prove the right information arrives in the right place.
You do not need to move the whole website into HubSpot to use its CRM. This guide is about keeping WordPress and connecting its enquiry process. A full platform move has different requirements, covered in our HubSpot Content Hub migration guide.
Draw the Existing Enquiry Journey First
List every active form and where it appears. Include service pages, campaign landing pages, pop-ups and older pages still linked from emails. Record the form plugin, notification recipients and any current CRM or automation connections.
For one form, trace a submission from the browser to its final destination. Does WordPress save an entry? Does a connector send it to HubSpot? Is another tracking feature also collecting it? Does a workflow create a task or deal afterwards?
This inventory often explains the confusion. Two mechanisms may be recording the same enquiry, or a form may depend on an old account connection that nobody owns.
Our WordPress development work treats forms as business functions, not decorative page elements. The integration needs an owner and a testable definition of success.
Choose One Capture Method Deliberately
Common options include embedding a HubSpot form, using a supported connector for the existing WordPress form, or building a controlled integration. HubSpot also provides a non-HubSpot forms collection feature for compatible external forms.
Do not assume these options behave identically. HubSpot's non-HubSpot forms documentation explains that collection depends on its tracking code and the form meeting specific requirements. It can record partial attempts when a visitor clicks submit before completing validation, and cookie behaviour can affect contact attribution.
Those limitations may be acceptable for one use case and unsuitable for another. Review the actual form behaviour rather than choosing solely by how quickly the connection can be switched on.
For a connector or custom integration, ask what event triggers the transfer. Ideally, the process should distinguish an accepted, valid enquiry from an attempted click. Confirm what happens if the external service is unavailable and how the team will discover the failure.
Write a Field Map the Team Can Understand
Create a small specification before configuring the integration. It should show the website field, destination property, expected format and update rule.
For example, a service selector may need to store an agreed internal value rather than the visible wording. A phone number should not be treated as a number that loses a leading zero. An optional field should not accidentally erase a useful existing value when it is blank.
| Website information | Mapping decision | Test to run |
|---|---|---|
| Email address | Contact matching and validation | New and returning contact |
| Service requested | Agreed property and allowed values | Every selectable option |
| Phone number | Text format and optionality | UK number with leading zero |
| Message | Suitable storage and length handling | Long but valid enquiry |
| Communication preference | Separate, explicit handling | Each available choice |
Keep operational enquiry processing separate from marketing permissions. Do not infer permission for unrelated marketing simply because someone asked for a quotation. The exact privacy and consent design should reflect your business's requirements and appropriate advice.
Decide What a Returning Enquiry May Change
A returning contact may already have a company, owner, lifecycle stage and useful notes. A new form submission should not casually reset those fields.
HubSpot's deduplication guidance explains that email addresses are used to match contacts in supported creation and submission flows. Matching an existing record is not the same as deciding which values should be overwritten.
Agree those update rules explicitly. A fresh service request may belong in submission history or a separate enquiry record rather than replacing the contact's original source. A blank company field should not automatically remove an established association.
Also plan for shared addresses and changed email addresses. Do not merge contacts merely because their names look similar. A sales administrator needs a safe way to review ambiguous cases without losing the history of either person.
Separate Three Different Duplicate Problems
The word “duplicate” can describe several failures. First, the same submission may be captured twice. Second, one person may have more than one contact record. Third, an automation may create several tasks or deals from one accepted enquiry.
Each needs a different investigation. Disabling one capture route might fix repeated submissions but will not automatically merge historical contacts. Improving contact matching will not stop a workflow from creating two deals.
Give each accepted submission a stable identifier where the integration supports it, and use that to recognise a retry. Keep the identifier separate from the person's identity: one contact can legitimately make several enquiries.
Do not solve the problem by deleting every repeated-looking record automatically. Repeated messages may contain changed requirements, and the team may need the history. Review the cause and preserve relevant evidence before cleaning up.
Test More Than the Happy Path
Use clearly labelled test data and a controlled test destination. Tell the team when testing will occur so synthetic enquiries are not treated as genuine opportunities.
Run a new-contact submission, a returning-contact submission and an invalid attempt followed by a correction. Test on mobile, with a long message, with optional fields empty and with each service option selected.
Include a repeated click and a connection failure. The expected outcome should be defined in advance. Does the form show an honest error, queue the enquiry for retry or save a recoverable entry? A reassuring success message is wrong if the system has neither delivered nor safely retained the request.
For every test, check the actual contact, property values, submission history, assignment and notification. Record what happened rather than relying on memory. Our conversion rate optimisation audit guide explains why the whole enquiry journey matters to conversion quality.
Check Notifications and Ownership
A lead stored in HubSpot can still be effectively lost if nobody sees it. Decide who owns each type of enquiry and how they are notified.
Use a monitored team process rather than a single personal inbox where possible. Define what happens when the usual owner is away, when a request has no matching service category or when a notification fails.
Avoid sending every submission to everyone indefinitely. Too many notifications make genuine exceptions harder to spot. Route ordinary work clearly and reserve alerts for failures or items needing attention.
An automation review can help connect capture to follow-up without introducing unnecessary steps. The aim is a dependable handover, not the largest possible workflow diagram.
Preserve Useful Attribution Without Polluting It
The team may want to know which page or campaign generated the enquiry. Decide which source details are useful and how they are captured through the chosen integration.
Distinguish the page where the form was submitted from the first page the person visited. They answer different questions. Do not overwrite an original acquisition source every time the contact returns.
Avoid putting personal information into URLs or general analytics events. Keep enquiry content in the appropriate CRM or form system with suitable access controls. A reporting field does not need the customer's full message to show which service page was involved.
If source information is missing because tracking was unavailable or consent was not given, label that limitation. Do not invent a channel to make the dashboard look complete.
Keep a Recovery Procedure
Document how the team checks for failed transfers and how a valid enquiry is safely replayed. The process should not require copying customer information into an unapproved tool or sharing an administrator password.
Define retention for any local form entries or integration logs. Keeping a recoverable record can help reliability, but retaining every message forever is not a sensible default. Balance operational needs with the relevant privacy obligations and access restrictions.
Re-test after changes to the form plugin, consent setup, caching, CRM properties or integration account. A connection that worked at launch can fail later when a field is renamed or permissions change.
For website maintenance and support, include form delivery in the recurring checks. A homepage loading successfully does not tell you whether enquiries are reaching the team.
A Sensible First Fix
If leads are currently missing or duplicated, start with one form and one labelled test submission. Trace it through every system and record where the behaviour differs from the intended journey.
Do not install another connector before understanding the existing route. You may add a third copy of the same problem.
Once the route is clear, agree the field map, matching rules and recovery process, then test them with the team responsible for enquiries. A website audit should leave you with that evidence and a short, owned action list—not just a screenshot showing that two accounts are connected.
Frequently Asked Questions
Do we have to move WordPress to HubSpot to connect forms?
No. You can keep WordPress and use a suitable embedded form, connector or integration. Choose the method according to the form's behaviour, required fields and operational needs.
Why does one enquiry appear several times?
Possible causes include overlapping capture routes, partial submission attempts, retries or downstream workflows. Distinguish duplicate submissions from duplicate contacts and duplicate tasks before changing the setup.
Does a WordPress thank-you message prove HubSpot received the lead?
No. Verify the CRM record, mapped fields, assignment and notification. The form should only report success according to a clearly defined delivery or recoverable-storage process.
Should new submissions overwrite existing contact details?
Only according to agreed rules. Some fields should update, while others should preserve established information or keep a submission history. Test returning contacts and blank optional values explicitly.
What should we test after changing the integration?
Test new and returning contacts, invalid entries, repeated clicks, mobile use and service failures. Check the complete journey, including field values, contact matching, notifications and a safe recovery route.
