Skip to main content

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
Lead buyers can verify any certificate via API before making a call. Consumers can revoke consent anytime through a self-service opt-out page, and eConsent tracks the FCC’s 10-business-day compliance deadline automatically.

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:
  1. You enable eConsent on your campaign in Pingtree
  2. Pingtree automatically provisions your organization and property with eConsent (no separate signup needed)
  3. The eConsent tracker script is injected into your landing page alongside your Click Script
  4. When a consumer interacts with the form, eConsent captures the session and writes an econsent_session_id to a hidden form field
  5. When the lead is submitted, Pingtree verifies the session against eConsent’s API before accepting the lead
  6. The verification result is stored on the lead record — isEConsentVerified: true means the consent was validated

Enabling eConsent

Campaign-Level Setup

  1. Navigate to your campaign’s Settings > Click Script tab
  2. Toggle eConsent to enabled
  3. 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 the econsent_session_id before accepting leads from that source.
SettingDescription
Enable for Form APIVerify eConsent session on form lead submissions
Enable for Ping APIVerify eConsent session on ping requests
Enable for Post APIVerify eConsent session on post requests
Verification TypeExact Match — the full consent text must match. Partial Match — a partial term match is accepted.
When verification is enabled and a lead arrives without a valid 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
The tracker script is loaded from eConsent’s CDN and requires two identifiers — your Company ID and Property ID — both of which Pingtree manages automatically.

On the Lead Record

After a lead is submitted and verified, the following fields are stored:
FieldDescription
econsent_session_idThe session token generated by the eConsent tracker on the landing page
isEConsentVerifiedtrue if Pingtree successfully verified the session against eConsent’s API
These fields are available in lead detail views, reports, and can be mapped to buyer endpoints via Distribution > Lead Routing so downstream buyers receive the session ID for their own verification.
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:
StructureBehavior
One-to-Many DynamicShows individual buyer cards with “Add” buttons — consumers choose which companies can contact them
One-to-Many SelectedShows a table of buyer options with combined consent language at the bottom
Standard LabelWraps consent text in a label element (compatible with Jornaya’s leadid_tcpa_disclosure field)
Configure your consent structure and language in Campaign Settings > Compliance. You can add individual buyer consent entries, set display order, configure auto-selection behavior, and upload company logos.

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:
  1. The lead record includes an econsent_session_id value
  2. Use eConsent’s verification API to validate the session
  3. The API returns the full consent certificate including session replay, disclosure text, listed companies, and cryptographic signature
This gives you an independent, tamper-proof record of consent that holds up in TCPA disputes.

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

ScenarioHow eConsent Helps
Insurance lead generationProve the consumer saw and agreed to be contacted by specific carriers before any calls are made
Financial servicesMaintain auditable consent records for TCPA-regulated outbound calling
Solar / home servicesCapture consent across multi-step funnels where disclosure text changes per page
Lead marketplaceGive buyers confidence that every lead has verified, tamper-proof consent — reducing TCPA exposure
Dispute resolutionProduce session replays and signed certificates as evidence if a TCPA claim is filed