Forms
Signup forms
Embed a signup form with two lines of HTML, post your own form to us, or sign people up from your server. People confirm by email before they join, by default, and every signup keeps a record of what they agreed to.
What it does
A signup form turns a visitor into a contact you may email. You build it in the dashboard: the fields it asks for, the list people join, the tags they get, the language it speaks and how it looks. Forms are served from a separate domain of ours, sendheron.page, and you put one on your site in whichever of three ways fits.
The embed is two lines: a div where the form appears and one script, which goes anywhere on the page, once, however many forms the page has. If you would rather write the markup yourself, your own HTML form can post to us, and the visitor finishes on our check page with their details filled in, the consent sentence, a bot check and your button. If the form is a component in your own app, your server signs people up with one API call.
Whichever way they arrive, by default the person gets one confirmation email in the form's language, from your workspace's default sender, and becomes a subscribed contact on the form's list, with its tags, once they confirm. A new subscriber starts sequences like any contact added to a list or tagged, so a welcome sequence triggered by the form's list or tag picks them up with nothing else to connect.
The shape of it
- 01
Build the form
In the dashboard: its fields, list, tags, language and look.
- 02
Put it on your site
Two lines of HTML, your own form, or a call from your server.
- 03
They confirm
The email's link opens a page, and its button confirms.
- 04
They join
A subscribed contact on your list, with the form's tags.
How it works
Double opt-in is on by default. A submission becomes a pending signup, which is not a contact and never counts toward your plan's contact limit, and the confirmation email goes out. Its link opens a page with a button, and pressing the button is what confirms. The extra click is deliberate: company mail scanners open every link in a message within seconds of delivery, so a link that confirmed by itself would confirm addresses nobody confirmed. A signup that is never confirmed is deleted seven days after its last confirmation email.
You can turn double opt-in off for a form, and a submission then subscribes at once, with the bot check and the limits still in place. Two cases ask for the email whatever the setting: someone who unsubscribed from you before, who comes back only by confirming, and a signup made through the API.
Every address gets the same answer. A new address, one already waiting for its email, one already subscribed and one we will not mail all see the same message, so nobody can use your form to find out who is on your list. The only things a form says about an address are about the address itself: that it is not valid, or that its domain takes no mail.
Each signup keeps a consent record on the contact: the form, the address, the exact sentence the person agreed to, the language they read it in, how they signed up, and when and from which IP address and browser they submitted and then confirmed. Through the API, the submission's IP address and browser are the ones your server reports. The record is your proof of consent, and it stays if you delete the form.
<div data-sendheron-form="YOUR_FORM_ID"></div>
<script async src="https://sendheron.page/embed.js"></script>- Embed with a div and one script, valid as JSX in React and Next.js
- Or post your own HTML form to us, with our check page after it
- Or sign people up from your server with a key that holds signups:create alone
- Double opt-in by default, confirmed with a button rather than a link
- English or Bulgarian, one language per form, in your own words
- A card or plain fields, four typefaces, four colours, rounded corners, one line
- A consent record kept for every signup
What makes it different, honestly
A form asks for an email address and, if you want them, a first and a last name. There are no other fields and no popups: a form sits in your page where you put it.
Your wording is shown as plain text. The consent sentence and any text you reword are never read as HTML or CSS, and an https address in the consent sentence, such as your privacy policy, is the only link your words can make. The look is a handful of settings rather than a stylesheet, so when a form has to match your site exactly, write your own HTML form and post it to us.
Confirmation emails count toward your daily sending and a new sender's warm-up like any other email, so a brand new account's first confirmations can take a little longer to arrive. A form takes signups once your account has passed its sending review and your workspace has a default sender on a verified domain, which is the address its confirmations come from. It takes none while your plan has no room for another subscribed contact.
On a React or Next.js site
The two lines of the embed are valid JSX, so they paste into a React or Next.js component as they are, a Server Component included. The form loads inside the div's shadow root and the div itself is never changed, so hydration sees no difference. Client-side navigation works too: a div that appears later gets its form, and changing the form id on the same div swaps the form, so a language switch can keep the element.
The success message shows inside the form, and your page can act on a signup by listening for the sendheron:done event, which bubbles from the div with the form's id. Two setups need one more step. A React 18 app rendered only in the browser, such as one built with Vite or Create React App, does not run a script it renders, so the div goes in the component and the script once in index.html. And a site that sends its own Content-Security-Policy has to allow sendheron.page in script-src and frame-src.
When the form is your own component, call the signup route from a Server Action or a route handler, never from the browser, because the key is a secret. Give that key signups:create alone, so it can do nothing but what a public form does. Run your own bot check before the call, pass the visitor's IP address as your server saw it, and show the form's consent sentence next to your form, since that is the sentence the consent record keeps.
The look and the language
A form is a card with its own background and border, or plain fields on your page. Choose one of four typefaces the visitor's device already has, so nothing is downloaded, and four colours: the background, the text, the button and the button's text. Round the corners anywhere from square to 24 pixels, and put an email-only form's field and button on one line. Spacing, sizes and the error colour follow from those choices, so a form never looks broken.
Each form has one language, English or Bulgarian, and our texts follow it: the labels, the button, the error messages, the check page, the message after a submission, the confirmation email and the confirm pages. You can reword any of them except a few that stay fixed: the confirmation email's lines for someone whose button does not work or who never signed up, the link to report the form, and the pages shown before we know which form a visitor came from. Your own wording is never translated, so a bilingual site uses one form per language, each with its own consent sentence.
What to send the people who join
Questions
Signup forms, in detail
Free trial
Signup forms, live on every plan
Everything on this page ships today, on every tier. Start a trial and use it on real sending.
7-day free trial. Pick a plan, add a card, cancel before the trial ends and you won't be charged. 1,000 contacts and 5,000 sends during the trial.