Quill Forms Integration
Quill Forms is a React-based WordPress form builder that renders its forms as a full single-page experience. Because Quill Forms is a React SPA, WP Smart Consent uses a different consent mechanism compared to standard PHP-rendered form plugins.
Enabling the Integration#
In the WP Smart Consent dashboard, go to Form Sources and toggle Quill Forms on. Per-form behavior is then configured individually from the Quill Forms form list.

Per-Form Settings#
WP Smart Consent integrates with Quill Forms as a native block you add in the Quill Forms builder. The block places a consent checkbox on your form and carries all of its WP Smart Consent settings on the block itself.
Adding the block#
Quill Forms’ builder is a full React app at admin.php?page=quillforms. To add consent tracking to a form:
- Open the form in the Quill Forms builder.
- Click Add Questions and choose WP Smart Consent from the block list (it appears with a shield icon, alongside blocks like Legal and Short text).
- Configure the block in its Question panel (see below).
All WP Smart Consent settings for the form live on this block — there is no separate settings page to open. Add the block once per form where you want to capture consent.
Form Type#
The Form type setting controls when a submission is forwarded to your CRM destinations. The block always renders as a consent checkbox on the front end; the form type only changes the forwarding logic.
- Contact — forward only when ticked. The submission is forwarded only when the visitor ticks the consent checkbox. Submissions left unticked are still recorded in your dashboard logs (with consent marked as not given) but are not forwarded.
- Newsletter — forward every submission. Every successful submission is treated as an opt-in and forwarded automatically.
You can also edit the Consent text shown next to the checkbox.
Collect Fields#
Under the field-mapping section, map the form’s blocks to standard WP Smart Consent data fields. Quill Forms identifies each block by its UUID — a unique identifier assigned when the block is added to the form (for example abc123-def4-…). Each dropdown is populated automatically from the form’s other editable blocks, shown by their labels.
- Email field — required.
- First name, Last name, Phone, Company, Country — all optional.
At submission time, field values are read directly from $entry->records['fields'] keyed by block UUID.
Extra Fields#
The Extra fields section maps any additional Quill Forms block to a custom CRM key. Click Add extra field to add a row, choose the form field on the left, and enter the CRM key on the right. Add as many rows as you need; remove a row with the × button. Each mapped value is sent alongside the standard contact data on every opt-in and recorded with the submission in your dashboard logs.
CRM Overrides#
The CRM overrides section lets you override list IDs and tags per CRM for this specific form. Click Add CRM override to add a row, then enter the CRM slug (for example, mailchimp), comma-separated list IDs, and comma-separated tags. These values take precedence over the global settings for that CRM when this form is submitted.
Submission Hook#
WP Smart Consent listens on quillforms_entry_processed, which fires after every Quill Forms submission is processed — including when entry storage is disabled. WP Smart Consent gates on the $context value being submission, so only real front-end submissions trigger consent capture, not internal processing calls.
Because the block carries its own settings, capture is enabled by the block’s presence on the form — you do not need to toggle a separate global option for submissions to be logged.
Logging#
Every qualifying submission is recorded in the WP Smart Consent dashboard under the quillforms source, including the mapped contact fields, the actual consent state (whether the box was ticked), and any extra mapped fields.
Troubleshooting#
WP Smart Consent block not appearing in the builder — confirm both Quill Forms and WP Smart Consent are active, then reload the form builder. Open Add Questions and look for WP Smart Consent in the block list.
Consent not being captured in Contact mode — confirm the WP Smart Consent block is on the form and that the visitor ticked the checkbox. In Contact mode, only ticked submissions are forwarded (unticked ones are still logged).
Submissions not being logged — make sure the Email field is mapped in the block’s settings. Enabling WP_DEBUG_LOG will surface a [WP Smart Consent] Quill Forms … line for each submission indicating what happened.
Wrong field values forwarded — Quill Forms blocks are identified by UUID, not label. If a block was deleted and re-added in the builder, it receives a new UUID and the mapping needs updating. Re-open the WP Smart Consent block’s settings and re-select the correct fields.