Skip to content
Moosewave
Demo
Forms in Moosewave

Create signup forms that keep permission clear.

Create forms, popups, and embeds that explain what someone will receive and save exactly what they agreed to. Moosewave keeps that signup source with their contact record.

Illustrative product example using sample data. No live action is run.
What you want to do

Grow the list cleanly

Example
Enter to preview · Shift + Enter for a new line

Opens the guided product tour with example data. No live actions run.

  1. Purpose writtenExpectation and channel made explicitClear
  2. Permission recordedSource, wording, and time retainedSaved
  3. Confirmation linkedDouble opt-in and failure statesReady
  4. Waiting for reviewThe exact form must be approved firstReview
Everything stays togetherForm · permission · welcome journey · plan · approval · historySaved
Decision9:41
Grow the list cleanly

Signup path ready

The form, permission wording, confirmation, and welcome handoff share one revision.

Details
Visible
Checks
Ready
Action
Waiting
Review exact versionNothing runs until the required decision is recorded.

Effective forms

What makes a signup form effective?

An effective form asks only for information you will use. It also says what the person will receive and how often it may arrive.

Place the form after useful content or near the relevant action. A clear promise is more helpful than a vague request to join a newsletter.

Example / signup checks

Submitting a form starts the signup. Confirmation finishes it.

A dependable signup checks the submission, blocks obvious bots, saves the consent wording and source, then confirms the email address before allowing marketing messages.

  1. Form submitted

    The required details and displayed consent are saved.
  2. Bot check

    Basic checks and submission limits block obvious automation.
  3. Consent record saved

    Wording, source, and time show how permission was given.
  4. Address confirmed

    A clicked confirmation link shows that the person can access the address.
  5. Ready for marketing

    Only a confirmed address can receive marketing.
Each check protects list quality and records consent.

This is an explanatory sequence, not a working signup form. Nothing in this example accepts input or sends a request.

In Moosewave

Keep signup source and permission attached to every contact

Moosewave keeps the signup wording, time, and source with each submission. That context stays attached to the customer record.

Each form can ask for an email confirmation, known as double opt-in. Built-in bot checks run before a visible challenge is needed.

  • Inline, embedded, and pop-up forms connected to one customer record
  • Signup wording, time, source page, and any appropriate extra data kept together
  • Optional double opt-in with a separate confirmation time
  • Hidden bot checks and limits on rapid submissions before a visible challenge
  • New subscribers sent directly into the chosen welcome flow
Signup formIllustrative
Confirmation
Double opt-in
Placement
Inline
Consent
Recorded
Confirmation
Required
Destination
Welcome flow
An illustrative representation of the signup form interface. Not a screenshot, and not representative of any particular account's results.

Learn the details

Practical guidance, when you need it.

Open the question that matters to you. The core product workflow is above; these sections explain the underlying concepts and tradeoffs.

Opt-in choice

Should you use single or double opt-in?

Single opt-in adds a contact after the form is submitted. Double opt-in waits for a confirmation click, which can filter typos, unwanted signups, and some bots.

Double opt-in also records that the person could access the email address. The right choice depends on your audience, risk, and applicable law; clear permission still matters.

Bot defence

How do bot submissions damage a list?

Automated submissions can add invented, mistyped, or harvested addresses. Sending to them may increase bounces, complaints, and other signs of poor list quality.

Use several checks: a field hidden from people but attractive to bots, limits on rapid submissions, and double opt-in. Add a visible challenge only when needed.

Placement

Where should forms be placed?

Place a form where the offer follows naturally from what the visitor is doing. Common locations include the end of useful content and a relevant product page.

Avoid covering content as soon as someone arrives. If you use a pop-up window, wait for a meaningful action and make the close control obvious.

Common questions

Does double opt-in reduce list growth?

It can reduce confirmed signup totals because some people never complete the extra step. It can also filter typos, unwanted signups, and some automated submissions.

How many fields should a signup form have?

Start with the email address, then add only fields you will use. Ask for a name or preference when it clearly improves the promised experience.

Are pop-ups bad for SEO?

Pop-ups that cover the page can make content harder to reach, especially on mobile. Keep important content available, delay optional prompts, and follow current search guidance.

Do I need a CAPTCHA on my signup form?

Not always. Start with limits on rapid submissions, a hidden bot field, and email confirmation where appropriate. Add a visible challenge when abuse continues or risk is high.

See it in context

Build a useful, permission-based audience.

The guided demo uses sample data and does not send anything. It shows where this capability fits in a complete customer journey.