Require TrustedForm for External Leads

Every external lead sent to Leadping requires its own TrustedForm certificate URL.

A missing certificate URL causes the intake request to fail. Capture the certificate on the form and preserve it through every handoff before submitting the lead.

Add the certificate field

Endpoint	Required field
`POST /leads`	`metadata.trustedFormUrl`
`POST /leads/intake`	`trustedFormUrl`

Structured request

{
  "metadata": {
    "trustedFormUrl": "https://cert.trustedform.com/example"
  },
  "contact": {
    "firstName": "Jordan",
    "phone": {
      "number": "+15555550123"
    }
  },
  "customer": {},
  "tagIds": [],
  "tagNames": []
}

Flat request

{
  "firstName": "Jordan",
  "phone": "+15555550123",
  "trustedFormUrl": "https://cert.trustedform.com/example"
}

Leadping does not provide a GET or query-string intake endpoint.

Understand the result

Certificate handling has two customer-visible stages:

Result	Meaning	Next action
`400 Bad Request` for a missing certificate	Intake did not create the lead	Correct the mapping before sending again
`201 Created`, lead still processing	The record exists; verification is not finished	Keep the lead ID and inspect its processing status
Ready	Lead processing completed	Check the intended workflow separately
Invalid	The lead did not pass validation	Read the processing reason and correct the source of the problem

An accepted request is not evidence that the certificate matches the person, sender, or intended outreach. Your team must be able to explain that relationship from the original submission and its consent records.

Trace a certificate through the integration

Install TrustedForm on the actual form where the person submits their information, following ActiveProspect’s setup guide.
Complete a controlled submission and confirm that it produces a certificate URL.
Inspect the form-to-backend handoff. Confirm that the URL travels with the same contact and upstream record ID.
Check each CRM, partner, or middleware mapping. A generic URL field can accidentally contain the landing-page address instead of the certificate.
Inspect the final Leadping record and compare its certificate with the original submission.

If the form does not produce a certificate, fix capture at the form. If the certificate exists there but is absent from Leadping, locate the first handoff that drops or replaces it. Do not create a new certificate for an old submission or reuse one from another person.

Integration requirements

Capture a unique certificate for each lead at the opt-in form.
Carry the complete URL through every form, webhook, CRM, and posting step.
Do not substitute a landing page, screenshot, consent timestamp, or internal ID.
Keep retries associated with the same lead and certificate.
Confirm a production-path test reaches Ready in Leadping.

TrustedForm records the opt-in event. It does not override an opt-out, correct inadequate consent language, or make an otherwise unlawful contact permissible.

Troubleshoot validation

Result	Cause	Correction
Intake returns `400`	Certificate field is missing	Restore the field mapping before retrying
Lead becomes Invalid	URL is malformed or incomplete	Submit the complete certificate URL
Lead becomes Invalid	A landing page or unrelated URL was supplied	Use the certificate issued for the original submission
Lead becomes Invalid	Certificate URL cannot be reached successfully	Check certificate capture and availability
Wrong certificate appears	A handoff reused or replaced the value	Preserve the certificate associated with that lead

Fix the underlying integration before sending more traffic.

Retention

Storing a URL in Leadping is not the same as retaining the certificate with ActiveProspect. Assign an owner for retention and verify that the retained certificate can be retrieved from the responsible account. Expiration depends on certificate and account conditions. Use ActiveProspect’s expiration and retention guidance to configure retention rather than assuming one default window covers every lead. Keep the related form disclosure, submission timestamp, and source record as well as the certificate.

Configure the source

Create the intake identity and obtain its source key.

Send leads

Build requests and handle processing results.

Start Here

Build Your Workflow

Prepare for Production

Build with Leadping

Security & Trust

Policies & Legal

Require TrustedForm for External Leads

Add the certificate field

Structured request

Flat request

Understand the result

Trace a certificate through the integration

Integration requirements

Troubleshoot validation

Retention

Configure the source

Send leads

​Add the certificate field

​Structured request

​Flat request

​Understand the result

​Trace a certificate through the integration

​Integration requirements

​Troubleshoot validation

​Retention

Configure the source

Send leads

Add the certificate field

Structured request

Flat request

Understand the result

Trace a certificate through the integration

Integration requirements

Troubleshoot validation

Retention