Guides

Signup forms

A signup form is a page we host for you where people join your list. Every signup is confirmed by email (double opt-in) before the person becomes a contact, so your list holds only addresses whose owners asked to hear from you.

Before you start

A form sends a confirmation email, so it needs what sending needs:

  • an approved account with a plan;
  • a verified sending domain and a default sender on it (the confirmation comes from that sender);
  • your organization name and mailing address in Settings → Workspace.

If one is missing, the editor says which and links to where you fix it. Anyone on your team can build and save a draft; Owners and Admins publish.

Building a form

Open Forms and create one. You can have up to 50. Each form has:

  • A name (up to 120 characters). Visitors don’t see it; people who sign up go into a segment called “Signed up: <name>”.
  • The words: a heading (120 characters), an optional introduction (600; say what people will get and how often), the button (40) and a thank-you message shown once someone confirms (400).
  • The fields: email is always asked. First name, last name and birthday are yours to show; visitors may leave them empty. Birthday is saved into a date property, which you add under Audience → Properties.
  • Your questions (up to 5). Ask anything short in your own words, such as a company or a job title. Each answer is plain text of up to 200 characters, saved in a text property you choose (add one under Audience → Properties first). Mark a question required if people must answer it. We read your questions before a form goes live, so never ask for anything listed under what a form can’t ask for.
  • A picture (optional), shown above the heading: choose one from your picture library or upload one. Describe it for people who can’t see it (up to 160 characters), or leave the description empty when it is only decoration. We read the description before the form goes live.
  • Topics (up to 10). When a form shows topics, people tick at least one.
  • Tags (up to 10). Everyone who confirms gets them. To gather people from several forms in one segment, give a segment a rule such as Tag has newsletter.
  • Three optional links: a privacy policy and a legal notice (in German, an Impressum, which businesses in Germany and Austria must have), both linked under the form, and a “Continue to” link shown after someone confirms. Each must be an https:// address on one of your verified domains (or a subdomain of one). We open a link when you save it and refuse one that is broken or leads off your domains, and we check every live form's links again each day: one that stops passing is taken off the page until it passes again.

Your logo and colours come from Settings → Brand. Every page also carries a line you can’t remove: “This page only signs you up for emails. It never asks for a password, a card or a payment.” “Powered by PristineSend” is always shown on Starter, and can be turned off from Growth up. The editor previews the form, the page after signing up and the page after confirming, at phone and desktop widths.

The form’s language

A form is in one of nine languages: English, Danish, Finnish, French, German, Norwegian (Bokmål), Portuguese (Brazil), Spanish or Swedish. Choose it under Language in the editor. Our words follow it everywhere a visitor reads them: the field names, the consent line and the lines at the bottom of the page, what to fix in a field, the page after signing up, the confirmation email, the confirm page and the page for reporting the form.

Your own words are never translated, so write the heading, introduction, button, questions, topics and thank-you message in the form’s language yourself. While the heading, button or thank-you message is still our default, it changes with the language; once you have written your own, it stays as you wrote it. Your organization name and mailing address are shown as you wrote them.

The language is part of what you publish: a change reaches the live form once you publish again and it passes review. We address visitors as each language’s signup pages usually do: Sie in German, vous in French, tú in Spanish, você in Portuguese, du in Danish, Norwegian and Swedish, and sinä in Finnish. A page that can’t tell which form it is about, such as a confirm link that no longer works, uses the visitor’s browser language, or English.

Publishing and review

Press Publish and the form is checked before it goes live. That review is how we keep a shared sending reputation clean, and how we stop forms that imitate another company before anyone sees them. While it runs, the form reads In review; you can keep editing the draft, and your edits wait until you publish again.

When it is live, the Owner and every Admin get a notice in the app and by email with its address. If a version isn’t put live, you get a notice too; a live form stays as it was. Publishing a change to a live form works the same way: the live form keeps running until the change passes.

A form is checked again by itself when something it shows changes: your organization name, the default sender’s name or address, your logo, a topic name or the page address. A change of sender address or page address stops signups until the new version passes, because the confirmation would otherwise come from somewhere the page didn’t say.

Drafting a form with your AI

An AI you connect to PristineSend (Claude, for one) can read your forms, with their numbers, and draft a new form or a change to one. It never publishes: you open the form in PristineSend, check it and press Publish, and it is checked before it goes live, as every form is. The editor says when the draft was last saved by your AI.

Reading forms is part of the default access new connections get. Drafting them is not: tick Edit form drafts for the connection in Settings → Connected agents. The same calls are in the API, for your own code: Forms API.

Sharing your form

Once a form is live, its editor shows a Share box with the form’s link, a Copy link button, and a ready-made button for your website. Put the link wherever people find you: a button or menu item on your website, your social bios, your email signature or a post. Nothing to install, and nothing of ours runs on your site, so it keeps working when your site changes.

Put your form on your website has the steps for Wix, Squarespace, WordPress, Shopify and Webflow, and for bios and email signatures.

The page address

Your forms live at https://<handle>.pristinesend.page/<form>. The handle is chosen from your verified domain when you make your first form. The last part is yours to set until the form has been live; after that it stays, so links you have shared keep working. If you need a different handle, ask us.

When someone signs up

  1. They fill the form and press your button. A Cloudflare check runs in the background to stop bots. A mistyped address is pointed out on the field (“Did you mean gmail.com?”), as is a domain that can’t receive email.
  2. They see Check your inbox, and we send the confirmation email. It comes from your default sender, with the subject “Confirm your subscription to <your organization>”, your logo, your organization name and mailing address, and one button. Its wording is fixed, so nobody can use it to send something else. The button works for 7 days.
  3. The button opens a page on your form’s address with Confirm subscription and, below it, This wasn’t me.
  4. Pressing Confirm makes them a subscribed contact and shows “You’re subscribed”, your thank-you message and your Continue link if you set one. Nobody is redirected away without seeing where they are going.

If someone else typed the address, the owner presses This wasn’t me: nothing is added, and that address gets no more confirmations from your forms for 90 days. If they ignore the email, nothing happens.

Your own sign-up flow can send the same confirmation without a form: add the contact through the API with double_opt_in: true (Double opt-in). It shares your forms’ daily limit, their protections and their email, in one of the same languages, and the signup.confirmed webhook tells you when someone confirms, from a form or from the API.

Why confirming takes two clicks

People sometimes ask why the email’s button opens a page with another button, instead of confirming straight away. It is deliberate.

Many company mail systems open every link in an email before the person sees it, to check it for malware. Microsoft Defender, Mimecast and Proofpoint all do this. If opening the link confirmed the signup, those scanners would confirm people who never asked to join, and they would press “This wasn’t me” for people who did. Your list would fill with addresses nobody agreed to, which is what double opt-in exists to prevent and what drives spam complaints.

So the link only opens the page, and nothing changes until a person presses the button, behind the same Cloudflare check as the form. One extra click is the price of a list where every confirmation means a person said yes.

What happens to the contact

  • A new address becomes a subscribed contact, with the names, birthday and answers they gave, in “Signed up: <form name>”, with the form’s tags.
  • An existing contact keeps what you already have; only empty names, birthday and answer properties are filled. An answer whose property you have since removed is not saved.
  • Someone who unsubscribed earlier and signs up again is subscribed again, because they asked. A bounce, a spam complaint about your email, or a block you set yourself stays in place.
  • Every confirmation is recorded: open the contact and choose How this contact joined to see the form, the words they agreed to and when they confirmed.
  • If your contact list is full, a confirmed signup waits. It is added as soon as there is room (after an upgrade or when you delete contacts), and dropped after 90 days. You are told once a week while signups are waiting.

Limits

  • Signups a day across your forms: one twentieth of your plan’s contact limit (100 on Starter, 500 on Growth, 1,250 on Scale, 3,000 on Pro), or 5,000 on an unlimited plan. For the first 14 days after your first form goes live it is 50 a day. Days are UTC. When the limit is reached, the page says it takes no more signups today and you get a notice; ask us if you need more.
  • One confirmation per address every 24 hours from your account, or every 30 days for someone who unsubscribed from you.
  • A single visitor can submit a form 20 times in 10 minutes. Anything we decline still shows Check your inbox, so the page never reveals who is on your list.
  • Confirmation emails don’t count against your plan’s email allowance.

Pauses and abuse reports

A form pauses by itself if its confirmations go badly: in 24 hours, 50 or more sent with 10% or more bouncing, or 2 marked as spam. A run like that usually means someone is typing other people’s addresses into your form. While paused, the page takes no signups and no confirmations go out, and the Owner and Admins are told. You can resume it from the editor once in 7 days; after that, write to support@pristinesend.com.

Every page has a Report abuse link. A report comes to us and we look; a report alone never takes your form down.

Numbers

Once a form has been live, its editor shows the last 30 days: page views, signups, confirmation emails sent, confirmed, not sent (and why), bounced and marked as spam, the share of emails that were confirmed, and where signups came from. A signup counts on the day it was made; an email and what happened to it count on the day it was sent.

We also open your form’s links every day. A link that breaks or leaves your verified domains is hidden from the page until it works again, and you are told.

Taking a form down

Unpublish in the editor (Owners and Admins) takes the page down; you can publish it again later, and it is reviewed first. A form that was never live can be deleted by anyone on your team. Deleting a form that has been live closes its address for good: it shows “This form is closed” and is never given to another form.

What a form can’t ask for

A form collects email sign-ups and nothing more. It must never ask for passwords, PINs or one-time codes, security answers or recovery phrases, sign-in details for other services, card or bank account numbers, government ID numbers, or health information, and it must never present itself as someone else. The businesses our Acceptable Use Policy doesn’t allow can’t use forms either. We may take down a form that breaks the policy.

Questions? Ask us.