Skip to main content
Revision Date: June 14, 2026 A source is the approved path that sends leads into Leadping. It can represent a website form, partner, publisher, buyer, internal system, CRM, or direct-post integration. Every external lead should be tied to the source that produced it. That source gives Leadping and your team the context needed to validate the submission, route follow-up, review consent evidence, and investigate disputes.

​
What a source controls

A source can control:
  • Whether the source is enabled
  • Whether the source is compliance-approved for production intake
  • Whether TrustedForm is required
  • Which states, products, or verticals are allowed
  • Which tags are applied to new leads by default
  • Cost-per-lead tracking, when used by the account
  • Source credentials used by external posting systems
  • Compliance notes and review context
If a source is disabled, not approved, or outside its configured state or product rules, Leadping may reject or hold submitted leads.

​
Before creating a source

Prepare these details before you connect production traffic:
  • Source name and owner
  • Website, landing page, form, publisher, partner, or system that creates the lead
  • Products, states, audiences, and verticals the source is allowed to send
  • Expected volume and posting schedule
  • Consent language shown to the person submitting the lead
  • TrustedForm certificate URL handling
  • Example lead payload
  • Tags or labels your team needs for routing and reporting
  • Support contact for fixing source issues quickly
The source should match the real intake path. Do not reuse one generic source for unrelated publishers, websites, or campaigns when separate review and traceability would be clearer.

​
Source credentials

External posting systems use source credentials, not a user bearer token. Leadping provides:
CredentialPurpose
sourceIdIdentifies the approved source
apiKeyAuthenticates submissions for that source
Send both credentials as query parameters when posting leads. 
POST https://api.leadping.ai/leads/intake?sourceId=source_123&apiKey=lp_source_key
Content-Type: application/json
Treat the API key as a secret. Use HTTPS, share it only with the posting system that needs it, and rotate it if it is exposed or sent to the wrong party.

​
Approval and launch

A source is not ready for production just because credentials exist. Before launch, confirm:
  • The source is enabled.
  • The source is approved for the intended use.
  • Required TrustedForm handling is working.
  • Allowed states and products match the traffic you plan to send.
  • Default tags and routing context are correct.
  • Test leads appear in Leadping with the expected source and metadata.
  • The first outreach workflow is ready before real leads arrive.
Send a small amount of traffic first and verify the records, conversations, and workflow behavior before increasing volume.

​
When to create a separate source

Use separate sources when leads differ in a way your team may need to review later, such as:
  • Different publishers, partners, or buyers
  • Different websites, landing pages, or consent language
  • Different products, states, or verticals
  • Different pricing or billing arrangements
  • Different routing, tags, or reporting needs
  • Different compliance review outcomes
Separate sources make it easier to pause one path without stopping unrelated traffic.

​
When to update support

Contact support@leadping.ai before continuing production traffic when a source changes materially:
  • New publisher, partner, form, landing page, or posting system
  • New opt-in language or consent path
  • New product, state, vertical, or audience
  • New message copy, call script, link domain, or sender brand
  • Increase in complaints, opt-outs, failed submissions, or source disputes
Source changes can affect carrier registration, TrustedSetup, compliance review, and automation eligibility.