Why aren't website leads showing up in the CRM?
Website leads may disappear before the CRM because a form never reaches its server, a notification is filtered, a webhook points to an old endpoint, credentials expire, field validation rejects the record or duplicate handling places it somewhere unexpected. A lead can also arrive in the CRM but enter the wrong pipeline, remain unassigned or receive no follow-up.
The useful first question is not “Is the CRM broken?” It is “What is the last handoff we can prove?” Start there and verify the next stage independently.
How forms normally reach a CRM
A browser sends the form to a website or form provider. That system validates and accepts the request, then may store an entry, send an email, invoke a webhook or call a CRM API. The CRM validates the payload, creates or updates a record, applies duplicate rules, selects a pipeline or queue, assigns an owner and may create a task or notification.
Each arrow is a separate condition. A thank-you message proves only that the browser received the expected response. It does not prove an email arrived, a webhook succeeded, a CRM record exists or a person saw it.
How to test whether a form reaches the CRM
- Submit one controlled, clearly labeled test through the same public path a prospect uses.
- Record the time and the non-sensitive marker used for the test.
- Confirm the receiving form system accepted or stored it.
- Check the intended notification or webhook log instead of relying on the success screen.
- Find the exact CRM record, including duplicate or approval areas.
- Confirm the expected pipeline, queue and owner.
- Confirm a follow-up task exists and the responsible person can see it.
- After a repair, repeat the original path before calling recovery Verified.
For a focused procedure, use the end-to-end contact form test. If the form submits but email does not arrive, use the notification troubleshooting guide.
Common CRM ingestion failures
- Expired credentials or an integration connected to the wrong account.
- Required fields missing, renamed or sent in an invalid format.
- Duplicate rules updating an older contact instead of creating a visible lead.
- Approval, spam or validation queues hiding rejected records.
- Webhook timeouts, disabled automation or an obsolete endpoint.
- Source fields sent successfully while ownership fields are blank.
Provider behavior varies. For example, Zoho CRM's official webform troubleshooting documentation directs administrators to check unique, duplicate and invalid-entry approval views, and notes that workflow rules can depend on approval and field criteria. Treat that as a Zoho-specific example, not a rule for every CRM.
Lead routing, assignment and ownership
Routing selects the destination; assignment names the accountable person. A small business may need only a shared intake queue plus one backup owner. A larger business may route by location, service, territory, language or availability. Complexity is optional; explicit ownership is not.
Common failures include inactive employees, stale territory mappings, wrong-field criteria, round-robin pools that still contain unavailable people, rules that never match, duplicates bypassing automation and records created without a follow-up task. Salesforce's official assignment-rule guide illustrates that rule order, matching conditions and assigned user are separate configuration decisions.
Read the deeper guide to lead routing, assignment and queue ownership.
How do I know whether sales received a lead?
A CRM record alone is not enough. Confirm that the record is visible in the salesperson's actual queue, has the correct owner, contains a due follow-up task or equivalent next step, and shows an acknowledged human action. “Assigned” is a system state; “acted on” requires separate evidence.
Map first, troubleshoot second
The Lead Tracking & Revenue Path Map names the full system from source to outcome. This troubleshooter is for a suspected break inside that mapped path. Use the map when ownership and destinations are unclear; use this diagnostic when you know the intended path and need an ordered verification sequence.
Wave 3: phone economics
When the uncertain handoff is a customer call, use the Missed Call Revenue Calculator to estimate the opportunity represented by missed calls. Keep mapping and delivery diagnosis separate from the estimate.
Keep marketing source attached to the outcome
When the lead arrives but its campaign history is missing or unreliable, use the UTM-to-CRM Attribution Audit. It checks whether the original marketing source stays attached to the lead and sale without replacing this lead-delivery check.
Frequently asked questions
Does this tool test my CRM?
No. It runs locally in the browser and prioritizes manual checks from your selections. It makes no request to your website, form provider, mailbox or CRM.
Why do form submissions disappear?
They may be rejected before storage, delivered to the wrong destination, filtered as spam, rejected by integration validation, merged as duplicates, routed incorrectly or left without an owner.
What is the first thing to check?
Find the last stage supported by direct evidence, then test the next handoff. If all you know is that a confirmation appeared, verify server-side acceptance before investigating the CRM.
Can AvertSignal replace my CRM or sales process?
No. AvertSignal is an independent protection layer around the tools and people already responsible for the customer path.