Getting Started

LeadExec's dynamic consent provider allows you to control and validate what consent text is displayed on a form that you receive leads from.

These requests are logged within LeadExec to provide the tools to verify consent to be contacted with regard to the TCPA laws.

More information regarding TCPA

Step 1: Configure your account to use TCPA options

Using a simple code snippet generated from LeadExec, you can control which consent text is displayed on forms you control as well as 3rd party forms that are sending you leads.

To get started, you must set up TCPA options within LeadExec.

More information on how to setup LeadExec for TCPA

Step 2: Configure your form or supply a 3rd party source with consent code

Once your LeadExec account is TCPA enabled and you have created a campaign to be used with your form. You will need to include the form code snippet in your form's HTML markup.

<!-- LeadExec Consent Provider Script Block -->
<script type="text/javascript">
	var consentKey = '[CONSENT_API_KEY]';
	(function () {
	    var consentJs = document.createElement('script'); consentJs.type = 'text/javascript'; consentJs.async = true;
	    consentJs.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + '';
	    var consentS = document.getElementsByTagName('script')[0]; consentS.parentNode.insertBefore(consentJs, consentS);

The CONSENT_API_KEY is supplied by the software and is used to identify the request with the form.

Step 3: Tell the consent code where in the form you would like the consent text

The consent code will place the text of the consent as HTML into a container called consentText.

You can label any container with the id=consentText, the code will automatically append the consent text within the container.

Important: This container must be visible to the end user, if the container is not visible the consent request will be rejected, and the lead will not be certified.

Step 4: Be sure that the form is sending the user's IP address

The consent provider system works off the user's IP address. When the form is submitted to the processor responsible for processing the field information and forwarding on to LeadExec, that system must include the user's IP address.

Failure to include the user's IP address to LeadExec will result in the consent request being ignored.

If you need to know the IP address reported to the consent provider, create a hidden input called consentTextIPAddress. This hidden field will automatically be populated with the IP address that the consent provider received when sending the text.

Example: <input type="hidden" id="consentTextIPAddress" name="IPAddress" />

You can then submit that field to your backend process and forward that on to LeadExec.