For a marketing manager: make every web lead arrive once, reach an owner and be noticed if the form breaks

Write the path of one lead

You pay for web leads, so write down what should happen to one of them. Which form or tool captures it? Where does it land in HubSpot, and is it matched to an existing contact and company? Who owns it, by what rule, and who is told? Does anything sync to Salesforce, and which system should win? A paragraph for each stage is enough. Gaps in the paragraph are where leads are lost.

Check matching and ownership with invented leads

Test with leads you made up, never real people. Submit the same synthetic email twice, two people from one domain, and two different people from one browser, and count contacts and companies. Then check ownership: one synthetic lead per routing rule, one for each edge, and one that matches nothing. HubSpot sends no owner notification for a contact with no owner, so an unowned lead can sit unnoticed unless a view or alert watches for it. Make sure test leads cannot email or notify real people.

• Same email twice: one contact, two submissions.
• Two people at one domain: two contacts, one company.
• A lead that matches no rule: the named fallback owner, with an alert.

Watch the sync and the team

If HubSpot syncs with Salesforce, each mapped field has a sync rule, and a value that keeps reverting is often the rule doing its job. Rotation counts reset when owners are added or removed, so every change to the sales team is also a change to routing, and should trigger a retest. Make one person responsible for the lead path, and give them a weekly view of unowned leads, new duplicates and sync errors.

Which paid job fits

If one form path creates duplicates, the outcome for one path changes it and proves it with six synthetic submissions. If leads have no owner or the wrong one, the routing outcome rebuilds one workflow from your approved rule table and tests it with synthetic leads for every rule, edge case and the fallback, and a pool change. If one field changes back, the sync outcome covers one mapped field pair. If several are broken at once, the project tests up to three paths from form to owner. If you want it kept true, the standing service checks weekly and repairs on a copy or with synthetic records. No outcome promises how quickly a lead is contacted.