Campaign forms - Creating lead capture forms

Modified on Thu, 4 Dec at 11:34 AM

Campaign forms - Creating lead capture forms

Campaign forms are embeddable forms used for creating leads in a campaign. They can be embedded on external websites as contact forms or used internally by logged-in users to create new leads.

On this page

Jump to any section using the links below

Campaign forms are embeddable forms used for creating leads in a campaign. They can be embedded on external websites as contact forms or used internally by logged-in users to create new leads. Campaign forms support field selection, validation, success handling, and advanced multi-step workflows.


What are campaign forms

Campaign forms are embeddable forms used for creating leads in this campaign.

Primary use cases:

External website embedding:

  • Standard contact forms on your website
  • Lead capture landing pages
  • Newsletter signup forms
  • Service request forms
  • Quote request forms

Internal lead creation:

  • Quick lead entry by users
  • Step 1 of multi-step processes
  • Manual lead registration
  • Event registration

Key distinction: Campaign forms create NEW leads. For displaying data to existing leads (offers, invoices, information requests), use Webpage forms instead.


Accessing campaign forms

Go to a campaign's Settings menu and select Campaign forms.

The page displays:

  • Explanation text: "Campaign forms are embeddable forms used for creating leads in this campaign."
  • Status message when no forms exist: "There are no campaign forms. Click 'New campaign form' to create one"
  • Link: "Go to legacy form settings"
  • Button: + New campaign form (blue, top right)

Campaign forms table

When forms exist, a table displays all campaign forms with these columns:

Embed:

  • External link icon
  • Download/code icon (</>): Access embed code

Name: Form identifier (e.g., "webpage from")

ID: Information icon showing form ID

Fields: Lists all fields in the form:

  • Regular fields with slugs (e.g., "Adressen (adressen)", "Primær kontaktperson (primaer-kontaktperson)")
  • Select fields in italics (e.g., "Sælger (select_saelger)")
  • File fields (e.g., "File: Logo")

Content: </> Content button (blue): Edit form HTML/CSS/JS

On success: ? Actions button (blue): Configure success behavior

Edit: Edit icon (orange): Modify form settings

Delete: Trash icon (red): Remove form


Creating a new campaign form

Click + New campaign form to open the creation dialog.


New campaign form dialog

The dialog contains these configuration sections:


Friendly name

Field: Text input Purpose: Internal identifier for the form Example: "webpage from"

Use descriptive names that indicate the form's purpose or location.


Style

Field: Dropdown Default: "None" Purpose: Apply predefined CSS styling to the form

Options likely include:

  • None (custom styling)
  • Predefined style templates

Submit when pressing enter

Field: Dropdown Default: "No" Options:

  • Yes: Form submits when user presses Enter key
  • No: Enter key does not submit (useful for multi-line fields)

When to use Yes:

  • Simple single-field forms
  • Search forms
  • Quick entry forms

When to use No:

  • Forms with textarea fields
  • Multi-field forms where accidental submission is problematic

Fields

Field: Dropdown showing "4 fields selected" Purpose: Select which campaign fields to include in the form

Click to open field selector showing available campaign fields. Select the fields that should appear in the form.


Select fields

Field: Dropdown Example: "Sælger" (Seller/Salesperson) Purpose: Include select/dropdown fields in the form

These are typically relationship fields or predefined option lists.


Files

Field: Dropdown Example: "Logo" Purpose: Include file upload fields in the form

Allows users to upload documents, images, or other files when submitting the form.


Create button

Button: + Create (blue, bottom right) Action: Creates the campaign form with configured settings


Form actions configuration

After creating a form, click the ? Actions button to configure what happens on successful submission.


Form actions dialog

Dialog title: "Form actions: [form name]" Example: "Form actions: webpage from"

The dialog has two main sections:

  1. Validation settings
  2. Success behavior

Field rules apply on submissions

Field: Dropdown Default: "Yes - validate values" Purpose: Enable/disable field validation

Options:

  • Yes - validate values: Enforce field rules before submission
  • Other options may include validation bypassing

When enabled, field rules (required, format, length, etc.) are checked before allowing submission.


Show rejection message box

Field: Dropdown Default: "Yes" Purpose: Display error messages when validation fails

When Yes: Shows a message box with validation errors, allowing users to correct issues.


On successful form submission

Note displayed: "Note that the form is submitted using Ajax"

This means the form submits without page reload, providing a smoother user experience.


Redirect to page on success

Field: Dropdown Default: "Stay on page" Purpose: Control where users go after successful submission

Options visible in dropdown:

Stay on page: User remains on the current page (shows success message on same page)

Specific URL: Redirect to an external URL

Page in this campaign (Onboarding): List of internal pages in the campaign:

  • Booking viderestil
  • hubhus_dk/booking
  • Beregner
  • Tilbudsside 2.0
  • Køkkenbutik
  • Salgstal eksempel
  • har omdal tid?
  • Kundeinformationer
  • Leadhåndtering
  • Go Live Questions
  • Kunde har et spørgsmål
  • One-page landing
  • Tilbudsside
  • Referencer

Show popup message

Field: Dropdown Default: "No" Purpose: Display a popup/modal with success message

When to use:

  • Emphasis on success confirmation
  • Additional instructions after submission
  • Call-to-action after form completion

Show message on page

Field: Dropdown Default: "Yes" Purpose: Display success message inline on the page

This works with "Stay on page" redirect option.


ID of message HTML element

Field: Text input Default: "Auto" Purpose: Specify which HTML element should display the success message

Insert helper: "Insert: Form ID (replaces form with message on success)"

Options:

  • Auto: Automatically determines where to show message
  • Custom ID: Target specific HTML element by ID

When using "Form ID", the form itself is replaced with the success message.


Success message HTML

Field: HTML editor with line numbers Default: Shows "Auto" as placeholder Purpose: Customize the success message content

Placeholder search: "Search for placeholder.." field below the HTML editor

You can write custom HTML including:

  • Thank you messages
  • Next steps instructions
  • Download links
  • Additional information
  • Placeholders from the submitted lead

Action buttons

? Update button (orange): Save changes without closing ✓ Save and close button (orange): Save and close dialog


Advanced usage: Multi-step workflows

Campaign forms can be the first step in sophisticated workflows:

Scenario 1: Form → Booking

  1. User fills out campaign form (Step 1)
  2. On success, redirect to booking form
  3. Booking form uses data from newly created lead
  4. Result: Seamless lead creation + appointment booking

Configuration:

  • Set "Redirect to page on success" to a booking page
  • Booking form automatically picks up the new lead

Scenario 2: Form → Webpage form (Step 2)

  1. User fills out campaign form (Step 1: basic information)
  2. On success, redirect to webpage form
  3. Webpage form loads and displays content from newly created lead
  4. User completes additional information
  5. Result: Multi-step data collection process

Configuration:

  • Campaign form creates the lead
  • Redirect to internal webpage form
  • Webpage form uses lead context from campaign form submission

Use cases:

  • Complex service requests requiring multiple steps
  • Phased information collection
  • Progressive profiling
  • Conditional follow-up questions based on initial answers

Embedding campaign forms

To embed a form on an external website, click the download/code icon (</>) in the Embed column.

This provides:

  • Embed code (HTML)
  • JavaScript includes
  • CSS styling (if applicable)

Typical embed code structure:

html
<script src="[Hubhus script URL]"></script>
<div id="hubhus-form-[ID]"></div>

Paste this code into your website where you want the form to appear.


Internal vs external use

External use (embedded on website):

  • Public-facing contact forms
  • Lead capture on marketing sites
  • Newsletter signups
  • Service requests from website visitors
  • Anonymous visitors create leads

Internal use (logged-in users):

  • Quick lead entry by sales team
  • Event registration by staff
  • Manual lead creation with validation
  • Step 1 of internal workflows
  • Authenticated users create leads

Both use cases use the same form, but context determines who fills it out.


Best practices

Form design:

  • Only request essential information
  • Use clear field labels
  • Provide helpful placeholder text
  • Group related fields logically
  • Test on mobile devices

Field selection:

  • Start with minimal fields
  • Add fields only when necessary
  • Consider progressive profiling for complex needs
  • Use required fields sparingly

Validation:

  • Enable field validation for data quality
  • Provide clear error messages
  • Test validation rules thoroughly
  • Balance strictness with user experience

Success handling:

  • Always show clear success confirmation
  • Provide next steps or expectations
  • Consider redirecting to relevant content
  • Thank users for their submission

Multi-step workflows:

  • Use for complex processes requiring multiple information stages
  • Redirect to booking for appointment-based services
  • Chain to webpage forms for additional data collection
  • Maintain context across steps

Embedding:

  • Test embedded forms in target environment
  • Verify styling matches your website
  • Ensure mobile responsiveness
  • Monitor submission rates and errors

Campaign forms vs webpage forms

Understanding the difference:

Campaign forms:

  • Purpose: Create NEW leads
  • Use: External embedding, initial lead capture
  • Direction: Public → System (data flows in)
  • Example: Website contact form

Webpage forms:

  • Purpose: Display data to EXISTING leads
  • Use: Offers, invoices, information requests
  • Direction: System → Customer (data flows out and back)
  • Example: Quote approval, additional information request

Choose campaign forms when you need to capture new leads. Use webpage forms when interacting with existing leads.


Legacy form settings

The link "Go to legacy form settings" provides access to older form configuration interface.

This may contain:

  • Previous form versions
  • Legacy configuration options
  • Migration tools

Use the modern campaign forms interface for new forms.


Summary

Campaign forms are embeddable forms for creating new leads in a campaign, used for external website embedding as contact forms or internal lead creation by logged-in users. Configure forms with friendly names, style templates, field selection including regular fields, select fields, and file uploads, submit-on-enter behavior, and field validation. Set up form actions including validation rules, rejection messages, redirect options (stay on page, specific URL, or internal campaign pages), popup messages, inline success messages, and custom HTML success content. Advanced workflows enable multi-step processes where campaign forms redirect to booking forms or webpage forms, maintaining context across steps. Embed forms on external websites using provided embed code, or use internally for authenticated lead creation. Campaign forms create new leads, while webpage forms display data to existing leads - choose appropriately based on your use case.

? Common searches

web form • form setup • booking form • form builder

? Also known as

project • workspace • pipeline • customer

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article