Skip to main content
A source tells Leadping where a lead came from and which rules apply to it. It might represent your website form, a specific partner, a publisher, a CRM, or an internal posting system. Every external lead should arrive through the source that actually produced it—not a catch-all source created for convenience.
The workflow: define the source here, connect its consent evidence, then use its source key to send leads to Leadping.

​
The rule for creating sources

Use one source when leads share the same:
  • form, website, publisher, or posting system;
  • consent language and evidence path;
  • product, states, audience, and sender;
  • routing and operational treatment; and
  • review, reporting, and billing context.
Create separate sources when any of those differences matter. This lets your team approve, pause, route, investigate, or report on one intake path without affecting unrelated traffic.
Name a source so a new teammate could identify it six months from now. “Acme Solar — Quote Form” is more useful than “Website Leads.”

​
What a source controls

Leadping may reject or hold a submission when its source is disabled, unapproved, missing required evidence, or outside the configured state or product rules.

​
Before you create one

Have the real intake path in front of you. Gather:
  • the source owner and a useful name;
  • the form, landing page, publisher, partner, CRM, or system;
  • products, states, audiences, and expected volume;
  • the exact consent language shown to the person;
  • how the TrustedForm certificate URL will be captured and posted;
  • a representative payload; and
  • tags needed for routing or reporting.
Do not connect production traffic until the source configuration describes what will actually be sent.

​
Source credentials

Each external posting system authenticates with a source key:
An lp_src_... key is valid only for approved lead-ingestion routes. It is not a user token, business API key, or general-purpose integration credential. Store it in the posting system’s secret configuration, send it only over HTTPS, and rotate it if it is exposed. Use different keys for sources that should be independently traceable or revocable.

​
Test the real path

Before increasing traffic:
  1. Confirm the source is enabled and approved.
  2. Post a test lead from the real system—not a hand-built request that bypasses it.
  3. Verify the source, product, state, tags, and TrustedForm URL on the Leadping record.
  4. Check that routing, automations, inbox views, and reporting behave correctly.
  5. Make sure the source owner can see failed posts and act on them.
Start with a small production volume and watch the resulting records and conversations before scaling.

​
When a source changes

A meaningful source change can affect consent review, phone-number readiness, carrier registration, and automation eligibility. Contact support@leadping.ai before continuing traffic after a change to the publisher, form, landing page, consent language, product, state, audience, sender, first message, call purpose, or link domain. Also contact support if complaints, opt-outs, failed posts, or source disputes increase.

Add consent evidence

Capture and post the TrustedForm certificate for each lead.

Send the first lead

Choose an endpoint, build the payload, and test the real integration.