- Who this is for
- The person responsible for form records, integrations, or lead assignment.
- What you will leave with
- A field map, recovery procedure, and reconciliation log.
- Scope of this guide
- An editorial test plan with documentation-based product descriptions. No campaign, conversion uplift, live CRM integration, or customer result is claimed. Test your exact plan and connection.
On this page · 10 sections
01 / Name each state in the handoff
List submitted, captured, received, accepted, assigned, and followed up as distinct states. Decide where evidence of each state is stored and who can inspect it. A webhook can be acknowledged without completing every downstream operation. Do not let a visitor-facing success message become the only evidence that a request reached its destination.
02 / Create a field contract
Document the source label, internal field key, destination field, type, required status, and treatment of blank values. Include source context and optional preferences. Review hidden and static values as carefully as visible fields. A field with the same name in two systems may still represent a different status, date format, or meaning.
03 / Choose the exact connection route
Compare the supported native integration, a documented webhook, or an embedded destination form. Confirm which plan and permissions are needed. Instapage documents differences when using embedded CRM forms, including effects on native lead collection and conversion tracking. Verify your chosen configuration directly rather than assuming an embedded form inherits every platform behavior.
04 / Define identity and duplicates
Agree on the destination’s matching rule and how a repeat request should be handled. Decide whether to add an activity, update permitted fields, or send the item for review. Preserve verified customer information. A duplicate contact may represent a legitimate second inquiry, so deduplicating records should not erase the person’s new request or its source.
05 / Protect the meaning of visitor choices
Keep a request for contact separate from other preferences. Specify how an absent, false, or changed value is transferred and retained. Test both new and existing contacts. Review applicable requirements with the responsible owner before enabling marketing follow-up; this checklist describes data continuity and does not determine the legal basis for your campaign.
06 / Test malformed and unusual data
Try blank optional fields, accented names, long company names, an invalid required value, and a value your CRM rejects. Compare the submitted text with the destination record. Check error details without publishing personal information in logs. Establish a review destination for cases that cannot be transformed safely instead of silently replacing the visitor’s input with a guess.
07 / Make failures visible
Unbounce provides integration-error documentation; use the relevant account view to inspect failed actions. For any route, name the monitoring owner and define the information needed to investigate. Test an intentionally controlled failure in an appropriate environment. Verify what your connection actually retries rather than assuming every action will be repeated automatically.
08 / Recover without duplicating consequences
Document how to find the original submission, check whether part of the workflow succeeded, and rerun only the missing action. A second attempt should not create a second record, notify several owners, or send another acknowledgment unnecessarily. Confirm the recovered destination record and assignment before marking the incident complete.
09 / Reconcile and sample the finished records
Compare source and destination counts using the same time window and identity rule. Investigate every unmatched test item and sample ordinary accepted records for field and owner correctness. Include assignments and follow-up, not only contact creation.
Six marked test submissions produce four new contacts, one activity on an existing contact, and one visible rejected item. The rejected item is repaired and verified; counting only new contacts would have hidden both valid reuse and a failure.
10 / Assign continuity and change control
Record the integration owner, backup owner, field contract, test cases, and recovery steps. Rerun affected cases after changing a form, destination field, credential, or assignment rule. Confirm what happens when the integration owner leaves. A maintainable handoff has an operational owner who can explain the accepted record and repair an exception.
Reconcile source requests with accepted, assigned records. A successful capture is an input to the handoff, not proof of its completion.
Official sources
Unbounce: Field mappingUnbounce: Webhook deliveryUnbounce: Troubleshooting integration errorsInstapage: CRM and lead-management integration routesSource material supports product descriptions; workflow criteria and pilot suggestions are our editorial analysis. Check the current documentation and your account settings before implementation.