Publish and share a form

Publish your form, put it on your site, and test a signup through to the saved contact. A builder preview does not test submission, confirmation or a welcome workflow.

Publish to go live

Check the fields, consent and branding, then click Publish. The Builder is replaced by Overview and Share.

Draft forms return not-found and accept no submissions. Edit unpublishes a live form; make the change and publish again to restore it. Plan for that interruption.

Share the form

Open Share and choose:

• Hosted link: a page you can share directly.
• Embed: place the form in your website using the generated code.
• Custom form: post from your own front end to the public form endpoint, with the configured fields and consent choice.

Visitors need no maxclicks login or API key. All three methods follow the published form's validation, consent, confirmation and protection settings.

A protected custom form must supply a valid captchaToken. Share hides the basic custom-form examples while protection is enabled; use the hosted link or embed, or implement the provider in your own front end.

The embed is two snippets, not one

Copy both the iframe and its handler script. For an inline form, the script keeps its height aligned with the content. For a popup, it is required to open the form and forward scroll and exit-intent triggers from your page.

Set the confirmation behavior

With double opt-in off, choose the post-submission behavior in the Builder.

Show a message

Show a thank-you title, optional message and optional coupon code in place of the form.

Redirect

Send the visitor to the URL you provide, such as a dedicated thank-you page.

With double opt-in on, these options are ignored. Visitors see a fixed check-email screen; the emailed link leads to a subscription-confirmed page. A visitor who leaves optional consent unchecked receives no confirmation email, even though the hosted form still shows its check-email screen.

Read view and submission counts

Open Analytics for views, submissions, conversion rate and the daily trend. Successful returning submissions count too, so total submissions do not equal unique new contacts or new subscribers. An opted-in submission pending double opt-in is counted after confirmation.

Use the numbers to identify what to investigate: traffic, required fields, the offer or popup timing. They do not establish which change caused a result.

Conversion Rate is submissions divided by unique views when available, otherwise total views. The display rounds to a whole percentage and caps at 100%. Twelve submissions and 100 unique views show 12%; those submissions can include returning contacts.

The daily comparison uses the latest seven recorded days against the preceding seven. It needs 14 daily entries and a nonzero previous submission total. The viewed-only chart uses total views, so its denominator can differ from the conversion-rate card. See form reporting.

Test the live form once

1. Open the hosted page or real embed and use an address you control.
2. Check required-field validation and the saved fields, tags and subscriptions in the selected contact schema.
3. Test both checked and unchecked consent, including a matching existing contact.
4. With double opt-in, open the confirmation email and verify when the contact is saved.
5. Inspect any resulting workflow or webhook before bringing in more traffic.

Fix problems with Edit, then republish and repeat the relevant check. Configured AI auto-fill can use credits, and follow-up emails still need your verified sending domain.

Configure form protection

An Admin with editing access can save provider keys in Settings → Forms Protection. Then select Cloudflare Turnstile, Google reCAPTCHA v3 or hCaptcha in the form. Missing keys block submissions; test protection on the real website domain.

See consent and double opt-in for the complete setup.