Link valid submissions to CRM outcomes
Count the new valid request and its qualified opportunity separately, retain the repeat submission and exclude the identified internal test from buyer totals. Keep an unknown source visible. Joining request and CRM identities explains the pipeline stages without treating every submission or person as a new qualified opportunity.
Worked example — illustrative data.
| Submission | CRM outcome | Counting decision |
|---|---|---|
| D101: new buyer | Qualified opportunity Q41 | One valid request and one qualified outcome |
| D102: repeat from D101 | Same opportunity Q41 | Keep repeat; do not create a second opportunity |
| D103: test address | Marked internal test | Exclude from buyer conversion totals |
| D104: valid, source unknown | Awaiting review | Retain valid request and unknown attribution |
Define qualification with the sales owner before reporting it. Use an approved request or account identifier to join stages, while keeping personal information out of analytics payloads. Record first submission, repeat activity, qualification date and attribution basis separately. A later CRM update should not silently change the meaning of the original form count. Reconcile a small sample manually before relying on an aggregate dashboard.
Keep request identity separate from opportunity identity
Retain D101 and the repeat D102 as two submissions linked to the same opportunity Q41 under the example’s rule. Record valid new requests, repeats, tests and pending review in separate fields. When another person from the same company enquires, let sales determine the account and opportunity relationship rather than deduplicating by email domain alone.
Decision: Report request volume and qualified opportunity volume alongside the unresolved rows. Treat attribution as an assigned reporting rule rather than proof that the landing page caused the deal.
Several contacts at one account may share an opportunity: Several people from the same account can submit legitimate requests. Do not deduplicate solely by email domain or count each person as a separate opportunity without the sales definition.
Can a form submission be reported as pipeline immediately?
Use the agreed sales definition and an actual linked opportunity record. A request received, a qualified request and a sales opportunity are different states. Show pending and unlinked records instead of assuming each submission became pipeline.
Continue with Guides for stores, software teams and local businesses, Conversion tracking for orders and qualified leads and Choose a conversion rate baseline you can use.