Everest Forms Integration
Needs a full rewrite — missing collect fields, extra fields, submission hook, field mapping notes, and troubleshooting. Here’s the updated version:
Everest Forms Integration#
Everest Forms is a WordPress form builder with a drag-and-drop editor. WP Smart Consent integrates with Everest Forms to add an opt-in checkbox to any form on your site, with per-form configuration accessed from the Everest Forms list screen.
Enabling the Integration#
In the WP Smart Consent dashboard, go to Form Sources and toggle Everest Forms on. This activates the integration globally. Per-form behaviour is configured individually from the Everest Forms list screen.
Per-Form Settings#
WP Smart Consent does not add a tab inside the Everest Forms editor itself. Instead, settings are accessed via a WP Smart Consent row action on the forms list. Go to Everest Forms → All Forms, hover over the form you want to configure, and click WP Smart Consent in the row actions below the form name.
This opens a dedicated settings page for that form with the following options.
Form Type#
Contact form — WP Smart Consent injects a consent checkbox above the submit button via the everest_forms_display_submit_before hook. Only submissions where the visitor ticked the checkbox are forwarded to your CRM destinations. The injection is PHP-only with no JavaScript required.
Newsletter form — no checkbox is injected. Every successful submission from this form is treated as an opt-in and forwarded automatically. Use this for dedicated newsletter signup forms.
Collect Fields#
Map the form’s fields to standard WPSC data fields. The dropdown options are populated automatically from your form’s registered fields.
Email — required. Select the Everest Forms field that contains the submitter’s email address.
First name, Last name, Phone, Company, Country — all optional. Map whichever fields from your form you want forwarded to your CRM destinations alongside the email.
Everest Forms field names in the dropdown correspond to the field labels as configured in the form builder. If a field label is changed in the builder after mapping, re-open the settings page and re-select the correct field.
Extra Fields#
Below the standard field selectors, the Extra fields section lets you map any additional Everest Forms field to a custom CRM key. Add a row, select the form field on the left, and enter the CRM key on the right.
The CRM key is the identifier your destination platform uses for that field — for example CITY in Mailchimp (MERGE tag), city in FluentCRM (custom field slug), or city as a HubSpot contact property. Whatever key you enter is sent alongside the standard contact data on every opt-in.
Submission Hook#
WP Smart Consent listens on the everest_forms_process_complete action, which fires after Everest Forms has validated and processed the submission successfully. Field values are read from the $entry_fields array passed by Everest Forms and matched by the field IDs configured in the per-form settings.
Troubleshooting#
Checkbox not appearing — confirm the form is enabled in the WP Smart Consent settings for that form. Also check that the form is not using a custom theme template that skips the everest_forms_display_submit_before hook.
Consent not being captured — everest_forms_process_complete only fires on successful validated submissions. If a submission fails validation or spam checks, the hook never fires and no consent is captured. Confirm the form is submitting successfully by checking Everest Forms entries.
Wrong field values forwarded — re-open the WP Smart Consent settings for the form from the forms list and verify the field dropdowns still match the correct fields. If field labels were changed in the builder, the mapping may need to be updated.