Short answer
Audit WhatConverts by comparing enquiries confirmed in the receiving system with captured records. Separate an absent enquiry from a present record without a source. Test each journey and document the denominator: complete capture of test enquiries does not establish complete measurement of real customers.
Key verification: Match every sampled enquiry by identifier and classify the omission before changing tags.
Sources and limitationsSeeing enquiries in a dashboard does not establish that an installation covers every entry point on a website. A coverage audit asks which confirmed enquiries are missing from WhatConverts and where the journey loses them. Its output is an omission register with an owner, rather than a comparison between total clicks and total leads.
Build a reference independent of the same script
For a form, use the receiving system's acceptance record; for chat, the received conversation; for a call, the relevant telephone log. Clicking submit or a phone link does not establish receipt. Assign test identifiers and avoid customer data in testing. If two dashboards rely on the same tag, both may omit an enquiry while still agreeing.
Define the period, pages, included channels and justified exclusions. A direct call to the usual number, a request on an external portal or a visitor whose consent choice limits measurement may be outside scope. Recording that boundary prevents partial coverage from becoming a universal capture claim.
Separate missing capture from missing source data
The WhatConverts guidance on leads without traffic sources says the script needs to be on both the landing and conversion pages. It suggests checking installation, GTM firing and cached page versions. This diagnoses missing source data; it does not establish that an uncaptured enquiry has the same cause.
Classify the record first. If it exists without a source, investigate attribution continuity. If it does not exist, inspect receipt and the channel's capture mechanism. If it appears twice, investigate duplication. Changing every trigger simultaneously prevents you from identifying which change resolved the problem.
Original journey test matrix
| Proposed test | Independent reference | Verification |
|---|---|---|
| Form from the homepage | Request accepted by the receiver | Record and expected source |
| Form from a landing page | Accepted request with a test ID | Coverage of that template |
| Chat started on mobile | Received conversation | Capture of the actual widget event |
| Call to the displayed number | Telephone test log | Session correspondence where applicable |
Add a row for each template, language and path that changes implementation. Repeat the journey with relevant consent choices and record the conditions; do not force measurement on visitors who reject it. This matrix is a proposed CallsIQ protocol, not a test performed in an account.
Calculate coverage without mixing identities
Fictional example: 12 eligible enquiries are confirmed and 10 corresponding records are found. Sample coverage is 10 / 12 = 83.3%. Of the 10 captured, 2 lack a source: available attribution is 8 / 10 = 80%. These are separate problems. Do not apply that proportion to all traffic to invent missing enquiries.
Match by identifier and authorised context before pairing approximate timestamps. Leave uncertain cases pending. The report needs a numerator, denominator, exclusions and the failing journey; a percentage alone conceals what was actually counted.
Close the incident and decide whether software is needed
After a correction, repeat the same test and confirm both independent receipt and the WhatConverts record. Manual entry may repair a report but does not establish that automatic capture works. Retain the cause and verification so the test can be repeated when forms or templates change.
WhatConverts may fit a need to review enquiries and attribution across supported channels. A manual sample may suffice for a one-off check. Confirm your plan's capture and integration options before extending installation. This guide examines documentation and proposes a method; it does not claim CallsIQ product usage results.
Sources and limitations
Documentary review: . Content type: Documentation-based guide with original resource.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- WhatConverts guidance on leads without traffic sourceswww.whatconverts.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
WhatConvertsAffiliate linkThe labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.