What is eConsent?
eConsent is a TCPA consent verification platform built for lead generation. When a consumer fills out a form — requesting an insurance quote, signing up for solar, applying for a loan — eConsent records the entire session, captures the consent language they were shown, and generates a signed certificate proving they agreed to be contacted. This matters because if a TCPA lawsuit arises, the certificate includes:- A full session replay of exactly what the consumer saw and did
- The exact disclosure text that was displayed at the time of consent
- Which companies were listed in the consent language
- A cryptographic signature proving nothing was tampered with after the fact
How It Works in Pingtree
Pingtree has a built-in integration with eConsent. When enabled, a single line of JavaScript on your landing page handles everything — session recording, consent extraction, and certificate generation. No backend integration is required from the publisher. Here’s the flow:- You enable eConsent on your campaign in Pingtree
- Pingtree automatically provisions your organization and property with eConsent (no separate signup needed)
- The eConsent tracker script is injected into your landing page alongside your Click Script
- When a consumer interacts with the form, eConsent captures the session and writes an
econsent_session_idto a hidden form field - When the lead is submitted, Pingtree verifies the session against eConsent’s API before accepting the lead
- The verification result is stored on the lead record —
isEConsentVerified: truemeans the consent was validated
Enabling eConsent
Campaign-Level Setup
- Navigate to your campaign’s Settings > Click Script tab
- Toggle eConsent to enabled
- Pingtree automatically handles the rest:
- Creates your organization in eConsent using your account details
- Creates a property linked to your campaign’s production domain
- Stores the returned Company ID and Property ID on the campaign
Tip: You do not need to create a separate eConsent account. Pingtree provisions everything automatically when you flip the toggle.
Source-Level Verification
Once eConsent is enabled at the campaign level, you can configure verification behavior per source. This controls whether Pingtree validates theeconsent_session_id before accepting leads from that source.
| Setting | Description |
|---|---|
| Enable for Form API | Verify eConsent session on form lead submissions |
| Enable for Ping API | Verify eConsent session on ping requests |
| Enable for Post API | Verify eConsent session on post requests |
| Verification Type | Exact Match — the full consent text must match. Partial Match — a partial term match is accepted. |
econsent_session_id, or the session fails verification, the lead is rejected with a 400 error before distribution begins.
What Gets Captured
On the Landing Page
The eConsent tracker script runs in the consumer’s browser and captures:- The consumer’s interaction with the form (clicks, scrolling, typing behavior)
- The TCPA consent language displayed on the page
- Which buyers/companies were listed in the consent disclosure
- A session token (
econsent_session_id) that uniquely identifies this consent event
On the Lead Record
After a lead is submitted and verified, the following fields are stored:| Field | Description |
|---|---|
econsent_session_id | The session token generated by the eConsent tracker on the landing page |
isEConsentVerified | true if Pingtree successfully verified the session against eConsent’s API |
Consent Language and Buyer Display
Pingtree’s consent system works alongside eConsent to display dynamic, buyer-specific TCPA consent language on your landing pages. This is handled by the Pingtree Consent Script (pingtree-consent.js), which is separate from the eConsent tracker but works in tandem.
The consent script supports three display structures:
| Structure | Behavior |
|---|---|
| One-to-Many Dynamic | Shows individual buyer cards with “Add” buttons — consumers choose which companies can contact them |
| One-to-Many Selected | Shows a table of buyer options with combined consent language at the bottom |
| Standard Label | Wraps consent text in a label element (compatible with Jornaya’s leadid_tcpa_disclosure field) |
Verification API
When a lead is submitted, Pingtree calls eConsent’s verification API before accepting the lead into the distribution pipeline.Exact Match Verification
Sends the full consent text along with the session ID. eConsent confirms that the consent language recorded in the session matches exactly.Partial Match Verification
Sends a search term along with the session ID. eConsent confirms that the term appears within the recorded consent language. Useful when consent language varies slightly across form versions. If verification fails, the lead is rejected immediately — it never reaches your buyers.For Lead Buyers
If you’re a lead buyer receiving leads from a Pingtree campaign with eConsent enabled, you can independently verify any lead’s consent before making a call:- The lead record includes an
econsent_session_idvalue - Use eConsent’s verification API to validate the session
- The API returns the full consent certificate including session replay, disclosure text, listed companies, and cryptographic signature
Consumer Opt-Out
eConsent provides a self-service opt-out page where consumers can revoke their consent at any time. When a consumer opts out:- The consent certificate is updated to reflect the revocation
- eConsent tracks the FCC’s 10-business-day compliance deadline automatically
- Webhooks can notify your systems of revocation events in real time
Use Cases
| Scenario | How eConsent Helps |
|---|---|
| Insurance lead generation | Prove the consumer saw and agreed to be contacted by specific carriers before any calls are made |
| Financial services | Maintain auditable consent records for TCPA-regulated outbound calling |
| Solar / home services | Capture consent across multi-step funnels where disclosure text changes per page |
| Lead marketplace | Give buyers confidence that every lead has verified, tamper-proof consent — reducing TCPA exposure |
| Dispute resolution | Produce session replays and signed certificates as evidence if a TCPA claim is filed |
Related Resources
- Compliance Settings — configure TCPA consent language and buyer display
- TrustedForm Integration — alternative consent certification via ActiveProspect
- Jornaya Integration — LeadID-based consent tracking
- eConsent — official eConsent platform for TCPA consent verification
- Live Support — get help setting up eConsent for your campaigns