How Does Consent Proof Reach the Buyer? The Short Answer
In LeadExec, consent proof travels with the lead as lead type fields. Your lead sources post consent data into those fields, and you then choose which fields go to each buyer in the ping and in the post.
LeadExec lead types can include these consent-related fields:
Field name | Description in the app | Use |
IPAddress | IP Address | The consumer's IP address |
TCPAConsentText | TCPA Consent Text | The consent language the consumer saw |
TCPAContactConsent | TCPA Contact Consent | The consumer's contact consent |
OptIn | Opt In | A Yes/No opt-in value |
TrustedFormToken | TrustedForm Token | TrustedForm data from the lead source |
TrustedFormText | TrustedForm Text | TrustedForm data from the lead source |
JornayaToken | Jornaya Token ID | The Jornaya token from the lead source |
LandingPageURL | LandingPageURL | The page where the lead was captured |
LeadExec has no dedicated consent-timestamp field. If a buyer requires the time of consent, agree with your lead sources and the buyer how it will be supplied.
LeadExec does not send consent evidence to a buyer on its own. How consent evidence is shared with buyers during a ping post sale depends on how you configure each buyer's delivery and on what each buyer's posting instructions ask for.
For the current status of the FCC's one-to-one consent rule, see TCPA One-to-One Consent: Current Status and How LeadExec Handles Consent. That article explains the rule never took effect. This article covers only how proof is passed to buyers in a ping post auction.
This isn't legal advice. Talk with your own lawyer about the consent records your business needs.
Step 1: Add Consent Fields to Your Lead Type
Go to Settings > Lead Types, open the lead type, and review its Fields. Each field has a Name, a Description, a Required setting, and a Type. The consent fields above are Text fields, except Opt In, which is a Yes/No dropdown.
Add any consent field your buyers require that the lead type doesn't have yet, using New Field.
Step 2: Collect Consent Proof From Your Lead Sources
Lead type fields appear in each campaign's Posting Instructions. The Request Parameters table lists every field with its Type, Position, Required setting, and Description, and the sample request (JSON or XML) shows the fields inside a "fields" object.
Consent fields such as JornayaToken, TrustedFormToken, TrustedFormText, TCPAConsentText, and TCPAContactConsent appear as optional body parameters. Tell each lead source which of them you need, so the proof arrives with the lead.
For how to generate and share posting instructions, see How to Generate Posting Instructions.
Capturing Consent on Your Own Forms
If you capture leads on your own landing pages, LeadExec's TCPA consent certification can capture consent with the lead:
In Account Settings > Lead Source Settings > TCPA Options, set Enable TCPA Information Services, then turn on the lead type under Enable Lead Types for use within TCPA. Once a lead type has been enabled and the campaign configured, it will be able to receive TCPA information.
In the campaign's Compliance settings, turn on Enable TCPA Services ("Enable the ability to provide TCPA consent text to 3rd party for internal forms.").
For the full setup, see How to Set Up TCPA Consent Certification in LeadExec.
Verifying TrustedForm Certificates
LeadExec integrates with ActiveProspect TrustedForm. As documented in How to Configure the ActiveProspect TrustedForm Integration, you select the lead field that contains the TrustedForm certificate URL, can compare the lead's email and phone with the certificate, and can reject a lead or send it to Quality Control when it fails your criteria, so it never reaches buyers.
Requiring Proof on Inbound Pings
For pings from lead suppliers, Ping-Post Lead Campaign Advanced Settings documents Field Requirements: the fields a ping must include. These appear in the posting instructions you give the lead source.
Step 3: Map Consent Fields Into Each Buyer's Ping and Post
Buyers receive lead data through the delivery method on their delivery account. For ping post buyers, Ping-Post Field Mappings documents how it works:
The Ping Post Delivery Method has PING and POST Configuration tabs, each with field mappings.
Click Import to bring in the lead fields from your lead type, then rename each field to the name the buyer's posting documentation expects.
Mappings on the Ping tab can also be added to the Post body.
The Post needs the Ping reference field, so the buyer can match the post to its ping.
The ping is an anonymous preview used to collect bids. It leaves out the consumer's name, phone number, and email, which are sent only in the post. If a buyer wants to see consent proof before bidding, include those consent fields in the ping mappings as the buyer's posting instructions require.
For the request format, see Ping-Post Request Body Tab. Run test deliveries to confirm the buyer receives every consent field.
Step 4: Pass Seller-Specific Consent With Return Client Offers
Some buyers want consent for each named seller. In the campaign's Compliance settings, under FCC 1 to 1 Consent, Return Client Offers will "Return the offer information located on the associated delivery account of the selected client." The app explains that this "can be used to force a 1 to 1 delivery by allowing the source to present offers to the end consumer."
Each buyer's offer is set up on the Offer tab of the buyer's delivery account. For the offer fields and how the ping response and post carry offers, see LeadExec Offers Overview: 1-to-1 Compliance | Phase 1 release.
Step 5: Check What Each Buyer Received
Outbound > Outbound PINGs lists pings sent to buyers. Select a row and click View Request / Response to see the data sent to the buyer and the buyer's response.
Inbound > PING Orders lists pings received from your lead sources. See Ping Order List – How to Use This Screen.
For leads captured with LeadExec's TCPA consent certification, How to Set Up TCPA Consent Certification in LeadExec explains how to open the lead's TCPA details and print a certificate.
Consent Records Buyers Commonly Ask For
Lead buyers are responsible for the calls and texts they make. They often ask sellers how consent was captured, which sellers were named, and how to get proof for each lead.
The TCPA status article recommends keeping the consent text, time, IP address, and any certificate with each lead. In LeadExec, the consent text and IP address have their own lead type fields (TCPAConsentText and IPAddress), and certificate data can arrive in fields such as TrustedFormToken, TrustedFormText, or JornayaToken. There is no dedicated field for the time of consent.
For LeadExec's ping post capabilities, see LeadExec ping post software.
Frequently Asked Questions
Does LeadExec send consent proof to buyers automatically?
No. A buyer receives the fields set up in that buyer's delivery. Include the consent fields each buyer's posting instructions require.
Which consent fields does LeadExec support?
Lead types can include IPAddress (IP Address), TCPAConsentText (TCPA Consent Text), TCPAContactConsent (TCPA Contact Consent), OptIn (Opt In), TrustedFormToken (TrustedForm Token), TrustedFormText (TrustedForm Text), JornayaToken (Jornaya Token ID), and LandingPageURL.
Does LeadExec have a consent timestamp field?
No. LeadExec has no dedicated consent-timestamp field. Agree with your lead sources and buyers how the time of consent will be provided.
Can I pass a Jornaya token to a buyer?
Yes, if your lead type has the JornayaToken (Jornaya Token ID) field and your lead source posts it. Include it in the buyer's ping or post mappings using the field name the buyer expects.
Can a buyer see consent proof before bidding on a ping?
Yes, if the consent fields are included in the ping mappings. The ping still leaves out the consumer's name, phone number, and email.
Is seller-by-seller consent required?
Not by the current federal rule. The FCC's one-to-one consent rule never took effect. Some buyers still ask for seller-specific consent as a business practice, and Return Client Offers can support it. See TCPA One-to-One Consent: Current Status and How LeadExec Handles Consent.





