A success message on a WordPress form does not prove that the lead reached your CRM. Trace one controlled submission from the stored entry through the integration response to the final CRM record. Diagnose the first missing checkpoint instead of replaying every lead.
Create a traceable test without customer data
Use a permitted test address and a distinctive label such as TEST-CRM-0925. Record the form ID, entry ID, submission time, destination account, and expected CRM object. A contact, company, deal, and activity are not interchangeable success criteria.
Check whether the entry exists locally. If it does not, investigate the form first. If an email notification arrived but the CRM record did not, keep those workflows separate: the email can succeed while an integration feed never runs. The form-email diagnosis addresses the former, not proof of CRM delivery.
Confirm that the integration was meant to run
Check the feed or automation's enabled state and conditions against the saved entry. Verify its destination account and environment. A staging form may intentionally point to a test workspace. A conditional rule may skip incomplete, unqualified, or non-consenting submissions by design.
For Gravity Forms, the official webhook submission guidance provides the integration model. Do not assume another form builder uses the same event timing, retries, or mapping controls. Read the installed connector's contract before changing it.
Explanatory worksheet for your own test evidence. No customer results are represented.
Inspect the response, not only the HTTP code
| Checkpoint |
Evidence to keep |
What can still be wrong |
| Entry saved |
Local entry ID |
Feed condition did not match |
| Feed attempted |
Redacted attempt ID and time |
Wrong account or endpoint |
| API returned |
Status and safe response fields |
Validation error or asynchronous job not finished |
| CRM record found |
Record ID and object type |
Merge, assignment, or lifecycle automation differs |
A 2xx response can mean accepted for processing rather than a finished record, depending on the destination API. An error body can identify an invalid required field, expired authorization, unsupported enum value, or duplicate policy. Retain the useful error code without logging access tokens or complete personal-data payloads.
Audit the fields that decide acceptance
Compare required CRM fields with the actual submitted values. Check empty conditional fields, dropdown option values versus labels, date formats, and country or state identifiers. A visible label can look correct while the API expects a different internal value.
Next inspect identity. Search the CRM for the controlled address across merged, archived, or existing records if your permissions allow it. Some integrations update a contact instead of creating a new one. Check the relevant activity history and assignment rules before declaring the lead lost.
Attribution fields need their own acceptance test. Preserve only the identifiers and campaign data that the site's consent and privacy design permits. A successfully created contact with missing source information is an attribution defect, not a missing-record defect. Keep those outcomes separately in the test worksheet.
Retry with duplicate protection
Determine whether the original attempt created anything before retrying. Follow the connector's supported retry mechanism and the destination's idempotency or upsert rules. Do not invent an idempotency header and assume the server honors it. Limit the first replay to the controlled entry and observe downstream notifications or workflows.
For a backlog, reconcile attempted entry IDs against destination record IDs and obtain approval for the exact replay set. Unrestricted resubmission can generate duplicate deals, sales tasks, or customer messages even when contacts are deduplicated.
Define the finished business result
Confirm the record exists in the intended account, required fields survived, the correct team owns it, and permitted attribution is present. Prove one normal new submission works after the fix. HandL WP integration repair can help when the form, connector, and CRM owners have conflicting evidence. Bring checkpoint IDs and redacted responses, not an export of every customer's information.
References checked September 25, 2026. Illustrations and examples are explanatory, not customer case studies.