Prepare identifiable test data
Use a clearly labelled fictional contact and an example-domain email. Record the test time and source form. Prefer a test destination where possible and understand whether submitting the form triggers other systems. Avoid using another person’s real details simply to see whether the integration works.
Check field mapping
Compare the resulting name, email, and phone with the submitted values. Include optional blanks and an international phone format. A form’s visible label may differ from its payload key, so similar wording is not proof that fields will map correctly. Inspect the actual result before expanding testing.
Understand timing and failures
Determine whether processing is immediate or queued. If the lead does not appear, check delivery feedback and configuration before submitting again. A timeout does not always mean the destination failed to save the record. Repeated tests without reconciliation can create duplicates that obscure the original issue.
Review the operational result
Confirm where teammates see the new lead and what happens next. Remove or clearly retain the test record according to your testing process. Repeat the check after form, credential, or provider changes. This is a testing method, not a claim that every provider connection has been independently certified.
Continue reading
Guide / Integrations
Webhook or CSV import: which fits your lead workflow?
Choose a transfer method around timing, review needs, and the ability to handle failures.
Read the guide →Guide / Lead data
How to prepare a lead spreadsheet for CSV import
A practical guide to cleaning names, email addresses, and phone numbers before importing a lead spreadsheet.
Read the guide →Guide / Follow-up
A practical lead follow-up routine for small teams
Build a repeatable daily process for reviewing enquiries, preparing useful replies, and recording next steps.
Read the guide → Browse all guides →