Signup forms

Forms collect signups from your website and put them straight into a list. No coding beyond pasting one snippet.

Form types

Building one

1. 1Forms → New form, choose the type.
2. 2Add the fields you want. Email is always included; keep the rest short, since every extra field costs you signups.
3. 3Choose the list new signups join.
4. 4Style it, set display triggers for popups and slide-ins, then publish.

Adding it to your site

Published forms give you an embed snippet. On WordPress you can instead use the Nectazo Connect plugin and drop in a shortcode:

[nectazo_form id="your-form-id"]

Putting one on a Nectazo landing page

A form can also go on a landing page you build in Nectazo, with no snippet and no website of your own. Add a Form block to the page and choose this form.

Only inline and hosted forms can be used that way — a popup or slide-in is built to appear over somebody else's site. The page reads the form live, so editing it here changes every page carrying it, and the page separately records how many of its visitors signed up.

When it appears

Popups, slide-ins and bars need a trigger: immediately, after a delay, after scrolling a percentage of the page, on exit intent, or when someone clicks a button.

For the click trigger, add data-nectazo-open to any button or link on your site:

<button data-nectazo-open="YOUR-FORM-ID">Get the free guide</button>

The value is the form's id, and it is what ties a button to one form. That matters as soon as a page carries more than one: data-nectazo-open written bare, with no value, opens every form on the page — which is fine while there is one and confusing the moment there are two. The form editor shows the exact attribute to copy.

Or set a CSS selector on the form to use a button you already have, like #signup-btn. Buttons that appear after the page loads — inside a menu, a cart drawer, or anything a page builder renders late — work too, and the form can be closed and reopened as often as somebody likes. It still counts as one view.

Width

Popups, slide-ins and the hosted page take a width in pixels. It is worth more attention than it sounds: the width is fixed and the height is not, so a long heading and a full paragraph in a narrow card push everything downwards until the card is taller than the screen it is supposed to appear over. Widening it is usually the fix.

It also decides how a left or right image looks. That image takes a share of the width and then fills its column, so on a narrow card it is cropped to a sliver — at 440px roughly a quarter of the picture is visible, at 760px about half. Anything with a side image is held to a minimum width for that reason.

Type sizes

The title, body text and button each take their own size in pixels, so they can be tuned against one another rather than scaled together. A long heading is usually better served by a smaller title than by a wider card, and a short one can afford to be much larger than the default.

All three are read by the preview, the hosted page and the embedded form alike. They used to be fixed and slightly different on the hosted page, which made the preview very slightly untrue; they agree now.

How often it appears

A popup, slide-in or bar with an automatic trigger would otherwise appear on every page view, for ever, including to somebody who signed up a minute ago. Two settings stop that.

• Stop showing it once somebody signs up — on by default. Asking a person to subscribe on every page after they just did is the single fastest way to make a popup resented.
• After it is closed, show it again in N days — seven by default. Zero means every page view, which is the old behaviour and rarely what anyone wants.

Both are remembered in the visitor's own browser, so a different device, a different browser or a cleared history starts again. That is the honest limit of doing this without identifying people, which is a much larger promise than a signup form should make.

A form set to open when a button is clicked ignores all of it and opens every time the button is pressed. Somebody who clicks “get the guide” has asked for it; refusing because they closed it last week would be a fault, not a courtesy.

Field order

Fields appear in the order shown in the editor, and the arrows beside each one move it. Email is in that list like everything else, so you can put a first name above it if that reads better — it just cannot be removed or made optional, since a signup form that does not collect an address collects nothing.

Double opt-in

If the brand has double opt-in enabled, form signups arrive as pending and must confirm by email before they receive anything else. See Consent and unsubscribes.

It applies to addresses that are new to the list. Somebody already subscribed proved their address the first time, so they are not asked again — they go straight to the confirmation email and its lead magnet. Asking an existing subscriber to confirm a second time is a reliable way to lose them.

Two consequences worth knowing. On an established list most people filling in a form are already on it, so the no-confirmation path is the common one rather than the exception — word your success message so it is true either way. And testing a form with your own address will always take that path, so use an address you have never signed up with if you want to watch the opt-in email arrive.

Lead magnets

A form can give something away — a guide, a template pack, a sample chapter. Upload it on the form and it is delivered as a gated link in the confirmation email, so the file is only reachable by someone who actually confirmed their address. It is never a public URL and never an attachment.

• PDF, ZIP, EPUB, DOC, DOCX, PNG, JPG or WebP, up to 100MB. The file uploads straight from your browser to storage, so a large one is a matter of your connection rather than a limit here.
• The download link is per-recipient and tied to the form. Sharing it on works, so treat it as you would any unlisted link — it is a convenience gate, not a licence check.
• Replacing the file replaces it for everyone, including people who confirmed weeks ago, because the link points at the form rather than at a copy.

Uploading the file is only half of it. Something in the confirmation email has to link to it, and that is a separate screen. Open the form's Confirmation email, add a Button, and set its URL to {{lead_magnet_url}}. Any block that takes a link works — a button is simply the one people click.

Nectazo warns you on both screens while the link is missing, because an email with no link to the file still sends perfectly happily. Nothing is broken and nothing is logged; the subscriber just never gets their download, and you would only hear about it from whoever bothered to write in.

Abuse protection

A public form is the one part of Nectazo a stranger can reach, so two limits sit in front of it. Neither is something a real visitor will meet.

• A form accepts a limited number of submissions from any one internet address in a ten-minute period. Well past a person who mistypes their email and tries again, and low enough that a script cannot sit on the endpoint. Beyond it the form answers "too many attempts, please wait a moment".
• A confirmation email goes to any one address at most once an hour, no matter how many times the form is submitted. Without this, anyone could type a stranger's address into your form repeatedly and have Nectazo mail them over and over — from your domain, counted against your sending reputation.

Someone who genuinely lost their confirmation email and resubmits within the hour is not told anything different; the copy already sent is still valid, and it is the same email they would receive again.

What is recorded

Each signup creates or updates a contact, sets their source so you can tell where they came from, and adds them to the chosen list — which can in turn trigger an automation. A welcome sequence on a form's list is the single highest-value automation most brands set up.