TCPA Consent Blocks

Consent Blocks let you add compliance disclosure text to any step in your funnel. They support TCPA, CCPA, GDPR, PIPEDA, CASL, A2P SMS, and custom consent language. You can place consent text above or below the submit button, optionally require a checkbox for explicit agreement, and the full consent text is captured and stored with every lead for your records.

Why Consent Blocks Matter

If your business contacts leads by phone, SMS, or email, you may be required to obtain and document consent under regulations like TCPA (US), CCPA (California), GDPR (EU), PIPEDA (Canada), or CASL (Canada). Consent Blocks make it easy to display the right disclosure language and capture proof that the lead saw (and optionally agreed to) your consent terms.

Adding a Consent Block

1. Open your funnel in the builder.
2. Select the step where you want to add consent (typically the final step before submission).
3. In the step properties, scroll to the Consent section.
4. Click Add Consent Block.
5. Select a template from the dropdown:
   • TCPA: Standard TCPA consent for phone and SMS marketing.
   • CCPA: California Consumer Privacy Act disclosure.
   • GDPR: General Data Protection Regulation notice.
   • PIPEDA: Canadian personal information protection notice.
   • CASL: Canada's Anti-Spam Legislation consent.
   • A2P SMS: Application-to-person SMS consent (for recurring messages).
   • Custom: Write your own consent text from scratch.
6. Edit the pre-filled text as needed.
7. Configure the options (see below).
8. Save your funnel.

Configuration Options

Position

Choose whether the consent text appears above or below the submit button. Most lead generation forms place TCPA consent text below the button.

Checkbox

By default, consent blocks display text only (no checkbox). You can enable a checkbox to require explicit agreement:

• Checkbox off (default): The consent text is displayed as a disclosure. Submitting the form implies consent.
• Checkbox on, not required: A checkbox appears next to the text. The lead can optionally check it, but it is not required to proceed.
• Checkbox on, required: The lead must check the box before they can submit. If they try to proceed without checking, a validation message appears (default: "You must agree to continue", customizable).

Webhook Field Name

Each consent block has a customizable webhook field name (default: consent_text). This is the key used in your webhook payload to deliver the consent text. You might rename it to tcpa_consent_text or ccpa_disclosure to distinguish between multiple consent blocks.

If the checkbox is enabled, an additional field is sent: {fieldName}_agreed with a value of true or false.

Styling

Customize the appearance of each consent block:

• Font size: Extra small, small, or base.
• Text color: Any color using the color picker.
• Text alignment: Left, center, or right.
• Link color: Separate color for hyperlinks within the consent text.

Using Links in Consent Text

You can include clickable links in your consent text using markdown syntax:

Read our [Privacy Policy](https://example.com/privacy) to learn more.

Links automatically open in a new browser tab and are always underlined for visibility.

Line Breaks

Use \n in your consent text to create line breaks. This is useful for separating paragraphs or adding space between clauses.

Multiple Consent Blocks

You can add multiple consent blocks to the same step. For example, you might include:

• A TCPA consent block above the submit button.
• A CCPA disclosure below the submit button.
• An A2P SMS consent block below the CCPA disclosure.

Each block has its own template, text, checkbox settings, webhook field name, and styling. They operate independently.

Template Merge Tags

The TCPA and A2P SMS templates include merge tags that are automatically replaced at render time:

What Gets Stored with the Lead

When a lead submits a form with consent blocks, the following is captured and stored:

• The full consent text exactly as it was displayed to the lead (with merge tags resolved).
• The template type (TCPA, CCPA, GDPR, etc.).
• The checkbox status (checked or not checked, if a checkbox was shown).
• The timestamp of when consent was captured.

This data is stored in a dedicated consent field on the lead record, separate from the form data. It is also visible on the lead detail page under the Compliance and Consent section.

Webhook Delivery

Consent data is included in all integration payloads: webhooks, Zapier, LeadProsper, LeadByte, and email notifications. The full consent text is sent as plain text (any markdown links are stripped to their display text).

Pro Tips

• Templates are starting points. Always review and customize the text with your company name, phone number, and specific terms.
• Consult with your legal team to ensure your consent language meets regulatory requirements for your industry and region.
• Use different webhook field names for each consent block (e.g., tcpa_text, ccpa_text) so they are easy to identify in your CRM.
• The consent text stored with each lead serves as documentation of what the lead agreed to, which is valuable in the event of a compliance audit.
• Consent blocks work in both hosted funnel pages and embedded funnels on external websites.