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 is configured per form directly inside the Everest Forms form builder, on the Integrations tab. Open Everest Forms → All Forms, edit the form you want to configure, and open the Integrations tab.

On Everest Forms Pro, WP Smart Consent appears in the Integrations sidebar alongside the native integrations (Mailchimp, HubSpot, and others) — click WP Smart Consent to open its panel. On the free edition, the WP Smart Consent panel is shown inline in the Integrations tab. Either way, the settings are identical.

You can also reach it via the WP Smart Consent row action on the forms list (Everest Forms → All Forms, hover a form, click WP Smart Consent), which opens the same Integrations tab. WP Smart Consent additionally appears on the Everest Forms Dashboard → Features page for discovery, with its logo and a link to its settings.

Settings are saved with the Save Settings button, which confirms success or reports the specific error.

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 Integrations tab 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 action, which fires after Everest Forms has validated the submission. The consent checkbox state is read directly from the submitted POST data (the wpsc_optin field), so it is captured reliably regardless of how Everest Forms processes its registered fields. Mapped field values are read from the $form_fields array by the field IDs configured in the per-form settings.

Because the hook fires only on validated submissions, consent is captured only on genuine, successful submissions — validation failures and spam blocks do not trigger it.

Troubleshooting#

Checkbox not appearing — confirm the form is enabled in the WP Smart Consent panel (Integrations tab) and set to Contact form mode (Newsletter mode does not inject a checkbox). Also check that the form is not using a custom theme template that skips the everest_forms_display_submit_before hook.

Settings not saving — the Integrations tab must be open in the form builder. The Save button confirms success with a “Settings saved.” message; if it reports an error, note the HTTP status shown and check the browser Console / Network tab.

Consent not being captured — everest_forms_process 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 panel on the Integrations tab 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.