Registration and onboarding forms - what to ask and when

Every field you add to a registration form reduces completion rates. Research shows a form with 3 fields converts at 25%. Add more than 6 fields and watch that drop to 15%. The cost is real, and the temptation is constant. You want to understand who your new users are, so you ask for more information upfront. Registration forms are where the friction starts.

The solution is not to ask less. It is to ask differently. Separate registration (collecting what you need to create an account) from onboarding (the experience after someone signs up). Ask for the minimum at registration. Ask for everything else during onboarding, when the user is already invested in your product. This shift changes everything about conversion.

This article covers what belongs in a registration form, when to ask for additional information, and how to design an onboarding experience that feels like a welcome instead of an interrogation.

What is the difference between registration and onboarding?

Registration and onboarding are not the same thing, but they are always treated as one step. Understanding the distinction changes how you build your forms and improves your conversion rates.

Registration is the account creation step. It collects the absolute minimum information needed to create a working account. Email, password, and possibly a name. That is it. Registration happens once and happens fast. The goal is to get the person across the line into your product as quickly as possible.

Onboarding is everything that happens after registration. It includes the welcome email, the first-time user experience, profile completion, preference settings, and the initial tutorial or walkthrough. Onboarding can happen over minutes, hours, or days. The goal is to help the new user understand what they just signed up for and how to get started.

The separation matters because the psychology is different. Someone filling out a registration form is deciding whether to commit. They are in a high-friction moment. Adding fields at this point costs you conversions. Someone who has already registered is past the commitment. They are now in a learning mode. They expect to provide more information as they explore. This is when you ask the questions that matter.

Which fields belong in a registration form?

The test is simple. Ask yourself: can the user use the product without this information? If the answer is yes, it does not belong in the registration form.

Email address

Email is required. It is the primary way you reach the user, send password resets, and verify account ownership. Always ask for email at registration. Make sure the field accepts all valid email formats, including aliases and plus addressing (for example, user+tag@domain.com). Avoid complex validation rules that reject valid emails.

Password

Passwords are required unless you offer passwordless authentication (which more brands should). If you use passwords, state the rules upfront. Do not surprise the user with errors after they try to submit. Common password requirements: 8 characters minimum, at least one number or symbol. Keep it simple. The NIST guidelines recommend against complexity requirements because they reduce memorability without significantly improving security. Let users see what they are typing with a show/hide toggle so they can catch typos before submitting.

Name (first and last)

Name is useful but optional at registration. Many users object to providing their legal name to a service they just met. If you need a name, ask for first name only or allow a username instead. Last name can wait until onboarding. Some brands skip names entirely and ask for them only when shipping or payment is required.

Phone number

Phone number does not belong in registration. It belongs in onboarding or at checkout. If the user has not used your product yet, they will not trust you with their phone number. Save it for later when they have decided you are legitimate.

Location or address

Address and location do not belong in registration. These are onboarding or checkout fields. The only exception is if your product is location-specific (for example, a local service directory). Even then, starting with a postcode instead of a full address reduces friction.

Job title, company, or industry

Job title and company belong in onboarding. B2B brands especially have the temptation to ask for these fields upfront. Resist it. A three-field form (email, password, first name) will convert better than a six-field form that adds job title, company, and industry. You can request this information right after signup when the user is exploring your onboarding flow.

Terms and privacy agreement

Always include a checkbox confirming the user agrees to your terms of service and privacy policy. This is legal protection, not optional. Place it just before the submit button. Make sure the text is readable and links to the full policy are clear. The checkbox itself should be checked manually by the user, not pre-checked.

When should you ask for additional information?

Additional information belongs in the onboarding flow. This is called progressive profiling, and it is the key to maintaining high registration conversion while still collecting the data you need.

Progressive profiling spreads questions across multiple touchpoints after signup. Instead of one long form, the user answers a few questions during registration, then additional questions appear naturally as they explore the product or receive emails.

Profile completion during first login

Right after registering, guide the user to a profile completion step. Ask for phone number, location, job title, company, and preferences. Present these fields on one page or across two pages. This is no longer a registration form. This is the onboarding experience, and the user expects to provide information here. The barrier is lower because they have already committed.

Welcome email with profile link

Send a welcome email immediately after signup. Include a button that links back to the profile completion form. Give the user a reason to click: "Complete your profile to unlock personalized recommendations" or "Set your preferences so we send you relevant updates." This spreads the friction across multiple days and multiple channels.

Triggered after first action

Ask for additional information after the user has taken a specific action in your product. For example, after they upload a document, ask for the document type and category. After they make a purchase, ask for billing preferences. After they join a community, ask for their interests. This approach ties the question to context, making it feel natural instead of intrusive.

Preference surveys in email

A few days after signup, send an email asking the new user to set their communication preferences. Ask about topics they are interested in, how often they want to hear from you, and what format they prefer. These questions belong in email, not on the website. Email is a lower-friction channel for optional information.

How to design the onboarding experience after someone registers

Onboarding is where you set the tone for the entire user relationship. A smooth onboarding experience turns a new signup into an active user. A rough one drives abandonment within hours.

Immediate confirmation page

After registration, show a confirmation page that acknowledges the account was created. Do not bounce the user to the dashboard immediately. Give them a moment of confirmation: "Your account is ready. Welcome to [brand]." Then show the next step. This breaks up the friction and gives the user a moment to catch their breath.

Email verification

Send a verification email right after signup. Use a verification link or code, not a long email confirmation process. The link should take the user directly to the onboarding flow, skipping any re-entry of the email. On mobile, verification codes sent via SMS are faster than email links because users do not have to switch between apps.

Profile completion form

The profile completion form is the first major step in onboarding. Show this immediately after email verification. Ask for the information you deferred from registration: phone number, location, job title, company, and preferences. Keep this to 4-6 fields maximum. Break it into two pages if it feels longer. Show progress (Page 1 of 2) so the user knows how much is left.

Guided first-time user tour

After profile completion, show a brief tutorial that explains the core features. This is not mandatory. Make it skippable. A video walkthrough, a clickable tutorial, or a simple list of quick-start guides. The goal is to show the user the 3-5 most important features so they do not get lost in the full interface.

Onboarding checklist

Display a checklist of onboarding tasks: verify email, complete profile, explore the main features, make your first action (upload a document, invite a team member, create a project). Make each task clickable so the user can jump to it. As they complete tasks, check them off. This gives a sense of progress and shows them they are moving through the onboarding process successfully.

Welcome email series

After registration, send a series of 3-5 emails over the first week. Email 1: Welcome and getting started guide. Email 2: Feature highlight and how to use it. Email 3: Success story or use case inspiration. Email 4: Help and support options. Email 5: Invite to community or customer group. Space them out (one every 1-2 days) so they feel helpful, not overwhelming. Make unsubscribe easy. Make each email clickable back to the product.

Common mistakes in registration and onboarding forms

These are the patterns that kill conversion and user activation.

Too many fields upfront

The single biggest mistake is asking for everything at registration. Brands justify this by saying they need the data for compliance, personalization, or account setup. The cost is conversion. A 6-field registration form loses 15% of people who would have converted on a 3-field form. That 15% drop compounds. If you get 1,000 signups per month on a short form, you might get 850 on a long form. The missing 150 per month is 1,800 per year. Data collection is not worth that.

Confusing field labels

Label fields clearly. Use simple language. Do not use jargon or clever phrasing. "What is your field of work?" is clearer than "Professional discipline" or "Domain of expertise." "How often should we email you?" is clearer than "Communication frequency preferences." If the label requires explanation, the label is wrong.

Requiring confirmation of email or password

Do not ask users to type their email or password twice for confirmation. This doubles friction and creates frustration when there are typos. Instead, show a toggle button that lets users see the password as they type. Use a verification email to confirm the email address actually belongs to them. This is faster and less error-prone.

Missing password visibility toggle

Always include a show/hide password icon. Users want to see what they typed to make sure there are no typos. This is especially important on mobile where keyboards are small and typos are common. The toggle should be right inside the password field, not a separate button.

Weak password feedback

If you require strong passwords, show a strength meter that gives real-time feedback. The meter should show whether the password is weak, medium, or strong, and why. "Your password is too short" is helpful. "Your password is weak" is not. The user needs to know what to fix.

Skipping email verification

Always verify the email address. A user might mistype their email and then lose access to their account. Do not skip this step. Use a fast verification method: a code sent to their email, not a confirmation email they have to open in the same client where they are registering. On mobile, SMS verification is faster than email.

Onboarding that does not feel like a welcome

After someone registers, the tone should shift from "prove yourself" to "we are glad you are here." Too many brands show an empty dashboard right after signup with no guidance. This is a mistake. Show the onboarding checklist. Show the tutorial. Send the welcome email. Make the new user feel like they made the right choice in signing up.

Mobile registration forms - what works and what fails

Mobile registration forms have different constraints than desktop. Smaller screens, touchscreen input, and browser behavior all change how forms perform.

Single column layout

Always use a single-column layout on mobile. Do not stack fields side by side. A mobile screen is narrow. Two columns create small boxes that are hard to tap. One column per field, full width, stacked vertically. This is faster to scan and easier to fill.

Input type matters

Use the correct input type for each field. Email fields should be type="email" so the mobile keyboard shows an email-friendly layout with @ and a period. Phone fields should be type="tel" so the keyboard shows numbers. Date fields should be type="date" so the user gets a date picker instead of typing. Using the right input type on mobile reduces typos and makes form filling faster.

Keyboard behavior and auto-advance

When the user finishes typing in a field on mobile, the keyboard should disappear if they are moving to the next field. Set the next field to auto-focus so the cursor jumps there automatically. This creates a flow where the user does not have to tap between fields. On a multi-page form, show a Next button that is obvious and easy to tap. Make buttons at least 44 pixels tall so they are easy to hit on a small screen.

Avoid auto-capitalization issues

Mobile browsers auto-capitalize the first letter of text input. This works fine for names but breaks email addresses. Use autocapitalize="off" on email, password, and username fields so the browser does not auto-capitalize. The same applies to username fields.

Form completion on slow connections

Test your registration form on slow mobile networks. A form that works on WiFi might time out on 4G. Keep scripts minimal. Show a loading indicator if the form takes more than 2 seconds to submit. On mobile, every millisecond of delay increases abandonment. Make the submit button disable itself after being clicked so the user cannot accidentally submit twice.

Viewport and zoom behavior

Make sure the form does not have zoom issues. When a form field is focused, the mobile browser should not zoom in aggressively. This looks like a bug and breaks the flow. If you use an input type of email or number, test that the browser does not zoom unexpectedly. Also make sure the form is responsive and fields scale properly on very small screens (under 350px wide).

How WEMASY handles registration and onboarding

WEMASY's website builder uses a two-step approach to registration and onboarding. The registration form asks only for email and password. No phone number, no company name, no location. The form converts at a high rate because it is short and easy.

After registration, WEMASY guides the new user through an onboarding checklist. The checklist includes profile completion (where we ask for website name and business type), choosing a template, and publishing the first page. The welcome email series introduces features step by step as the user explores the builder. This approach keeps the registration barrier low while still collecting the information we need to provide a personalized experience.

See what is included in each plan at /pricing.

Frequently asked questions