Short answer
Valid form attribution preserves a submission accepted by the website and its relationship to the visit. Configure WhatConverts capture and test the source, fields and duplicates; clicking submit is not equivalent to a recorded lead.
Key verification: Test accepted submission, error, iframe and replay from a known source.
Sources and limitationsTo attribute forms with WhatConverts, configure the form you want to measure, perform a test send from an identified visit, and check the received record along with its origin. The success criterion is a submission accepted by the website and captured with the expected data. A click on the submit button is not enough to validate it.
This guide expands the measurement of a company that receives both telephone and written inquiries. Keep each interaction with its identifier and relate those that belong to the same opportunity. A form followed by a call can represent a single purchasing process.
Identify the form and how it confirms submission
Before installing tracking, complete a submission on your test website. Look at what confirms that the request has arrived: success message, thank you page, or entry in the receiving system. Repeat with an invalid field to identify the error path.
| Inventory data | Question resolved by |
|---|---|
| Page and form name | Which request will be measured? |
| Supplier or component | Who controls the submission? |
| Valid Confirmation | How do you know the query was received? |
| Required fields | What information should arrive and what should be excluded? |
| Identifier or reference | How will you relate the receipt and the tracking record? |
WhatConverts documents detection with Form Finder and manual configuration using form attributes. For forms in an iframe, your code must also be inside the iframe; installing it only on the main page does not detect that sending. Compatibility and limits of form tracking .
If the form belongs to a third party and you cannot add code to its environment, check compatibility before contracting for tracking. Just because the form is visible on your website does not mean that you can implement its interior.
Configure the form you really need
- Check the WhatConverts project and the code installed on the page.
- Select the form with the appropriate configuration method.
- Check which fields are to be collected.
- Save the configuration and prepares an identified test visit.
- Check a valid request and a rejected one for validation.
The manual configuration guide is for reviewing that method when automatic detection does not apply to your form. Preserves the name and attribute used to repeat the check after a design change.
The form may contain identifying data. Select the fields necessary for the approved purpose and check the treatment of free text, passwords or sensitive information. Marketing capture does not justify indiscriminately copying all the fields on a page.
Test a known source without inventing a real campaign
Use a test visit identified according to the tool options. An example of internal nomenclature could be source “test”, medium “control” and campaign “budget_form”. These are fictional diagnostic labels and should be excluded from the business report.
The official WhatConverts startup journey allows you to select the form and source, submit a test, and open the lead to review attribution. Guided follow-up test .
Compare three pieces of evidence: what the visitor saw, what the forms system received, and what WhatConverts recorded. The check is incomplete if you only find one of them. An unknown origin should be kept as such until you have evidence to correct it.
A test matrix for your website
| Test | Expected result of your configuration |
|---|---|
| Valid submission from identified visit | A request received and a record with the expected origin |
| Validation error | No accepted query counted as a valid sale or lead |
| Reload after confirmation | Do not count the same request again |
| Mobile or drop-down form | Same fields and acceptance criteria |
| Form within an iframe | Compatibility checked in the environment containing the form |
| Visit without identifiable source | The report shows the available information, without assigning an assumed source |
The matrix is an original protocol, not a claim that all such situations are resolved automatically. If a test fails, revise the method or ask the vendor for a configuration compatible with your component.
Separate submissions, people and opportunities
Fictional example: a person sends a quote, calls the next day and writes again to attach information. You have three interactions. Depending on your process, they may pertain to a single opportunity and a single subsequent sale.
A shared reference makes review easier. Avoid merging contacts based on a single phone match, because it may be an office number. If duplicate records already exist, use the Identity Review procedure in the CRM .
Retests after changing the form, consent component, or confirmation page. Keep the file with date and version. This way you will know if the monitoring continues measuring requests actually received.
Sources and limitations
Documentary review: . Content type: Documentation-based procedure.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- Compatibility and limits of form trackingwww.whatconverts.com
- manual configuration guidewww.whatconverts.com
- Guided follow-up testwww.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.