What is 1-to-1?
1-to-1 consent is an FCC ruling that requires telemarketing businesses to get explicit, individual consent from consumers for each specific company contacting them. This means consumers must opt-in separately for each business, making blanket consents that cover multiple entities invalid. The ruling ensures that consumers have clear control over who can call or text them and is effective January 27, 2025. This standard raises compliance requirements across telemarketing practices in the U.S.
How does LeadExec work with 1-to-1
LeadExec provides 1-to-1 capabilities through the offers feature. Offers are set on the client level and can be either static or dynamic. They allow the system to post the required client TCPA information back to lead sources in the response when using the V2 lead receiver. Based on the consumer's selection, LeadExec will match the leads to the clients whose offers are returned in the post. The following sections provide more details on offers and how the functionality works throughout the system.
Lead Receiver
The v2 lead receiver allows LeadExec to pass back client offer details in the response to the lead source. Two channel-type settings can be used for campaigns using offers: ping-post and post. In most cases, ping-post will be the best option when using offers.
There are a few details to be aware of when using the V2 lead receiver.
API Keys are required for posting to the V2 lead receiver. API keys work independently from the API authentication that uses client ID and client secret.
All posts must be in either JSON or XML formats. URL Encoded strings are not available for use with the V2 lead receiver.
Documentation of the V2 lead receiver can be found through the link below:
Ping Response Update:
The ping response will include an "offers" array detailing each offer, including TCPA requirements.
Each offer will contain a name, buyer, description, offer amount, duration, redirect URL, and properties.
Post Request Update:
Includes an "offer" block within the lead properties to specify which offer was selected and whether TCPA consent was accepted.
Lead Source Settings
API Key Settings
API keys that work with the V2 lead receiver are generated on the lead source level. To create an API Key for a lead source, navigate to the lead source details page and select the Acess Keys button in the top menu. Here you can create new API keys for the vendor, which can be used with each of the source's campaigns. To note: API keys are not required for the legacy lead receiver.
Campaign Settings
To enable 1-to-1 to have your campaign work with offers, navigate to the Compliance tab of the campaign settings window and enable return client offers.
Client Settings
New UI for Offer Management:
Offers are managed on the offer tab in delivery accounts. There are two offer types available: static and dynamic. Both offer types have the same fields available for use. You can think of these as offer system fields, as they work in conjunction with the request posted back to your lead sources.
There are specific use cases for each of the offer types. Static offers are used for clients who are the end buyers, and the company will contact the lead directly. Dynamic offers are used for clients who resell leads to the end buyer. Using dynamic offers requires an outbound ping-post delivery configuration.
Static Offer Settings
Static offers are intended for clients who receive direct posts at a predetermined price set on the delivery account. Set the client's details in the static offers settings. The following fields are available for use.
Company Name: Name of the company buying the lead and who will work the lead.
Company Phone Number: Business phone number.
Name: Offer Name
Description: Details of the offer.
URL: Company website URL.
Image URL: Link to company logo.
Privacy URL: Link to company privacy policy.
Terms URL: Link to company terms and conditions.
Duration: Setting for the offer lifetime.
Amount: Cost of the offer to the consumer.
TCPA Consent Text: Company TCPA consent message.
Dynamic Offer Settings
Dynamic offers are used for clients when posting via outbound ping-post, allowing the lead to be sold to other businesses beyond the primary client. Due to the varying response types from outside systems, a custom script is required to use dynamic offers. To use this feature, contact a ClickPoint representative for assistance. An example response will be needed for the script to be written. The dynamic offers scripting is based on the same fields as static offers.
