Who this is for
A marketing or sales operations manager whose HubSpot database fills with duplicate contacts or companies, or whose contacts are overwritten, after leads arrive from web forms.
The same person appears twice, several companies share one domain, or a new enquiry replaced another person's details on a shared computer.
The result
With synthetic submissions through the one agreed HubSpot form or integration, the same email submitted twice leaves one contact with both submissions recorded, two people at one domain leave two contacts and one company, and two different people on one browser stay two separate contacts.
What is included
- One form path: either one HubSpot form, or one integration that creates contacts and companies through HubSpot's API
- Diagnose from the form settings, the integration's steps and a few redacted examples why that path produces duplicates
- Change the form setting, the integration step or the matching rule on that path so contacts match on email and companies on domain as agreed
- Run six synthetic submissions (two for each of three checks) in your HubSpot account, or a test account if you have one, and record the contact and company counts after each
You receive
- A short written diagnosis naming the cause on that form path
- The changed form setting, integration step or workflow, with change notes and how to reverse them
- Before and after contact and company counts for the six synthetic submissions
- A list of other form paths in the account that were not examined and may behave differently
What is not included
- A form on your own page that HubSpot collects through its tracking code: HubSpot documents that all submissions from one cookie go to one contact even with different emails, so this job cannot promise separate contacts there. Moving that form to a HubSpot form or sending submissions through HubSpot's Forms API is a separate quote
- Merging or deleting existing duplicate contacts or companies: HubSpot documents that merged contacts cannot be unmerged, so this is a separate job needing your approval of the matching rule
- More than one form path, or any redesign of your lead process
- Data-protection, consent or marketing-permission advice
- Duplicates created by the Salesforce sync, which follow different rules and need their own diagnosis
- Real contacts or any email, task or notification sent to real people during testing
What we need from you first
- How the lead reaches HubSpot: a HubSpot form or an integration, and its name
- Two redacted examples of the duplicate with created dates and the source shown on each
- Whether the form has an email field, and whether the setting that creates contacts from unknown email addresses is on
- Do not send contact lists, exports, passwords or an account invitation in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- Submitting the same synthetic email address twice through the agreed path leaves exactly one contact, and both submissions appear in its history.
- Submitting two different synthetic email addresses at one synthetic company domain leaves two contacts associated with exactly one company.
- Submitting two different synthetic people from one browser leaves two separate contacts, neither overwritten by the other.
- The change notes list each changed setting or step with its previous value, and no real contact was merged, deleted or messaged during testing.
You inspect the counts and the change notes, then sign off before payment. You delete the test contacts and check one genuine submission under your own account.
When we would stop or decline
- The duplicates come from the Salesforce integration, an import or manual entry rather than a web-form path
- The path is a form on your own page collected through the tracking code, which this fixed job does not cover
- Several form paths and integrations each create duplicates and no single path can be named
- Test contacts would trigger real emails, calls or tasks that cannot be switched off
Questions
Will you merge my existing duplicates?
No. HubSpot says merges cannot be undone, so merging needs a separate agreed scope with your sign-off on which record wins. This job stops new duplicates on one path.
Is this about the Salesforce sync?
No. Duplicates arriving through the Salesforce sync follow Salesforce matching rules and HubSpot's sync error list. This job covers one web-form path.
Do you need real contacts to test?
No. We use synthetic addresses that match nothing in your database. The test contacts are created in your account, or a test account if you have one, so any workflow that reacts to a new contact has to be switched off or filtered first, and you delete the test records afterwards.
Does this cover a form on my own website that is not a HubSpot form?
Not when HubSpot collects it through its tracking code. HubSpot documents that every submission from one browser then goes to one contact, so the separate-contacts test could not be met. Moving that form to a HubSpot form or the Forms API is a separate quote.
Price and terms
£225 · untested offer price. £225 after the agreed checks pass and you sign off. No payment before sign-off.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.