Guides
Practical, no-fluff guides to building better forms · from your first form to advanced logic.
6 min read
Creating a good online form is less about software and more about knowing what you want to learn. This guide walks you through the four steps that turn a vague idea into a form people actually finish, from defining the goal to sharing the link and reviewing responses.
Guides6 min read
A survey is only as good as its questions. Poorly worded items quietly push people toward an answer, confuse them, or wear them out before they finish. This guide covers how to phrase questions clearly, choose the right type, and order them so respondents give you honest, useful data.
Guides6 min read
Conditional logic lets a form react to what people type, so everyone sees only the questions that apply to them. This guide explains how to show and hide fields, branch between pages, and add calculations or scoring without making your form feel like a maze.
Guides6 min read
There are several ways to put a form on your site, from a one-line snippet to a fully custom API integration. This guide walks through inline embeds, popup modals, the web component and JS SDK, and the public REST API so you can pick the approach that fits your build.
Guides5 min read
Building a form used to mean dragging fields onto a canvas one by one. AI form builders flip that: you describe what you need in plain language, and the AI drafts the fields, required rules, and logic in seconds. You still make the decisions, what to ask, how it flows, what happens after submit, but you start from a working draft instead of a blank page. This guide covers how to write a prompt that gets a good first draft, and how to refine it afterward.
Guides6 min read
Conditional logic is what turns a long, one-size-fits-all form into something that adapts to each respondent. Instead of showing every question to everyone, you set rules that reveal or hide fields based on what someone already answered. Below are five patterns you'll use in almost any form, from a simple follow-up question to branching a whole page, plus what to watch for so the logic stays easy to follow.
Guides6 min read
A single long page works fine for a short form, but once you're past ten or so fields, splitting into pages usually raises completion rates, people can see progress and tackle one topic at a time. Branching goes a step further: instead of everyone seeing the same pages in the same order, the form routes each respondent down a different path based on what they've already answered.
Guides6 min read
Validation exists to catch mistakes before they become bad data, not to interrogate every respondent. Done well, it's mostly invisible, people barely notice the guardrails until they need one. Done badly, it turns a two-minute form into a frustrating loop of unclear errors. This guide covers what's worth validating, which checks a good field type gives you for free, and how to write rules and messages that help people finish instead of giving up.
Guides5 min read
Some forms need a number that depends on other answers, an order total, a quote estimate, a quiz score. Rather than making respondents do the math themselves, a calculated field runs a formula in the background and updates the result the moment they answer. This guide covers how the formula syntax works, how to format the output, and where calculations are most useful.
Guides5 min read
Not every form should be open to anyone with the link. A password gate adds a simple checkpoint: respondents enter a shared password once, and the form only shows itself to people who know it. This guide covers when a password makes sense, how the unlock flow behaves for respondents, and what it does and doesn't protect against.
Guides5 min read
Some forms just take longer than one sitting to fill out, a detailed application, a multi-page survey, anything that asks someone to go dig up a document or a number they don't have on hand. Forcing a single unbroken session on those forms is where a lot of drop-off happens. Save-and-resume fixes that by letting a respondent leave and come back to exactly where they stopped. This guide covers when it's worth adding, how the flow works for the respondent, and what keeps a resume link secure.
Guides5 min read
Any form with a public link eventually attracts bots, not because it's popular, but because bots submit to any form URL they find, automated and untargeted. The fix isn't to make humans prove they're human with a fiddly puzzle, it's a layered approach: a lightweight challenge that runs invisibly for most people, a limit on how fast one source can submit, and validation that makes a blind, scripted submission more likely to bounce. This guide covers what actually works and what to skip.
Guides5 min read
Not every piece of data a form collects needs to come from a question. A hidden field carries a value along with the submission without ever showing it to the respondent, prefilled from the link that brought them there. The most common use is attribution: knowing which campaign, email, or ad actually drove a submission, without turning that into a question you'd have to ask everyone by hand.
Guides5 min read
A form written in one language only reaches people comfortable in that language, which is a real ceiling if your audience is international. Translating a form well means more than swapping words, every label, option, and validation message needs a version in each language, and the form needs a reliable way to decide which version to show a given visitor. This guide covers how AI translation speeds up the first pass, how locale detection picks the right language automatically, and what still needs a human check.
Guides5 min read
Net Promoter Score is the most widely used loyalty metric because it reduces a fuzzy feeling (do customers like us) into one comparable number. Done right, it takes one question, one follow-up, and a consistent schedule. Done wrong, it becomes a number nobody trusts because the wording changed between sends or the follow-up got skipped. This guide covers the exact question, how the scoring works, and how often to ask it without wearing out your audience.
Guides6 min read
Most feedback forms fail the same way: too many questions, too many of them vague. A handful of well-chosen questions, each earning its place, gets a higher completion rate and more usable answers than a long form that tries to cover everything at once. Below are 15 questions grouped by purpose, plus guidance on which to combine for different situations, from a quick post-purchase check-in to a deeper quarterly review.
Guides6 min read
Event registration forms get filled out fast, often on a phone, often while someone is doing something else. Every unnecessary field is a reason to abandon it halfway. This checklist covers what to collect, what to make conditional, and what to handle after signup, so you get a form people finish and data your event team can actually use.
Guides7 min read
A job application form has two audiences at once: candidates who should have a smooth, respectful experience, and a hiring team that needs comparable, screenable data. Get the balance wrong and you either lose good candidates to a clunky form or drown the hiring team in unstructured resumes. This guide covers the fields, consent, and screening logic that make both sides work.
Guides6 min read
Every field on a lead form is a small tax on conversion. The form's job is to capture enough to qualify and follow up on a lead, not to complete a full customer profile in one sitting. This guide covers the field count that actually moves conversion, how to keep longer forms from losing people halfway through, and how to track where leads came from without asking them.
Guides7 min read
GDPR compliance for a form is less about a single checkbox and more about a handful of consistent habits: collect less, explain more, keep data only as long as you need it, and honor requests to see or delete it. This guide is a practical checklist for form builders, not legal advice: GDPR interpretation varies by data type and use case, so confirm specifics with someone qualified for anything high-stakes.
Guides6 min read
A form that collects responses is only half the job; understanding those responses is the other half. Two different kinds of analysis matter here: quantitative, where completion rate and drop-off show you where the form itself is failing, and qualitative, where open-text answers show you what's actually on respondents' minds. This guide covers both, plus how AI changes the second one.
Guides6 min read
A quiz or scored assessment is a form with two extra jobs on top of collecting answers: doing the math and deciding what happens next. Whether it's a lead-qualification quiz, a personality test, or a knowledge check, the same three pieces make it work: point values per answer, a running total, and branching based on the result. This guide covers how to structure each piece.
Guides6 min read
An order form without a visible running total makes people do math in their head or wait for a confirmation email to find out what they're paying. A live total removes that uncertainty and catches input mistakes (an extra zero on a quantity field) before submission instead of after. This guide covers the structure: fields, the formula, and small details that make the total trustworthy.
Guides7 min read
Once a form is more than a one-off, you usually want it wired into something else: a script that creates forms programmatically, a system that reacts the moment a response comes in, or an AI agent that builds and edits forms as part of a larger workflow. This guide covers the three pieces that make that possible: the API itself, webhooks for real-time notifications, and MCP for AI agent access.
Guides