Partner Certificates & Lead Distribution

What are Partner Certificates?

When you sell leads to another company, that buyer needs proof that the consumer consented to be contacted. Without proof, they’re exposed to TCPA lawsuits.

Partner Certificates solve this by letting publishers share consent certificates directly with lead buyers through eConsent. The buyer gets cryptographic proof of consent — the same certificate the publisher generated — with a full chain of custody showing when it was shared and claimed.

No more emailing screenshots or trusting a publisher’s word. The consent evidence travels with the lead.

For Publishers (Sharing Certificates)

Adding a Distribution Partner

If you regularly sell leads to the same buyer, add them as a distribution partner on your property:

  1. Go to your Property Settings
  2. Scroll to the Distribution Partners section
  3. Click Add Partner
  4. Enter the buyer’s eConsent company ID or email
  5. Choose an access level:
    • Read — Buyer can view certificates you share with them
    • Claim — Buyer can claim certificates and add them to their own account
  6. Optionally enable Auto-share if every lead from this property goes to this buyer

Sharing Individual Certificates

When you sell a specific lead:

  1. Go to the certificate for that session
  2. Click Share and select the buyer (or leave blank for an open claim token)
  3. You’ll receive a claim token (e.g., clm_a1b2c3d4...) and a claim URL
  4. Pass the claim token to your buyer alongside the lead data — via your existing ping/post, API, email, or however you deliver leads

Auto-Sharing

If you enable auto-share for a partner on a property, every certificate generated on that property is automatically visible to that buyer. This is ideal for exclusive partnerships where all leads go to one buyer.

For Buyers (Receiving Certificates)

Accessing the Partner Certificates Dashboard

  1. Log into eConsent
  2. Click Partner Certificates in the sidebar
  3. You’ll see all certificates that publishers have shared with you
  4. Each certificate shows: publisher name, consent capture date, consumer state, compliance score, and status

Claiming a Certificate

When a publisher sends you a claim token with a lead:

  1. Visit the claim URL (e.g., app.econsent.org/certificate-sharing/certificates/claim/clm_xxx)
  2. You’ll see a preview: when consent was captured, which publisher, and whether a recording exists
  3. Click Claim to add it to your account
  4. The certificate is now permanently in your Partner Certificates dashboard

You can also claim via the API for automated workflows.

Understanding the Compliance Score

When you claim a certificate, eConsent automatically validates the consent language against your configured rules:

  • 100% — Compliant (green) — All required phrases found in the consent language
  • 75-99% — Partial (amber) — Some required phrases missing
  • Below 75% — Non-compliant (red) — Most required phrases missing
  • Not checked (gray) — No consent rules configured

Viewing the Evidence Package

Click View Evidence on any claimed certificate to see:

  • The exact consent language the consumer saw
  • HMAC-SHA256 signature proving the certificate hasn’t been tampered with
  • Timestamp of when consent was captured
  • Consumer’s state (from IP geolocation) for state-level compliance
  • Link to the session replay showing the consumer’s interaction
  • Full chain of custody: when the certificate was created, shared, and claimed

As a lead buyer, you can define what consent language your publishers must include on their forms.

Creating a Rule with Individual Phrases

  1. Go to Partner Certificates → Manage consent rules
  2. Click Create Rule
  3. Select Individual Phrases mode
  4. Enter your rule name (e.g., “TCPA Express Consent”)
  5. Type each required phrase and press Enter:
    • Your company name (e.g., “Acme Insurance”)
    • “autodialer” or “automatic telephone dialing system”
    • “consent is not required as a condition of purchase”
  6. Choose a mode: Warn (flag for review) or Reject (auto-reject)
  7. Click Save Rule

Each phrase is checked independently. The certificate must contain ALL phrases to get a 100% compliance score.

Creating a Rule with Full Consent Text

If your legal team has a specific consent paragraph they require:

  1. Click Create Rule
  2. Select Full Consent Text mode
  3. Paste your entire required consent language into the text area
  4. eConsent will break it into sentences and validate each one
  5. Choose Warn or Reject mode
  6. Click Save Rule

Warn vs Reject Mode

  • Warn — Certificates that don’t match get flagged with an amber badge, but you can still claim and use them. Use this when you want visibility into compliance gaps without blocking leads.
  • Reject — Certificates that don’t match are automatically rejected. Use this when compliance is mandatory and you don’t want non-compliant leads entering your system.

Frequently Asked Questions

Can I see ALL certificates from a publisher? No. You only see certificates that a publisher has explicitly shared with you, either individually or via auto-share. This protects the publisher’s other leads and buyers.

How long do claim tokens last? 90 days from creation. After that, the token expires and the publisher would need to generate a new one.

Can I unclaim a certificate? No. Claims are permanent — this is by design for the audit trail. If you claimed a certificate, that claim is part of the chain of custody record.

Is the consent language validation legal advice? No. eConsent’s compliance checks are automated text-matching tools. They do not constitute legal advice or guarantee regulatory compliance. Always consult your legal team for TCPA compliance decisions.

What’s the chain of custody? Every action on a certificate is logged: when it was created, signed, shared, claimed, and viewed. This immutable audit trail is critical evidence in TCPA litigation — it proves when you obtained consent proof and from whom.

Can I use the API instead of the dashboard? Yes. All Partner Certificate operations are available via REST API. See the developer documentation for endpoint details, request/response formats, and code examples.

Does this work with eConsent Voice and SMS? Partner Certificates are currently for eConsent Web certificates (form-based consent). Voice and SMS certificates have their own verification URLs that can be shared directly.

Did this answer your question?

Back to Help Center
See eConsent in action. Schedule a live demo
Schedule a demo