When to run this checklist
Run it before any new lead source goes live: a new form, a new landing page template, a native lead form on an ad platform, a chat tool, an event list import. Run it again after any change to the plumbing underneath: new or renamed CRM fields, redrawn territories, a new segment, a change to lead scoringAssigning points to leads for fit and behaviour to decide which are ready for sales. rules or lifecycle stagesA CRM field recording where a contact stands in the relationship, such as subscriber, lead, opportunity or customer., or a new sales hire who should start receiving leads. Each of those can break a route that worked yesterday without any visible error.
The owner is usually marketing operations or whoever administers the CRM, with a named person from sales confirming the routing group, because only sales can say whether a test lead reached the right person. Run it in a test-safe way: mark test leads clearly so they can be excluded from reporting and deleted afterwards, and warn the sales owners who will receive them.
Before you start
- The routing rules in writing: territories, segments, round-robin groups and the fallback owner.
- The field map: each form field, the CRM property it should fill and any hidden fieldsA form field the visitor never sees that records values such as source, campaign and landing page, so each lead arrives in the CRM with its origin. such as source and campaign.
- The agreed stage definitions, including what makes a lead an MQLA lead that marketing judges ready for sales follow-up against agreed criteria. and what sales must do to accept it as a sales-qualified leadA lead that sales has reviewed and accepted as a genuine opportunity to pursue..
- A set of test personas, one for each territory or segment, plus one that matches no rule and one that duplicates an existing contact.
- Access to the CRM, the marketing automation tool and each ad platform's lead form settings.
- The privacy notice and consent wording the forms display.
The checklist
Work through the groups in the order a lead travels. Each test persona is submitted once and followed through every group; a check passes only when the record in the CRM shows the expected result, not when the rule looks right in the settings screen.
Capture
Routing
Scoring and stages
Follow-up
Feedback
Where each check is explained
The widget above keeps the lines short so they can be ticked; the reasoning lives in the guides. Each check links to the page that explains it. Test leads from personal addresses and from subsidiaries are worth adding, since the guide to matching contacts to company records explains why they are the leads most often attached to the wrong account.
| Check | Explained in |
|---|---|
| A test lead from each form and source | Forms that convert |
| Every field maps to the right CRM property | CRM fundamentals for marketers |
| Source and campaign captured with each lead | Connecting CRM to ads and analytics |
| Native ad platform lead forms sync to the CRM | LinkedIn leads not syncing to the CRM |
| Each test lead reaches the right owner | Inbound lead handling playbook |
| Fallback owner for unmatched leads | Inbound lead handling playbook |
| Deduplication against contacts and accounts | CRM fundamentals for marketers |
| Score and lifecycle stage update as the rules say | Lead scoring |
| Hand-off point matches the agreed definition | MQL, SQL and lead stages in B2B |
| Owner alerted when a lead arrives | Sales not following up on marketing leads |
| Acknowledgement that says what happens next | Nurture sequences |
| Leads not ready go to nurture, not sales | Nurture sequences |
| Qualified leads sent back as offline conversions | Connecting CRM to ads and analytics |
| Response times and outcomes reported by source | B2B measurement |
Phone enquiries are leads too, and they need the same checks. The guide to measuring phone calls from Google Ads sets which calls count, records a caller who also fills in a form as one enquiry and sends booked jobs back to the platform once per customer.
If an item fails
Capture and routing failures stop the launch. A lead that reaches the wrong owner, no owner or a duplicate record is a lead that will not be followed up, and the campaign's spend is wasted at the last step. Fix the rule or the mapping, then resubmit every test persona, not only the one that failed: routing rules are evaluated in order, and correcting one often changes which rule catches another. The fallback owner is not optional. If the business cannot agree who receives leads that match no rule, the launch waits until it can, because those are exactly the leads nobody will chase. Once the routes are live, a lead that still reaches the wrong owner is traced with the diagnosis for leads assigned to the wrong salesperson, which reads its owner history against the rules in the order they are evaluated. A website form whose entries do not reach the record system at all is traced stage by stage in the diagnosis of website form submissions not arriving.
Native lead forms fail in their own way: the platform shows the lead, the CRM never receives it. Check the connector's field mapping and its authentication, and do not rely on weekly CSV downloads as a fallback for anything other than a short gap.
Scoring and stage failures can ship with a note only if the hand-off still works. A score that updates a day late is a reporting nuisance; a stage that never changes to the one sales watches is a routing failure and belongs with the group above.
Follow-up failures are usually fixable on the spot. Feedback failures can ship with a date: sending qualified leads back as an offline conversion importUploading outcomes recorded outside the website, such as closed deals, to an ad platform. depends on click identifiers being captured at the form, so check that the capture group stores them even if the import itself is built later. Without them, the import can never be backfilled.
Throughout, keep the privacy side in view: test personas should use invented details, test records should be deleted after the pass, and each source should show the notice and consent wording that covers how the lead's details will be used.
A stairlift installer adds a quote form for a new region
A stairlift installer expands into a new region and adds it to the quote form's region list. Marketing operations submits nine test leads: one for each of its seven regions, one with an unmatched postcode and one duplicating an existing customer. Seven route correctly. The new region's lead lands with the fallback owner, because the territory rule still lists only the old six regions in its picklist, and the duplicate creates a second contact instead of updating the existing one, so the customer would have received a cold sales call about a product already installed in their home. Both are fixed in an afternoon and all nine leads are resubmitted. The form also turns out to drop the click identifier on the thank-you redirect; that is logged with an owner and fixed before the region's first paid search campaign starts a week later.
Common mistakes
- Testing with one lead. One test proves one route. Every territory, segment, the unmatched case and the duplicate case need their own test.
- Reading the rules instead of the records. A routing rule can look correct in the settings and still lose to an earlier rule. Only the resulting CRM record counts.
- No fallback owner. Leads that match no rule sit unassigned, and unassigned leads are invisible to every sales report.
- Forgetting native lead forms. Ad platform forms bypass the website entirely, so a website test says nothing about them.
- Leaving test leads in the CRM. They inflate lead counts, confuse sales and later appear in reports as leads that never converted.
- Skipping the acknowledgement. A lead who hears nothing after submitting often submits again elsewhere, or to a competitor.
The sales and marketing alignment guide covers the agreement these routes depend on, and the checklists library holds the rest of the lists.
