EmpireVault

Knowledge Base / Engage / Building Custom Forms

Building Custom Forms

Published July 07, 2026

Building a form

Navigate to Engage > Forms to open the drag-and-drop form builder. Add fields from the palette - text, email, phone, dropdown, checkboxes, consent, and more - and reorder them by dragging. A form is not live on your website until you click Publish.

Embedding the form on your website

Open the form's "Embed this form" panel for two ways to add it to your site: a WordPress block or shortcode ([engage_flexible_form]), or a JavaScript snippet for any other website. Submissions from either method appear under Engage > Submissions.

Notifications

In Form settings, choose which team members get emailed whenever a new submission arrives, so the right people know right away.

Follow-up email (optional)

Also in Form settings, you can enable a follow-up email - an automatic thank-you or booking-link message sent to the visitor right after they submit.

What the visitor sees after submitting

After a visitor submits, the form is replaced on the page by a styled confirmation panel. It shows your Success message (set in Form settings; it defaults to a thank-you). If a follow-up email is enabled, the panel also tells the visitor to expect an email from your sending address.

Conversion tracking with Meta Pixel

In Form settings, open the Conversion tracking (Meta Pixel) section, tick to enable it, paste your Meta Pixel ID, and pick a conversion event such as SubmitApplication, Lead, or CompleteRegistration. When a visitor submits, EmpireVault fires that event for your pixel only, so Meta Ads can attribute the conversion - without disturbing any other pixel on the page and without sending an extra PageView.

Posting submissions to Slack

Tick "Include submissions in Slack notifications" in Form settings to post each submission to a Slack channel. This requires a Slack destination to be set up with its "Custom form submission" event also enabled (under Platform > Integrations > Slack) - both the per-form toggle and the destination's event need to be on before anything posts, so a busy form does not flood a channel by accident.

The Slack toggle takes effect as soon as you save the form. The follow-up email's content, by contrast, is snapshotted when you publish - so if you change the follow-up text, publish the form again for the new wording to go out.

Was this article helpful?

Powered by EmpireVault