# Mokaform Help Center (/help)
Mokaform documentation for building forms, creating surveys, publishing links, embedding forms, collecting responses, and automating workflows.
## ๐ Welcome to Mokaform [#-welcome-to-mokaform]
Whether you're building your first form or fine-tuning an existing workflow, you're in the right place. Follow a guide from start to finish, or jump straight to the feature you need.
[Create your first form](/help/getting-started/create-first-form) is the best place to begin. We'll walk through
building, testing, and publishing it step by step.
## ๐ Start here [#-start-here]
See how setup, building, sharing, submissions, analytics, and integrations fit together.
Follow a friendly, step-by-step guide from a blank page to a published link.
Pick a proven structure and adapt it to your workflow.
Learn when to use each input, layout, rating, consent, payment, and media block.
## ๐งฉ Build with confidence [#-build-with-confidence]
Show relevant questions, calculate scores, prefill fields, and personalize copy.
Apply your brand, colors, fonts, cover images, and custom CSS.
Configure language, password protection, scheduled open or close, spam protection, and SEO previews.
## ๐ฃ Share your form [#-share-your-form]
Publish changes, copy or customize your live link, share QR codes, download a PDF, and customize social previews.
Add inline forms, popups, popovers, sliders, side tabs, and full-screen embeds.
Use your own domain for form links and verified sender domains for email notifications.
## ๐ Learn from responses [#-learn-from-responses]
Review aggregate results, inspect submissions, download files, and export response data.
Understand views, starts, completions, page funnel metrics, question drop-off, and traffic sources.
Send emails, post channel alerts, sync databases, create tasks, and trigger webhooks.
## ๐ Connect your favorite tools [#-connect-your-favorite-tools]
Configure team emails, respondent emails, Slack alerts, and Discord alerts.
Post submission alerts to Slack channels.
Post submission alerts to Discord channels.
Create Airtable records from Mokaform submissions and map answers to fields.
Add each submission as a spreadsheet row for reporting and operations.
## โ๏ธ Manage your workspace [#๏ธ-manage-your-workspace]
Keep forms organized by organization, workspace, folder, and project.
Give each teammate the right level of access.
Configure your organization, domains, email sending, and API keys.
## ๐ Privacy and policies [#-privacy-and-policies]
GDPR, privacy, terms, cookies, legal notices, and abuse reporting.
Understand the usage signals that keep Mokaform fast and fair.
## ๐ฌ Still need a hand? [#-still-need-a-hand]
Can't find what you're looking for? Visit the [support page](/support). Tell us what you're trying to do, and we'll help you find the way forward.
# Admin settings (/help/admin)
Manage Mokaform workspaces, folders, members, roles, organization settings, default URLs, and custom domains.
Set up a tidy workspace where everyone can find what they need and has the right level of access.
## โ๏ธ Manage your organization [#๏ธ-manage-your-organization]
Organize questionnaires by organization, workspace, folder, and project.
Manage organization and workspace members with Owner, Admin, Editor, and Viewer roles.
Configure the organization name, default URL, custom domains, email sending domains, and API keys.
# Members and roles (/help/admin/members-roles)
Invite Mokaform teammates and manage Owner, Admin, Editor, and Viewer access across organizations and workspaces.
Mokaform has two role levels: organization roles and workspace roles. Use organization roles for account-wide administration. Use workspace roles for access inside a specific workspace.
Unlimited team members and shared workspaces are PRO features. If your account reaches a member or workspace limit,
Mokaform will show an upgrade prompt before you invite more people or create more shared areas.
## Organization roles [#organization-roles]
| Role | Use it for |
| -------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `OWNER` | Full organization control. Owners can manage organization-level settings and ownership-sensitive actions. |
| `ADMIN` | Organization administration without being the owner. Use for trusted operators who manage members, settings, and connected setup. |
| `EDITOR` | People who need to create and work with forms but should not own organization administration. |
| `VIEWER` | People who need read access at the organization level. |
Keep the number of Owners small. Add Admins for operational coverage instead of making everyone an Owner.
## Workspace roles [#workspace-roles]
| Role | What it allows |
| -------- | ------------------------------------------------------------------------------------------------------------ |
| `OWNER` | Can create and manage forms and responses, manage workspace members, and delete the workspace. |
| `EDITOR` | Can create and edit forms, but cannot delete forms or responses and cannot manage members. |
| `VIEWER` | Can view forms and edit sharing options, but cannot make form changes, view workflow, or download responses. |
Workspace roles are useful when a person should help in one area without receiving broad organization access.
## Invite workflow [#invite-workflow]
Decide whether the person needs organization-level access, workspace-level access, or both.
Invite them from the organization team area for organization access.
Invite them from the workspace member area for workspace-specific access.
Choose the least-permissive role that lets them do their work.
Review roles when a project ends, someone changes teams, or a form begins collecting sensitive data.
## Role examples [#role-examples]
| Person | Recommended access |
| ------------------------------------ | ------------------------------------------------------------------------------------------------ |
| Founder or account owner | Organization `OWNER` |
| Operations lead | Organization `ADMIN` |
| Marketing manager building campaigns | Workspace `OWNER` or `EDITOR` |
| Client reviewing a form | Workspace `VIEWER` |
| Analyst exporting responses | Workspace `OWNER` or another role that is allowed to download responses in your workspace policy |
## Security checklist [#security-checklist]
* Give people access to the workspace they need, not every workspace by default.
* Use Viewer for review-only access.
* Use Editor for form building without member management.
* Use Workspace Owner for team leads who manage members and responses.
* Review access before collecting personal, payment, file, health, legal, or hiring data.
## Related docs [#related-docs]
Organize forms around access boundaries.
Manage account-level configuration.
# Organization settings (/help/admin/organization-settings)
Configure Mokaform organization names, default URLs, custom domains, branded email domains, and API keys.
Organization settings control the account-wide defaults that affect teams, workspaces, public form links, and branded emails.
Custom subdomains, custom domains, branded email sending domains, workspaces, and unlimited team members require a
PRO account.
## What belongs in organization settings [#what-belongs-in-organization-settings]
| Setting area | What it controls |
| -------------------- | -------------------------------------------------------------------- |
| Organization name | The name shown to members and in account areas. |
| Team members | Organization-level invites and roles. |
| Default URL | The domain or subdomain used by default when sharing forms. |
| Domains | Verified form domains and subdomains. |
| Email sending domain | The domain used for branded respondent and team notification emails. |
| API keys | Developer access when your workflow uses the API. |
## Default URL [#default-url]
The default URL decides which domain Mokaform uses first when generating form links.
| Option | Use it when |
| ------------------ | --------------------------------------------------------------------------------------------------------- |
| Standard subdomain | You want a simple Mokaform-hosted URL such as a default `form` style subdomain. |
| Custom subdomain | You want a branded subdomain on the Mokaform survey domain. **PRO feature.** |
| Custom domain | You have verified your own domain or subdomain and want forms to use it by default. **PRO feature.** |
Changing the default URL affects future link creation and sharing defaults. It does not automatically update printed QR codes, emails, ads, or links you already sent.
## Domains [#domains]
Use the Domains area to add and verify domains for public form links.
Adding and using custom form domains is available on PRO.
Add the domain or subdomain in organization settings.
Copy the DNS records shown by Mokaform.
Add those records in your DNS provider.
Return to Mokaform and verify the domain.
Select the verified domain as the organization default or choose it for a specific form link.
Domain statuses can include pending, verified, or failed. If verification fails, compare the DNS record name and value exactly with what Mokaform shows. Some DNS providers automatically append the root domain to record names.
## Email sending domain [#email-sending-domain]
Use an email sending domain when notification emails should come from your own domain.
Branded email sending domains are available on PRO.
Typical workflow:
1. Add the sending domain in organization settings.
2. Add the required DNS records.
3. Verify the domain.
4. Use the verified sender domain in respondent or team email actions.
If the sending domain is not active, email actions that depend on it may be blocked or disabled until DNS is fixed.
## Safe change checklist [#safe-change-checklist]
* Confirm you are editing the right organization.
* Check who has Owner or Admin access before changing domains.
* Verify custom domains before selecting them as defaults.
* Regenerate QR codes after changing a form URL.
* Test respondent emails after changing the sending domain.
* Review API keys and integrations after access or ownership changes.
## Related docs [#related-docs]
Set up DNS records and troubleshoot verification.
Manage organization and workspace access.
Choose the public link, QR code, embed, or PDF share option.
# Workspaces and folders (/help/admin/workspace-folders)
Organize Mokaform forms and questionnaires with organizations, workspaces, folders, project naming, and move workflows.
Mokaform uses a simple hierarchy: organization, workspace, folder, questionnaire.
Creating additional workspaces and folders is a PRO feature. Use the default workspace to start, then upgrade when
you need separate team, client, or project areas.
## How the hierarchy works [#how-the-hierarchy-works]
| Level | Purpose |
| ------------- | ----------------------------------------------------------------------------------------------- |
| Organization | Holds global settings, domains, billing, and organization members. |
| Workspace | Separates teams, clients, departments, or projects. Workspace members can have their own roles. |
| Folder | Groups related questionnaires inside a workspace. |
| Questionnaire | The form itself, including builder, summary, submissions, share, connections, and settings. |
Use workspaces when access should differ. Use folders when the same team needs a cleaner list.
## Recommended workflow [#recommended-workflow]
Create or choose the organization.
Create a workspace for the team, client, department, or project.
Invite workspace members with the role they need.
Create folders for active form groups.
Create questionnaires inside the right folder.
## Workspace examples [#workspace-examples]
| Workspace | Folder examples |
| ---------------- | --------------------------------------------------- |
| Marketing | Lead capture, events, campaign feedback, newsletter |
| Customer success | NPS, onboarding, cancellation, support follow-up |
| People ops | Hiring, onboarding, employee feedback, requests |
| Agency client | Intake, approvals, feedback, reports |
| Product | Research, beta testing, feature requests, usability |
## Folder practices [#folder-practices]
* Keep folders broad enough that people can find things quickly.
* Use dates only when they matter, such as `Events 2026` or `Q3 research`.
* Archive or rename old folders instead of letting active work get buried.
* Keep template forms in a dedicated folder if your team copies them often.
* Put private or sensitive forms in a workspace with restricted membership, not just a separate folder.
## Moving forms [#moving-forms]
Move a questionnaire when the ownership or working context changes. Before moving it, check:
* Who needs access in the destination workspace.
* Whether connected integrations still point to the right destination.
* Whether exported response processes or internal bookmarks rely on the old location.
* Whether the form should keep the same public link.
## Related docs [#related-docs]
Understand organization and workspace permissions.
Configure organization name, default URL, and domains.
# Form design and branding (/help/build/design-branding)
Customize Mokaform form themes, colors, fonts, cover images, logos, layouts, and CSS for branded surveys and questionnaires.
Your form's design builds trust and boosts completion rates. We'll show you how to apply your brand in minutes.
You'll need a published form to customize. If you haven't created one yet, visit [Create your first
form](/help/getting-started/create-first-form).
## 1. Apply a theme [#1-apply-a-theme]
Open your form in the builder.
Find the **Customization** panel on the right side.
Click **Design** to see available themes, then click one to apply it instantly. All colors, fonts, and spacing
update automatically.
**Theme categories:**
* **Professional Business** โ clean, corporate styling with high contrast
* **Creative and Modern** โ bold colors and contemporary fonts
* **Minimalist Clean** โ simplified elements with white space
* **Industry-Specific** โ healthcare, technology, creative, finance
After applying a theme, you can override individual settings while keeping the overall style.
## 2. Customize colors and fonts [#2-customize-colors-and-fonts]
### Update your colors [#update-your-colors]
**Essential color elements:**
* **Text colors** โ questions, descriptions, help text
* **Interactive elements** โ buttons, input fields, focus states
* **Background** โ form backdrop and section backgrounds
Click **Appearance** in the customization panel.
Update the primary brand color for buttons and key elements.
Set a secondary color for accents and highlights.
Choose neutral colors for text and backgrounds.
Use your logo colors as the primary palette. Test colors for accessibility with a [contrast
checker](https://webaim.org/resources/contrastchecker/).
### Choose fonts [#choose-fonts]
Click **Typography** in the customization panel.
Select a font family (Source Sans 3, system fonts, or Google Fonts).
Adjust text sizes if needed.
**Readability guidelines:**
* Minimum 16px for body text
* High contrast between text and background
* Match your website's fonts when possible
* Test on mobile devices
## 3. Add your logo and images [#3-add-your-logo-and-images]
Click **Add cover** or **Add logo** in the customization panel.
Upload your image.
Adjust positioning and size.
| Image Type | Recommended Size | Format |
| -------------- | ---------------- | --------------------- |
| Logo | 512ร512px | PNG with transparency |
| Cover image | 1200ร630px | JPG or PNG |
| Social preview | 1200ร630px | JPG or PNG |
Optimize images for web to ensure fast loading times.
## 4. Style buttons and inputs [#4-style-buttons-and-inputs]
Go to **Button** settings in customization.
Choose background and text colors.
Select a border style (rounded, square).
Set button size and padding.
**Mobile positioning:**
* **Sticky at bottom** (recommended) โ always visible, higher completion rates
* **Normal position** โ traditional placement after form content
**Button text best practices:**
* **Action-oriented:** "Submit Survey" vs "Submit"
* **Value-focused:** "Get My Free Report" vs "Download"
* **Clear expectations:** "Send Feedback" vs "Click Here"
## 5. Test your design [#5-test-your-design]
Preview on desktop.
Test on mobile devices.
Check the tablet view.
Try different browsers.
**What to check:**
* Text is readable at all sizes
* Buttons are easy to tap on mobile
* Colors have sufficient contrast
* Images load quickly
* Form fits the screen width
Complete the form yourself on mobile to ensure a smooth experience.
## Advanced styling with CSS [#advanced-styling-with-css]
Custom CSS is perfect for matching exact brand guidelines, creating unique visual effects, fine-tuning spacing, and advanced hover states.
Advanced customization, custom CSS, and removing Mokaform branding are PRO features.
```css
/* Custom button hover effect */
.mf-button:hover {
transform: translateY(-2px);
box-shadow: 0 4px 8px rgba(0, 0, 0, 0.2);
transition: all 0.3s ease;
}
/* Brand-specific font */
.mf-survey-main {
font-family: 'Your Brand Font', sans-serif;
}
```
Test CSS changes on multiple screen sizes and browsers before publishing.
## Common design issues [#common-design-issues]
Use a [contrast checker tool](https://webaim.org/resources/contrastchecker/), aim for WCAG AA compliance (a 4.5:1
ratio for text), test in high-contrast mode, and darken text or lighten backgrounds.
Use sticky button positioning, increase text size to a minimum of 16px, test touch targets (buttons should be
44ร44px minimum), and reduce image sizes for faster loading.
Upload a higher-resolution image (512ร512px minimum), use PNG format with transparency, check the image isn't being
stretched, and ensure you uploaded to the correct field.
Check the browser console for errors (**F12** โ **Console**), try applying a different theme first, clear your browser
cache and refresh, or contact support with screenshots of the issue.
***
## What's next [#whats-next]
Show off your beautifully designed form.
See how design impacts response quality.
Try professional designs.
# Form settings and access control (/help/build/form-settings-access)
Configure Mokaform language, navigation, password protection, schedules, reCAPTCHA, duplicate prevention, and social previews.
Form settings control how respondents access, navigate, and share your form. Review them before publishing anything public or time-sensitive.
## Navigation and form experience [#navigation-and-form-experience]
| Setting | Use it for |
| --------------------- | ----------------------------------------------------------------------------------- |
| Show navigation | Let respondents move between pages when the flow allows it. |
| Auto jump | Move forward automatically when a page has one question and the answer is complete. |
| Show progress bar | Help respondents understand how much is left. |
| Animation direction | Choose vertical or horizontal page transitions. |
| One question per page | Turn a longer form into a focused step-by-step flow. |
Use progress bars for longer forms. For very short forms, a progress bar can add visual noise without helping completion.
## Language and default text [#language-and-default-text]
The language setting controls built-in interface text such as buttons, validation messages, date labels, and file upload prompts.
It does not translate your written form content. Translate question text, descriptions, option labels, and end screens yourself.
Use custom translation overrides when your brand needs different wording, such as "Continue" instead of "Next" or "Send request" instead of "Submit."
## Open and close access [#open-and-close-access]
Mokaform supports both manual and scheduled availability controls.
* **Closed**: immediately prevents new submissions.
* **Scheduled open**: keeps the form unavailable until a selected date and timezone.
* **Scheduled close**: automatically stops new submissions at a selected date and timezone.
* **Closed message**: custom title and description shown when a form is unavailable.
* **Closed redirect URL**: optional button that sends visitors elsewhere.
Good uses:
* Event registration windows.
* Hiring application deadlines.
* Time-limited research studies.
* Forms that should pause while you make major changes.
## Password protection [#password-protection]
Password protection restricts access to people who know the password.
Use it for:
* Internal surveys.
* Private customer feedback.
* Small-group forms.
* Draft review by stakeholders.
Password protection is useful for basic access control, but it is not a substitute for collecting only the data you
truly need and applying proper privacy practices.
## Spam and duplicate protection [#spam-and-duplicate-protection]
Use **reCAPTCHA** for public forms that are likely to attract bots or spam.
Use **unique submissions** when only one response should be accepted per identifier. The unique key can be based on a field value, such as email, or a metadata value, such as a known external ID.
Examples:
* One vote per email address.
* One registration per employee ID.
* One feedback response per customer ID.
## Branding visibility [#branding-visibility]
Use the Mokaform branding setting to control whether Mokaform attribution appears on the form. If you disable it, test the footer area on desktop and mobile so the final page still feels complete.
Removing Mokaform branding is available on PRO.
## Social preview and SEO [#social-preview-and-seo]
The meta settings control how the form appears in browser tabs, search results, and social media cards.
Saving custom link preview metadata is available on PRO.
Recommended fields:
* Title.
* Description.
* Site name.
* Icon.
* Thumbnail image.
* Search indexing preference.
Enable indexing only for public forms that should appear in search engines. Keep indexing disabled for private, internal, time-limited, or campaign-specific forms.
## Pre-publish checklist [#pre-publish-checklist]
* The language matches the audience.
* Required fields are truly required.
* The form is open when respondents need it.
* Scheduled close uses the correct timezone.
* Passwords and closed messages were tested in an incognito window.
* reCAPTCHA is enabled for exposed public forms.
* Duplicate submission rules use a reliable field.
* Social preview title and image look correct.
## What to explore next [#what-to-explore-next]
Publish the form and share the right link.
Route links and emails through your own domain.
Review privacy, GDPR, and legal resources.
# Build forms (/help/build)
Build better Mokaform surveys and questionnaires with question types, conditional logic, branding, and form settings.
Turn your questions into a form that feels clear, useful, and unmistakably yours.
## ๐งฉ What would you like to build? [#-what-would-you-like-to-build]
Choose the right block for each answer and open the per-type reference pages.
Personalize flows, calculate values, and pass hidden data.
Customize fonts, colors, media, branding, and custom CSS.
Configure language, availability, password, duplicate protection, and preview metadata.
# Conditional logic, variables, and hidden fields (/help/build/logic-variables)
Use Mokaform conditional logic, variables, URL parameters, hidden fields, and answer references to personalize forms.
Logic helps you ask fewer, better questions. Use it to show relevant pages, calculate scores or totals, prefill known data, and personalize messages with earlier answers.
## Choose the right tool [#choose-the-right-tool]
| Tool | Use it for | Example |
| ----------------- | ------------------------------------- | ---------------------------------------------------------------------- |
| Answer references | Reusing a previous answer in text | "Thanks, @Name. What is your budget?" |
| Conditional logic | Showing, hiding, skipping, or routing | Show pricing questions only when someone selects "I am interested." |
| Variables | Storing calculated or reusable values | Lead score, quiz score, order total, selected plan label. |
| URL parameters | Passing known data into the form link | `?utm_source=linkedin&company=Acme` |
| End screens | Different completion messages | Send qualified leads to a booking link and others to a thank-you page. |
Do not put passwords, secrets, payment data, or sensitive personal data in URL parameters. URLs can be stored in
browser history, analytics tools, and server logs.
## Reference previous answers [#reference-previous-answers]
Use answer references when you want the form to feel conversational.
Add the question that collects the value, such as name, company, plan, or country.
In later question text, descriptions, or completion copy, type `@`.
Choose the earlier field you want to insert.
Good uses:
* Greeting respondents by name.
* Repeating a selected product or plan.
* Showing a selected quantity or date in confirmation text.
* Making follow-up questions easier to understand.
## Add conditional logic [#add-conditional-logic]
Conditional logic decides what happens when answers match a rule.
Common actions include:
* Show or hide follow-up questions.
* Route respondents to a relevant page.
* Send respondents to a specific ending.
* Set or update a variable.
* Trigger notifications only for matching submissions.
Good conditions are narrow and testable. Instead of one large rule that handles every case, use a small number of clear rules with obvious outcomes.
## Use variables for scoring and totals [#use-variables-for-scoring-and-totals]
Variables store values that do not need to be visible as normal questions.
Common examples:
* Quiz score.
* Lead qualification score.
* Product subtotal.
* Event fee.
* Segment name, such as `enterprise`, `student`, or `high_priority`.
Use variables when you need to reference the same computed value in several places: copy, logic rules, emails, webhooks, or integrations.
## Capture URL parameters [#capture-url-parameters]
URL parameters let you pass context into a form link.
```text
https://your-form-link?utm_source=linkedin&utm_campaign=launch&company=Acme
```
Useful parameters:
* `utm_source`, `utm_medium`, `utm_campaign` for attribution.
* `email`, `name`, or `company` when sent from a CRM or email tool.
* `customer_id`, `plan`, or `segment` for internal routing.
After a URL parameter is defined in the form, you can use it to prefill fields, personalize text, or power logic.
## Build a simple branching form [#build-a-simple-branching-form]
Split the form into pages: introduction, qualification, details, and ending.
Add the question that decides the route, such as "What are you looking for?"
Create one rule per route.
Send each route to the matching page or ending.
Preview the form and test every branch with realistic answers.
Keep a test checklist next to complex forms. Branching issues usually happen because one answer path was never
previewed.
## Troubleshooting [#troubleshooting]
Check whether another rule is also targeting that question or page. When rules overlap, simplify them so each
condition has one clear purpose.
Confirm the variable is set before it is used. If it depends on a later answer, it will not have a value on earlier
pages.
Verify the parameter name exactly matches the form configuration. Query parameter names are case-sensitive in most
workflows.
Test with a full URL that includes `https://`. Avoid using answer references or hidden values in the domain part of
a URL.
## What to explore next [#what-to-explore-next]
Pick fields that make logic easier to maintain.
Trigger external workflows from completed submissions.
Check whether logic improves completion.
# Create your first form (/help/getting-started/create-first-form)
Create and publish your first Mokaform form with questions, logic, variables, design settings, testing, and sharing steps.
Build a professional form in minutes. This guide walks you from blank page to published link, with best practices to
boost completion rates.
## Overview [#overview]
* Create your form
* Add and customize questions
* Make it smarter with logic, references, URL parameters, and variables
* Brand it and preview on mobile
* Publish, share, and track responses
* Troubleshoot common issues
***
## 1) Create your form [#1-create-your-form]
Click **+ Create a new form** in the left sidebar of your dashboard.
If prompted, select the workspace to create it in.
Choose a starting method:
* **Start from scratch** for full control
* **Import questions** by pasting from docs or spreadsheets
* **Generate with AI** to get a draft from your goal or prompt
***
## 2) Add questions [#2-add-questions]
Mokaform feels like writing a document:
Type `/` to insert question types: short text, long text, email, number, multiple choice, rating, file upload, and
more.
Just start typing to add explanatory text between questions.
***
## 3) Customize questions [#3-customize-questions]
Click any **โฎโฎ** icon to open settings such as:
1. Toggle **Required** for essentials only
2. Add clear **Placeholder** text, e.g. [`name@company.com`](mailto:name@company.com) for an email question
3. Use **Help text** to clarify complex questions
4. Set **Validation** for emails, URLs, phone numbers, or number ranges
5. For choice questions, add an **other option** as needed
***
## 4) Make your form smarter [#4-make-your-form-smarter]
### Reference previous answers [#reference-previous-answers]
Type `@` while editing any text to mention an earlier answer.
* Example: *โThanks @Name โ whatโs your budget?โ*
* Use in question text, descriptions, or post-submit messages for a conversational feel
### Conditional logic [#conditional-logic]
In the **Workflow** tab, show questions only when relevant:
* Follow-up pricing questions only if โInterested in purchasingโ is selected
* Ask company size only for business customers
* Branch follow-ups based on satisfaction ratings
### URL parameters (pre-fill) [#url-parameters-pre-fill]
Pre-fill specific fields by adding parameters to the form URL:
[`https://your-form-link?name=Sarah&company=Acme`](https://your-form-link?name=Sarah\&company=Acme)
Great for:
* Event registrations when attendee info is known
* Customer feedback with known account details
* Sales follow-ups with CRM data
### Variables [#variables]
Variables are calculated fields for math and text operations behind the scenes.
* Calculate totals: prices ร quantities, tax, shipping
* Score quizzes automatically
* Concatenate or format text
* Create conditions based on computed values
Common use cases:
* Order forms: running totals and final price
* Quizzes: points and result messages
* Lead scoring: weight answers like budget and timeline
* Event fees: compute based on options
***
## 5) Make it look professional [#5-make-it-look-professional]
Use the **Customization** panel to match your brand:
* Fonts that match your site
* Text, background, and button colors
* Button placement optimized for mobile (sticky at bottom is often best)
* Optional custom CSS for pixel-perfect control
Also on each page:
* Click **Add cover** to include a header image
* Click **Add logo** to display your brand
***
## 6) Test before you share [#6-test-before-you-share]
Use **Preview** and complete the form like a real respondent.
* Do all questions make sense on first read?
* Are required fields truly necessary?
* Does it work smoothly on a phone?
* Is the thank-you message clear and actionable?
Fix anything that feels awkward or causes hesitation before you publish.
***
## 7) Publish and share [#7-publish-and-share]
Click **Share** to make your form live.
Copy the form link and share it.
Open the **Share** tab for additional options.
You can:
* Email the link to contacts
* Post on social media
* Embed on your website
* Add to your email signature
***
## 8) After you publish [#8-after-you-publish]
Responses appear immediately in your dashboard, including:
* Starts vs. completions
* Individual responses with timestamps
* Basic completion analytics
Enable notifications to get alerts for new responses. Export data to spreadsheets or downstream tools anytime.
***
## Troubleshooting [#troubleshooting]
Confirm itโs published and that your share message explains the value of responding.
Shorten the form. Reduce required questions. Remove friction.
Add help text and validation rules. Use choice options where appropriate.
***
## FAQs [#faqs]
Yes. Use @mentions of prior answers or variables in confirmation text.
Duplicate your form and share two links to compare performance.
Limit questions to what is necessary, enable validation, and review sharing controls.
***
## What to explore next [#what-to-explore-next]
Publish and share your form everywhere.
Read, analyze, and manage submissions.
Apply your branding, colors, and fonts.
# Getting started with Mokaform (/help/getting-started)
Start using Mokaform with workflow basics, first-form setup, templates, publishing, response collection, and integrations.
๐ Welcome! These guides take you from your first look around Mokaform to a published form that's ready for responses.
## ๐ Choose your starting point [#-choose-your-starting-point]
Understand how organization setup, building, sharing, responses, analytics, and integrations fit together.
Build, test, and publish a form one step at a time.
Start from a template and adapt it to your use case.
Choose **Create your first form** for a guided walkthrough. You can always explore the full workflow later.
# Form templates (/help/getting-started/templates)
Use Mokaform templates to create surveys, questionnaires, applications, feedback forms, and intake forms faster.
Skip the blank page and launch faster with professionally designed forms. Our template library gives you proven designs that you can customize in minutes.
Before you start, make sure you're signed in to your Mokaform workspace.
## Browse the template library [#browse-the-template-library]
Look for **Templates** in your left sidebar.
Click to open the template gallery.
Browse the templates, hosted at [mokaform.com/templates](https://mokaform.com/templates).
Visiting [mokaform.com/templates](https://mokaform.com/templates) lets you browse all templates in one place, filter by category, preview before selecting, and integrate directly with your account.
## Choose the right template [#choose-the-right-template]
| Category | Best For | Examples |
| -------------------- | ----------------------------- | ------------------------------------------------------ |
| **Marketing** | Campaigns and lead generation | Newsletter signups, webinar registration, lead forms |
| **Business** | Operations and workflows | Client intake, vendor applications, expense reports |
| **Product** | User research and feedback | Feature requests, bug reports, beta testing |
| **HR** | Recruitment and management | Job applications, performance reviews, exit interviews |
| **Customer Success** | Support and relationships | Support tickets, satisfaction surveys, testimonials |
| **Office** | Everyday workplace needs | Supply requests, room bookings, maintenance reports |
### Match your needs [#match-your-needs]
**For lead generation:**
* What information qualifies a lead?
* How much detail to request upfront?
* What incentive will you offer?
**For feedback collection:**
* Measuring satisfaction or gathering suggestions?
* Need quantitative or qualitative data?
* How will you act on feedback?
**For data gathering:**
* What specific information do you need?
* How will this data be used?
* Who needs access to it?
Choose templates from your industry for questions that match your audience's expectations.
## Customize your template [#customize-your-template]
**Select and import** โ browse templates by category or search, preview to see the questions and flow, then click
**Use this template**. The questions import into your form builder.
**Make it yours** โ keep the professional phrasing, logical flow, and mobile-optimized layouts. Replace generic
terms with your language, add relevant questions, remove ones that don't apply, and adjust the tone to match your
brand.
**Brand and publish** โ update the form title and description, apply your brand colors and fonts, add your logo,
customize the thank-you page, and test before publishing.
Start with the template structure and make incremental changes. Don't over-customize on your first attempt.
## Common template issues [#common-template-issues]
Look for similar templates in related categories, combine elements from multiple templates, or use the closest match
and customize heavily.
Remove non-essential questions, split into multiple shorter forms, or use conditional logic to show only relevant
questions.
Add questions specific to your needs, include qualification questions, or add optional follow-up questions.
If you can't find the right template, browse adjacent industries, [create a form from
scratch](/help/getting-started/create-first-form), or contact our support team for recommendations.
***
## What's next [#whats-next]
Make your template uniquely yours.
Get your form in front of your audience.
See what people are saying.
# Mokaform workflow (/help/getting-started/workflow)
Understand the Mokaform workflow from workspace setup and form building to publishing, submissions, analytics, and integrations.
Mokaform works best when you treat a form as part of a workflow: organize it, build it, publish it, collect submissions, automate the follow-up, then improve it with data.
## 1. Set up the workspace [#1-set-up-the-workspace]
Start with the administrative structure.
* **Organization**: the top-level account for settings, domains, billing, and organization members.
* **Workspace**: a team or project area where forms are created and managed.
* **Folder**: a way to group related questionnaires inside a workspace.
* **Members**: people who can own, edit, or view organization and workspace resources.
Use workspaces for real access boundaries, such as departments, clients, regions, or business units. Use folders for day-to-day organization, such as `Hiring`, `Customer feedback`, `Events`, or `Support`.
Additional workspaces, folders, and unlimited team members are PRO features. Start in the default workspace, then add
more structure when your team or projects need it.
## 2. Create the questionnaire [#2-create-the-questionnaire]
Build the form in the editor.
Create a blank form or start from a template.
Add question blocks that match the data you need.
Add layout blocks for headings, paragraphs, images, videos, dividers, and callouts.
Add pages, end screens, or redirects when the form needs structure.
Add logic, variables, and URL parameters when the flow should adapt to each respondent.
The most important design decision is the question type. Structured blocks such as Multiple choice, Dropdown, Rating, Date, Number, and Email are easier to summarize, export, and map into integrations than open text.
## 3. Configure the questionnaire [#3-configure-the-questionnaire]
Open the form settings before publishing.
| Area | What to check |
| ---------- | ----------------------------------------------------------------------------------- |
| Experience | Navigation, auto jump, progress bar, animation, and one-question-per-page behavior. |
| Language | Built-in labels, validation text, and custom translation overrides. |
| Access | Closed state, scheduled open or close, password, reCAPTCHA, and unique submissions. |
| Branding | Mokaform branding visibility and visual consistency. |
| Preview | Social title, description, site name, icon, thumbnail, and search indexing. |
For public campaigns, test the final form in an incognito window before sending links or printing QR codes.
## 4. Publish and share [#4-publish-and-share]
Publishing pushes the latest version live. The Share tab gives you the distribution options.
| Option | Use it for |
| ------------------- | ------------------------------------------------------------------------------ |
| Link | Copy the live form URL for email, chat, social, or ads. |
| Customized link | Choose a verified domain and readable path for the form. |
| QR code | Print or display a scannable link for events and physical locations. |
| Embed in a web page | Add inline forms, popups, popovers, sliders, side tabs, or full-screen embeds. |
| Embed in an email | Put supported questions directly into an email marketing campaign. |
| Download as PDF | Download a blank PDF version of the form. |
| Template | Share a copyable version of the form structure. |
| Preview | Control the social media title, description, icon, and image. |
If a link or QR code has already been distributed, avoid changing the domain or path unless you are ready to update the campaign.
## 5. Review the summary [#5-review-the-summary]
The Summary tab helps you understand performance without opening every submission.
* **Views**: how many times the form was opened.
* **Starts**: how many respondents began answering.
* **Submissions**: completed responses.
* **Completion rate**: the share of starters who submitted.
* **Average time**: how long completed submissions usually take.
* **Question summaries**: charts, distributions, averages, NPS score, rankings, matrix results, and heatmap results where supported.
Use the date range controls when comparing a launch period, a campaign, or changes after an edit.
## 6. Manage submissions [#6-manage-submissions]
Use the Submissions tab when you need row-level detail.
* Open individual submissions.
* Search, sort, or filter responses.
* Download all responses as CSV or XLSX.
* Download uploaded files from file answers.
* Download an individual submission as PDF.
CSV is best for analysis. XLSX is best when non-technical teammates need to open the export directly in a spreadsheet app. Individual PDFs are best for applications, signed forms, approvals, and records.
## 7. Connect follow-up actions [#7-connect-follow-up-actions]
Use integrations when a submission should trigger work outside Mokaform.
* Notify your team by email, [Slack](/help/integrations/slack), or [Discord](/help/integrations/discord).
* Send confirmation or next-step emails to respondents.
* Sync rows to Google Sheets.
* Create records in Notion or Airtable.
* Create tasks or issues in Linear, Jira, or Asana.
* Send webhook payloads to your own systems.
* Use Zapier or Make for broader app catalogs.
After connecting an action, submit a test response and verify the destination. Recheck mappings after renaming questions, options, destination fields, projects, databases, or channels.
## 8. Improve the form [#8-improve-the-form]
Use summary metrics, submissions, and analytics together.
* Low views usually means the distribution channel needs work.
* Low starts can mean the landing context or first screen is weak.
* Low completion rate can mean the form is too long, confusing, or asking for too much.
* High drop-off at one question usually means that question needs clearer wording, fewer required constraints, or a different question type.
* Repeated manual follow-up usually means an integration or notification should be added.
## What to explore next [#what-to-explore-next]
Choose the right block for each answer.
Organize forms by team, client, project, or department.
Turn submissions into follow-up workflows in other tools.
# Airtable integration (/help/integrations/airtable)
Connect Mokaform to Airtable, create records from form submissions, and map answers to text, select, checkbox, and attachment fields.
Use the Airtable integration when submissions should become structured records in a base.
## Before you connect [#before-you-connect]
* Create the Airtable base and table you want to use.
* Add the Airtable fields that should receive Mokaform answers.
* Make sure the connected Airtable account has permission to create records in that table.
* Give Mokaform questions stable names before mapping.
## Connect Airtable [#connect-airtable]
Open the questionnaire and go to the integrations area.
Choose **Airtable**.
Connect or select the Airtable account.
Choose the base and table.
Map Mokaform questions to Airtable fields.
Submit a test response and confirm a new Airtable record appears.
## Field mapping [#field-mapping]
| Mokaform question type | Airtable field type |
| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| [Short text](/help/build/question-types/short-text) | Single line text |
| [Long text](/help/build/question-types/long-text) | Long text |
| [Email](/help/build/question-types/email) | Email |
| [Phone](/help/build/question-types/phone) | Phone number |
| [Website](/help/build/question-types/website) | URL |
| [Number](/help/build/question-types/number) | Number |
| [Date](/help/build/question-types/date) | Date |
| [Time](/help/build/question-types/time) | Single line text or date/time field, depending on your table design |
| [Multiple choice](/help/build/question-types/multiple-choice) or [Dropdown](/help/build/question-types/dropdown) | Single select |
| [Checkbox](/help/build/question-types/checkbox) or multi-select answers | Multiple select |
| [Yes/No](/help/build/question-types/yes-no) or [Legal](/help/build/question-types/legal) | Checkbox or single select |
| [Rating](/help/build/question-types/rating), [Opinion scale](/help/build/question-types/opinion-scale), [NPS](/help/build/question-types/nps) | Number or rating |
| [File upload](/help/build/question-types/file-upload) | Attachment or URL field, depending on the payload available |
| [Signature](/help/build/question-types/signature) | Attachment or URL field, depending on the payload available |
## Checkbox and multi-select mapping [#checkbox-and-multi-select-mapping]
For a multi-select question, map the answer to an Airtable **Multiple select** field when you want one field containing all selected options.
For separate yes/no flags, create one Airtable **Checkbox** field per option and map each option to the matching checkbox field when your setup supports option-level mapping.
## Practical tips [#practical-tips]
* Create Airtable select options before testing if your table rejects unknown option values.
* Keep required Airtable fields mapped, or Airtable may reject record creation.
* Avoid changing field permissions after the integration is active.
* Use an internal field for submission ID or submission timestamp if you need deduplication.
## Troubleshooting [#troubleshooting]
Confirm the connected Airtable account has access to that base and refresh the connection.
Check required fields, field permissions, and whether select fields accept the submitted option values.
Confirm the Airtable field is a Multiple select field and that the option names match the values sent by Mokaform.
# Asana integration (/help/integrations/asana)
Connect Mokaform to Asana and turn form submissions into tasks with mapped projects, sections, assignees, due dates, and notes.
Use the Asana integration when submissions should become tasks in an operations, hiring, support, marketing, or project workflow.
## Before you connect [#before-you-connect]
* Choose the Asana workspace and project.
* Decide who should own or triage new tasks.
* Prepare any custom fields you want to map.
* Keep the form questions stable before mapping.
## Connect Asana [#connect-asana]
Open the questionnaire and go to the integrations area.
Choose **Asana**.
Connect or select the Asana account.
Choose the workspace and project.
Map answers to task title, notes, assignee, and available fields.
Submit a test response and confirm the task appears in Asana.
## Recommended mapping [#recommended-mapping]
| Asana field | Good Mokaform source |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Task title | [Short text](/help/build/question-types/short-text), request type, or generated summary |
| Notes | [Long text](/help/build/question-types/long-text) plus important submitted answers |
| Assignee | Fixed integration setting or logic-based routing |
| Due date | [Date](/help/build/question-types/date) question |
| Custom fields | [Dropdown](/help/build/question-types/dropdown), [Multiple choice](/help/build/question-types/multiple-choice), [Number](/help/build/question-types/number), [Rating](/help/build/question-types/rating), or [Email](/help/build/question-types/email) |
## Practical tips [#practical-tips]
* Use a concise task title and put details in notes.
* Use logic to create tasks only when a submission requires follow-up.
* If several teams use the same form, route tasks with question answers or hidden fields.
* Recheck mappings after changing Asana custom fields.
## Troubleshooting [#troubleshooting]
Confirm the connected Asana account has access to the workspace and project.
Confirm the Mokaform answer type matches the Asana custom field type.
Add conditions so only submissions that require action create Asana tasks.
# Discord integration (/help/integrations/discord)
Connect Mokaform to Discord and post form submission alerts to selected servers or channels with mapped answers and metadata.
Use the Discord integration when a community, operations team, or internal group should receive submission alerts in Discord.
## Before you connect [#before-you-connect]
* Choose the Discord server and channel that should receive alerts.
* Confirm you have permission to connect apps or webhooks for that server.
* Decide which answers should appear in the message.
* Avoid posting private respondent data in public or community channels.
* Use stable question names before building message content.
## Connect Discord [#connect-discord]
Open the questionnaire and go to the integrations or notifications area.
Choose **Discord**.
Connect or select the Discord server.
Choose the destination channel.
Build the message from answers, metadata, and fixed text.
Submit a test response and confirm the message appears in Discord.
## Recommended mapping [#recommended-mapping]
| Discord message part | Good Mokaform source |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Message title | [Short text](/help/build/question-types/short-text), selected category, or generated summary |
| Main body | [Long text](/help/build/question-types/long-text), submitted answers, and submission metadata |
| Routing fields | [Multiple choice](/help/build/question-types/multiple-choice), [Dropdown](/help/build/question-types/dropdown), [Yes/No](/help/build/question-types/yes-no), or hidden variables |
| Contact details | [Email](/help/build/question-types/email), [Phone](/help/build/question-types/phone), or [Website](/help/build/question-types/website) |
| Files and proof | [File upload](/help/build/question-types/file-upload) links or [Signature](/help/build/question-types/signature) links when needed |
## Good Discord use cases [#good-discord-use-cases]
* Alert a community operations channel when a report or request is submitted.
* Notify moderators about forms that need review.
* Send event registrations or waitlist entries to an internal channel.
* Route member applications to a private review channel.
* Keep lightweight submission logs for community workflows.
## Routing and conditions [#routing-and-conditions]
Use logic when only some submissions should reach Discord. For example, send moderator reports to a private channel and send event questions to an operations channel.
Keep Discord alerts short. Include only the fields that help the channel act quickly, then link to the submission for the full record.
## Troubleshooting [#troubleshooting]
Confirm the connected Discord account has access and that the channel allows connected app messages.
Confirm the Discord action is active, the trigger condition matched the submitted response, and the destination
channel still exists.
Check that the mapped question was answered on the tested branch and that it was not skipped by logic.
## What to explore next [#what-to-explore-next]
Configure team email, respondent email, Slack, and Discord alerts.
Send alerts to Slack channels.
Trigger Discord alerts only for matching submissions.
# Google Sheets integration (/help/integrations/google-sheets)
Sync Mokaform submissions to Google Sheets rows for reporting, operations, exports, and spreadsheet-based workflows.
Use the Google Sheets integration when your team wants submissions in a spreadsheet for reporting, sorting, filtering, or lightweight operations.
## Before you connect [#before-you-connect]
* Create or choose the Google account that should own the spreadsheet connection.
* Decide whether Mokaform should write to an existing spreadsheet or a new one.
* Give important questions stable names before mapping.
* Prefer structured question types for values you want to filter or chart later.
## Connect Google Sheets [#connect-google-sheets]
Open the questionnaire and go to the integrations area.
Choose **Google Sheets**.
Connect or select the Google account.
Choose the spreadsheet destination.
Map each Mokaform answer to the spreadsheet column where it should be written.
Submit a test response and confirm a new row appears.
## Field mapping [#field-mapping]
| Mokaform value | Google Sheets column type |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| [Short text](/help/build/question-types/short-text), [Long text](/help/build/question-types/long-text), [Email](/help/build/question-types/email), [Phone](/help/build/question-types/phone), [Website](/help/build/question-types/website) | Text |
| [Number](/help/build/question-types/number), [Rating](/help/build/question-types/rating), [Opinion scale](/help/build/question-types/opinion-scale), [NPS](/help/build/question-types/nps) | Number |
| [Date](/help/build/question-types/date), [Time](/help/build/question-types/time) | Date/time or text, depending on your sheet formatting |
| [Multiple choice](/help/build/question-types/multiple-choice), [Dropdown](/help/build/question-types/dropdown), [Yes/No](/help/build/question-types/yes-no) | Text |
| [Checkbox](/help/build/question-types/checkbox) or multi-select answers | Text list |
| [File upload](/help/build/question-types/file-upload) or [Signature](/help/build/question-types/signature) | File URL or attachment reference when available |
| Submission metadata | Text, date, or number column depending on the field |
## Practical tips [#practical-tips]
* Put a header row in the spreadsheet and keep column names clear.
* Do not delete or rename mapped columns without updating the integration.
* Use separate sheets for separate forms unless the forms have the same structure.
* Protect formula columns so incoming rows do not overwrite calculations.
## Troubleshooting [#troubleshooting]
Confirm the integration is active, the Google account still has access, and the test response was fully submitted.
Check the mapping and make sure the source question was answered on the tested branch.
Review the column format in Google Sheets. Numbers, dates, and multi-select answers may need explicit formatting.
# Integrations and notifications (/help/integrations)
Connect Mokaform submissions to notifications, Google Sheets, Airtable, Notion, Jira, Linear, Asana, webhooks, Zapier, and Make.
โก Put every submission to work. Send the right data to your team, your respondents, or the tools you already use.
## ๐ Keep people in the loop [#-keep-people-in-the-loop]
Send team emails, respondent emails, Slack alerts, and Discord alerts.
Post submission alerts to Slack channels.
Post submission alerts to Discord channels.
## ๐ Connect data and workflows [#-connect-data-and-workflows]
Sync submissions to spreadsheet rows.
Create records in a selected base and table.
Create pages or database entries from submissions.
Create product or engineering issues.
Create issues in Atlassian Jira projects.
Create tasks in Asana projects.
Send structured payloads to your own endpoint.
Connect Mokaform to Zapier automations.
Connect Mokaform to Make scenarios.
## ๐ ๏ธ Connect an integration step by step [#๏ธ-connect-an-integration-step-by-step]
Build and publish the questionnaire.
Open the questionnaire's connections, integrations, or notifications area.
Choose the destination app, notification type, or channel.
Connect or authorize the external account.
Choose the destination workspace, channel, base, database, table, spreadsheet, project, or endpoint.
Map Mokaform answers and metadata to destination fields or message content.
Submit a test response and verify the destination result.
## ๐งญ Map fields with confidence [#-map-fields-with-confidence]
Use structured Mokaform question types when an integration expects structured data.
| Destination needs | Prefer these Mokaform question types |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Text | [Short text](/help/build/question-types/short-text), [Long text](/help/build/question-types/long-text), [Email](/help/build/question-types/email), [Phone](/help/build/question-types/phone), [Website](/help/build/question-types/website) |
| Numbers | [Number](/help/build/question-types/number), [Rating](/help/build/question-types/rating), [Opinion scale](/help/build/question-types/opinion-scale), [NPS](/help/build/question-types/nps), [Payment](/help/build/question-types/payment) amount |
| Dates and times | [Date](/help/build/question-types/date), [Time](/help/build/question-types/time) |
| Single category | [Multiple choice](/help/build/question-types/multiple-choice), [Dropdown](/help/build/question-types/dropdown), [Yes/No](/help/build/question-types/yes-no) |
| Multiple categories | [Multiple choice](/help/build/question-types/multiple-choice) with multiple selection, [Checkbox](/help/build/question-types/checkbox) |
| Files or approvals | [File upload](/help/build/question-types/file-upload), [Signature](/help/build/question-types/signature) |
Keep question names stable after mapping. If you rename questions, delete destination fields, or change required fields in the destination app, test the integration again.
## โจ What to explore next [#-what-to-explore-next]
Send alerts to people and channels.
Choose structured fields that map cleanly.
Trigger integrations only for matching submissions.
# Jira integration (/help/integrations/jira)
Connect Mokaform to Jira and create issues from form submissions with mapped projects, issue types, priorities, and descriptions.
Use the Jira integration when submissions should become tracked work in an Atlassian Jira project.
## Before you connect [#before-you-connect]
* Choose the Atlassian site, Jira project, and issue type.
* Confirm the connected account can create issues in that project.
* Review required Jira fields for the selected issue type.
* Decide which Mokaform answers should become the summary and description.
## Connect Jira [#connect-jira]
Open the questionnaire and go to the integrations area.
Choose **Jira**.
Connect or select the Atlassian account.
Choose the site, project, and issue type.
Map Mokaform answers to Jira fields.
Submit a test response and confirm the issue appears in Jira.
## Recommended mapping [#recommended-mapping]
| Jira field | Good Mokaform source |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Summary | [Short text](/help/build/question-types/short-text), category, or generated short summary |
| Description | [Long text](/help/build/question-types/long-text), selected answers, file links, and respondent metadata |
| Issue type | Fixed integration setting |
| Priority | [Dropdown](/help/build/question-types/dropdown), [Rating](/help/build/question-types/rating), [Opinion scale](/help/build/question-types/opinion-scale), or calculated variable |
| Labels/components | [Multiple choice](/help/build/question-types/multiple-choice), [Dropdown](/help/build/question-types/dropdown), URL parameter, or hidden variable |
## Practical tips [#practical-tips]
* Keep the Jira summary concise.
* Make sure every required Jira field has a mapped value or fixed value.
* Use conditional logic so only actionable submissions create Jira issues.
* Recheck the integration after Jira admins change required fields, workflows, or permissions.
## Troubleshooting [#troubleshooting]
Confirm the connected Atlassian account has permission to browse the project and create that issue type.
Check required Jira fields, field permissions, and destination project configuration.
Reduce the mapped fields and include only the context your Jira users need.
# Linear integration (/help/integrations/linear)
Connect Mokaform to Linear and create issues from form submissions with mapped teams, projects, labels, priorities, and details.
Use the Linear integration when form submissions should become product, engineering, support, or bug-triage issues.
## Before you connect [#before-you-connect]
* Choose the Linear workspace and team that should receive issues.
* Decide which Mokaform answer should become the issue title.
* Prepare labels, priorities, projects, or workflow states if your team uses them.
* Keep sensitive respondent data out of Linear unless your team is allowed to process it there.
## Connect Linear [#connect-linear]
Open the questionnaire and go to the integrations area.
Choose **Linear**.
Connect or select the Linear account.
Choose the team or project destination.
Map answers into the issue title, description, priority, labels, or other available fields.
Submit a test response and confirm the issue appears in Linear.
## Recommended mapping [#recommended-mapping]
| Linear field | Good Mokaform source |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Title | [Short text](/help/build/question-types/short-text), [Multiple choice](/help/build/question-types/multiple-choice) category, or generated summary |
| Description | [Long text](/help/build/question-types/long-text) plus relevant metadata |
| Priority | [Dropdown](/help/build/question-types/dropdown), [Multiple choice](/help/build/question-types/multiple-choice), [Rating](/help/build/question-types/rating), or calculated variable |
| Labels | [Multiple choice](/help/build/question-types/multiple-choice), [Dropdown](/help/build/question-types/dropdown), URL parameter, or hidden variable |
| Project or team | Fixed integration setting or routing condition |
## Practical tips [#practical-tips]
* Keep issue titles short and scannable.
* Put full reproduction steps, screenshots, and context in the description.
* Use logic to create Linear issues only for submissions that need product or engineering work.
* Use [File upload](/help/build/question-types/file-upload) links carefully if screenshots may contain personal data.
## Troubleshooting [#troubleshooting]
Confirm the integration is active, the connected Linear account has permission, and required fields are mapped.
Check the selected team or project in the integration settings and any conditional workflow rules.
Map a short structured answer to the title and move long context into the description.
# Make integration (/help/integrations/make)
Use Make with Mokaform to route form submissions into multi-step automation scenarios across apps, databases, and notifications.
Use Make when Mokaform submissions should trigger a scenario with routers, transformations, scheduling, or multiple app actions.
## Before you connect [#before-you-connect]
* Decide which Make scenario should receive the submission.
* Prepare a webhook or Mokaform module available in your Make setup.
* Plan how answers should be transformed before they reach destination apps.
* Submit a realistic test response so Make can infer payload fields.
## Connect Make [#connect-make]
In Make, create or open the scenario.
Add the Mokaform trigger or webhook module available in your setup.
Connect Mokaform by following Make's setup instructions.
Submit a test response from Mokaform.
Map Mokaform values into later scenario modules.
Run the scenario once, verify the result, then turn scheduling on.
## Good Make use cases [#good-make-use-cases]
* Route submissions to different apps based on answers.
* Transform field values before sending them to another system.
* Create multi-step approval workflows.
* Sync data into tools without direct Mokaform integrations.
* Combine file links, respondent details, and metadata into a custom process.
## Practical tips [#practical-tips]
* Use routers when different answers need different destinations.
* Keep a submission ID in downstream records to avoid duplicates.
* Re-run a controlled test after changing Mokaform question names.
* Watch scenario history when debugging failures.
## Troubleshooting [#troubleshooting]
Confirm the scenario is listening or scheduled, the trigger is configured, and the Mokaform response was submitted.
Submit a fresh test response that includes the field and check whether logic hides the question for that branch.
Use the submission ID as a deduplication key in your Make scenario.
# Form notifications (/help/integrations/notifications)
Create Mokaform notifications for team emails, respondent emails, Slack alerts, Discord alerts, conditions, and branded sender domains.
Notifications send messages when a questionnaire receives a submission. Use them when a person or channel needs to know what happened.
This guide covers notification behavior. For channel-specific setup, see [Slack](/help/integrations/slack) and
[Discord](/help/integrations/discord).
## Notification types [#notification-types]
| Notification | What it does | How it works |
| ---------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Team email | Alerts your team when a submission arrives. | Choose recipients, subject, message content, and whether answers or a PDF should be included. |
| Respondent email | Sends confirmation, follow-up, or next-step emails to the person who submitted. **PRO feature.** | Map the recipient to an Email question, then write the message and sender details. |
| Slack | Notifies a Slack channel. | Connect Slack, choose the workspace and channel, then build the message from answers and metadata. |
| Discord | Notifies a Discord channel. | Connect Discord, choose the server or channel target, then build the message payload. |
Respondent email actions and custom email sender domains are available on PRO.
## Create a notification [#create-a-notification]
Open the questionnaire and go to the notifications area.
Choose when the notification should run: any submission, a specific ending, or submissions that match a condition.
Add an action, such as team email, respondent email, Slack, or Discord.
Connect the external account if the notification uses Slack or Discord.
Write the message using form answers where needed.
Submit a test response and confirm the message was delivered.
## Team email notifications [#team-email-notifications]
Use team email notifications when your team needs to act on each response.
Good uses:
* New lead alerts.
* Support requests.
* Application submissions.
* Payment or booking confirmations.
Keep the subject easy to scan. Include only the answer data your team actually needs in the message body or attachment.
## Respondent emails [#respondent-emails]
Use respondent emails when the person who filled out the form needs a receipt or next step.
Common examples:
* Confirmation emails.
* Application received messages.
* Event registration details.
* Follow-up instructions.
* Payment or booking next steps.
The recipient should be mapped to an [Email](/help/build/question-types/email) question. Test with a real inbox before sharing the form publicly.
## Slack and Discord alerts [#slack-and-discord-alerts]
Use [Slack](/help/integrations/slack) or [Discord](/help/integrations/discord) when a team watches a channel more actively than email.
Good uses:
* Send urgent support requests to a triage channel.
* Alert a sales channel when a qualified lead arrives.
* Notify a community or operations channel when a specific branch is submitted.
Use conditions when only some submissions should alert the channel. For example, notify support only when the issue type is urgent.
## Branded sender domains [#branded-sender-domains]
If respondent or team emails should come from your own domain, configure a branded email sending domain in organization settings.
Branded email sending domains are available on PRO.
## Troubleshooting [#troubleshooting]
Confirm the notification is active, the trigger condition matches your test submission, and the form was fully
submitted.
Check that the form has an Email question and that the notification recipient is mapped to that question.
Reconnect the external account. Channel permissions, deleted channels, revoked tokens, or workspace policy changes
can stop delivery.
Confirm the organization has an active branded email sending domain and that the account is on PRO.
## What to explore next [#what-to-explore-next]
Sync submissions to apps, databases, task tools, and webhooks.
Send submission alerts to Slack channels.
Send submission alerts to Discord channels.
Configure verified sender domains for email notifications.
Trigger notifications only for matching submissions.
# Notion integration (/help/integrations/notion)
Connect Mokaform to Notion and create pages or database entries from submissions with mapped answers and metadata.
Use the Notion integration when each submission should become a page, lead record, request, research note, or database item.
## Before you connect [#before-you-connect]
* Choose the Notion workspace and database or page destination.
* Make sure the connected Notion account has access to the destination.
* Create database properties for the answers you want to map.
* Use structured Mokaform fields for properties you want to sort or filter.
## Connect Notion [#connect-notion]
Open the questionnaire and go to the integrations area.
Choose **Notion**.
Connect or select the Notion account.
Choose the destination page or database.
Map Mokaform answers to Notion properties.
Submit a test response and confirm the Notion item is created.
## Field mapping [#field-mapping]
| Mokaform value | Notion property |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------- |
| [Short text](/help/build/question-types/short-text), [Long text](/help/build/question-types/long-text) | Text or title |
| [Email](/help/build/question-types/email) | Email |
| [Phone](/help/build/question-types/phone) | Phone |
| [Website](/help/build/question-types/website) | URL |
| [Number](/help/build/question-types/number), [Rating](/help/build/question-types/rating), [Opinion scale](/help/build/question-types/opinion-scale), [NPS](/help/build/question-types/nps) | Number |
| [Date](/help/build/question-types/date) | Date |
| [Multiple choice](/help/build/question-types/multiple-choice), [Dropdown](/help/build/question-types/dropdown), [Yes/No](/help/build/question-types/yes-no) | Select |
| [Checkbox](/help/build/question-types/checkbox) | Checkbox or multi-select |
| [File upload](/help/build/question-types/file-upload), [Signature](/help/build/question-types/signature) | Files/media or URL, depending on your Notion setup |
## Practical tips [#practical-tips]
* Map one concise field to the Notion title property.
* Put long answers in rich text properties or page body content.
* Keep Notion select option names aligned with Mokaform option labels.
* Recheck mappings after changing Notion database properties.
## Troubleshooting [#troubleshooting]
Confirm the Notion integration has access to the database and reconnect the account if permissions changed.
Check the mapping and confirm the question was answered on the tested branch.
Make sure a Mokaform answer is mapped to the Notion title property.
# Slack integration (/help/integrations/slack)
Connect Mokaform to Slack and post form submission alerts to selected channels with mapped answers, metadata, and conditions.
Use the Slack integration when a team should see new submissions in a channel they already monitor.
## Before you connect [#before-you-connect]
* Choose the Slack workspace and channel that should receive alerts.
* Make sure you have permission to add or authorize apps in that workspace.
* Decide which answers should appear in the message.
* Avoid sending sensitive respondent data to broad channels.
* Use stable question names before building message content.
## Connect Slack [#connect-slack]
Open the questionnaire and go to the integrations or notifications area.
Choose **Slack**.
Connect or select the Slack workspace.
Choose the destination channel.
Build the message from answers, metadata, and fixed text.
Submit a test response and confirm the message appears in Slack.
## Recommended mapping [#recommended-mapping]
| Slack message part | Good Mokaform source |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Message title | [Short text](/help/build/question-types/short-text), selected category, or generated summary |
| Main body | [Long text](/help/build/question-types/long-text), submitted answers, and submission metadata |
| Triage fields | [Multiple choice](/help/build/question-types/multiple-choice), [Dropdown](/help/build/question-types/dropdown), [Yes/No](/help/build/question-types/yes-no), or hidden variables |
| Contact details | [Email](/help/build/question-types/email), [Phone](/help/build/question-types/phone), or [Website](/help/build/question-types/website) |
| Attachments and evidence | [File upload](/help/build/question-types/file-upload) links or [Signature](/help/build/question-types/signature) links when needed |
## Good Slack use cases [#good-slack-use-cases]
* Alert sales when a qualified lead is submitted.
* Notify support when an urgent request arrives.
* Send internal application reviews to a hiring channel.
* Route payment or booking confirmations to operations.
* Create a channel log for high-value submissions.
## Routing and conditions [#routing-and-conditions]
Use logic when only some submissions should reach Slack. For example, send urgent support requests to `#support-triage`, high-value leads to `#sales`, and normal requests only to email.
Keep channel alerts concise. Put the most actionable fields near the top and link to the submission when the team needs the full record.
## Troubleshooting [#troubleshooting]
Confirm the connected Slack account has access to the workspace and channel, then reconnect Slack if permissions
changed.
Confirm the Slack action is active, the trigger condition matched the submitted response, and the channel still
exists.
Check that the mapped question was answered on the tested branch and that it was not skipped by logic.
## What to explore next [#what-to-explore-next]
Configure team email, respondent email, Slack, and Discord alerts.
Send alerts to Discord channels.
Trigger Slack alerts only for matching submissions.
# Webhook integration (/help/integrations/webhooks)
Send Mokaform submission payloads to your own HTTPS endpoint and process answers, files, metadata, and integrations server-side.
Use webhooks when your own system should receive submission data directly.
## Before you connect [#before-you-connect]
* Prepare an HTTPS endpoint that can receive POST requests.
* Decide how your server will authenticate or verify incoming events.
* Make sure your endpoint can respond quickly with a successful status code.
* Log payloads during testing so you can inspect field names and values.
## Configure a webhook [#configure-a-webhook]
Open the questionnaire and go to the integrations area.
Choose **Webhook**.
Enter the destination URL.
Configure SSL verification and an optional secret if your setup uses one.
Submit a test response.
Confirm your server receives and accepts the payload.
## What to include in your handler [#what-to-include-in-your-handler]
* Validate the request before trusting the payload.
* Return a `2xx` response only after accepting the event.
* Store the submission ID so repeated delivery does not create duplicates.
* Handle missing optional answers.
* Avoid logging sensitive answers in plain text.
## Practical tips [#practical-tips]
* Use a staging endpoint before connecting production systems.
* Keep your handler tolerant of new fields.
* Transform Mokaform answers into your internal schema after receipt.
* Monitor failures and rotate secrets when access changes.
## Troubleshooting [#troubleshooting]
Confirm the URL is reachable over HTTPS, the server accepts the request method, and SSL verification matches your
certificate setup.
Store submission IDs and make your handler idempotent.
Check whether the question was hidden by logic, skipped, or optional for the tested branch.
# Zapier integration (/help/integrations/zapier)
Use Zapier with Mokaform to send form submissions to CRMs, email tools, spreadsheets, notifications, and apps without direct integrations.
Use Zapier when you want Mokaform submissions to trigger workflows across Zapier's app catalog.
## Before you connect [#before-you-connect]
* Decide which app and action Zapier should run after a submission.
* Prepare a Mokaform webhook or supported Zapier entry point.
* Name important questions clearly so mapping is easy in Zapier.
* Use a test submission with realistic data.
## Connect Zapier [#connect-zapier]
In Zapier, create a Zap for the destination workflow.
Choose the Mokaform trigger or webhook trigger available in your setup.
Connect Mokaform by following Zapier's setup instructions.
Submit a test response from Mokaform.
Map the test data into the Zap action fields.
Turn on the Zap and run another test submission.
## Good Zapier use cases [#good-zapier-use-cases]
* Add leads to a CRM.
* Send data to an email marketing platform.
* Create calendar events.
* Add rows to apps without direct Mokaform integrations.
* Send SMS or transactional follow-up through another provider.
## Practical tips [#practical-tips]
* Keep the first Zap simple, then add filters and branching after the base flow works.
* Use Zapier filters when only some submissions should continue.
* Update the Zap after renaming Mokaform questions.
* Check Zapier task history when a workflow does not run.
## Troubleshooting [#troubleshooting]
Confirm the Mokaform trigger or webhook is active and submit a new completed response.
Send a fresh test response that answers the relevant question on the correct logic branch.
Check required fields, connected account permissions, and destination app limits in Zapier.
# Cookie Policy (/help/resources/cookie-policy)
Read how Mokaform uses cookies and similar technologies across the website, application, hosted forms, analytics, and media features.
Last updated: July 8, 2026
This page explains Mokaform's use of cookies and similar technologies in a
practical format. The formal Cookie Policy is available at [Mokaform Cookie
Policy](/cookie).
## 2-minute summary [#2-minute-summary]
Mokaform uses cookies and similar technologies to operate the website and application, remember preferences, measure usage, and keep the service secure.
What you should know:
* Strictly necessary cookies are used to make the site and service work.
* Optional cookies are used only where permitted by law and controlled through the cookie banner where available.
* You can accept, reject, or change optional cookie choices through the cookie banner and cookie preferences link.
* Mokaform does not sell personal data.
* Mokaform does not use form responses or uploaded files for targeted advertising.
* Mokaform uses analytics tools such as Google Analytics and Segment to understand website and product usage.
* Mokaform uses an EU-hosted Logto tenant for authentication.
* Klipy, Pexels, and Unsplash are optional media content providers used server-side for GIFs, videos, and photos. They are not used as browser-side cookie providers in Mokaform's current architecture.
* More detail about personal data processing is available in the [Privacy Policy](/privacy) and [Privacy Notice](/help/resources/privacy-policy).
## Article 1 - What are cookies? [#article-1---what-are-cookies]
Cookies are small text files stored in your browser or device when you visit a website or use an online service.
Similar technologies include local storage, pixels, tags, SDKs, and other browser or device storage technologies. In this page, "cookies" refers to cookies and similar technologies together.
Cookies can help a service:
* keep you signed in;
* remember your preferences;
* protect accounts and forms from abuse;
* understand how visitors use the website;
* measure performance and errors; and
* improve the product.
## Article 2 - Where Mokaform uses cookies [#article-2---where-mokaform-uses-cookies]
Mokaform may use cookies on:
* [www.mokaform.com](https://www.mokaform.com/);
* the Mokaform application;
* forms hosted through Mokaform;
* account and authentication flows;
* help, support, and documentation pages; and
* checkout or payment flows provided by payment partners.
Some cookies are set by Mokaform. Others are set by service providers that help us operate, secure, analyze, or improve Mokaform.
## Article 3 - Cookie categories [#article-3---cookie-categories]
### 3.1 Strictly necessary cookies [#31-strictly-necessary-cookies]
These cookies are required for the website and service to work. They may support security, authentication, session management, load balancing, consent storage, fraud prevention, and basic service delivery.
Because these cookies are necessary, they cannot usually be disabled through the cookie banner. You can block them in your browser, but parts of Mokaform may stop working.
Examples include:
| Purpose | Examples |
| ----------------------------- | ----------------------------------------------------------------------- |
| Authentication and sessions | Keeping users signed in, securing access, and managing account sessions |
| Consent preferences | Remembering whether you accepted or rejected optional cookies |
| Security and abuse prevention | Detecting suspicious activity, spam, misuse, or unauthorized access |
| Service delivery | Routing traffic, loading pages, and operating forms |
### 3.2 Analytics cookies [#32-analytics-cookies]
Analytics cookies help us understand how people use the website and service, which pages are useful, whether features work correctly, and where performance can be improved.
Mokaform may use analytics tools such as Google Analytics and Segment. These tools may process identifiers, page views, device information, browser information, approximate location, referral source, and usage events.
Analytics cookies are optional where consent is required.
### 3.3 Functional and personalization cookies [#33-functional-and-personalization-cookies]
Functional cookies remember choices you make, such as language, interface preferences, or settings that improve your experience.
These cookies are optional where consent is required. If you reject them, Mokaform should still work, but some preferences may not be remembered.
### 3.4 Marketing cookies [#34-marketing-cookies]
Mokaform does not use form responses or uploaded files for targeted advertising.
If Mokaform uses marketing cookies on the website, they will be used only where permitted by law and controlled through the cookie banner where available. Marketing cookies may help measure campaigns or understand how visitors arrive at Mokaform.
## Article 4 - Providers [#article-4---providers]
Mokaform may use the following providers in connection with cookies, analytics, authentication, monitoring, or related online technologies.
| Provider | Purpose | Region | Link |
| ---------------------------------------- | ------------------------------------------------------------------------ | ------ | ------------------------------------------------------------ |
| Logto, Inc. | Authentication and account access for Mokaform's EU tenant | EU | [Learn more](https://logto.io/legal/privacy-policy) |
| Google Analytics | Website analytics | US | [Learn more](https://policies.google.com/privacy) |
| Segment.io, Inc. | Product and website analytics routing | US | [Learn more](https://segment.com/legal/privacy/) |
| Sentry.io | Error tracking, monitoring, performance diagnostics, and crash reporting | US | [Learn more](https://sentry.io/legal/dpa/) |
| Render Services, Inc. | Hosting, networking, deployment, and runtime logs | EU | [Learn more](https://render.com/dpa) |
| Amazon Web Services, Inc. and affiliates | Storage, file uploads, email, backups, and infrastructure services | EU | [Learn more](https://aws.amazon.com/compliance/gdpr-center/) |
| Stripe, Inc. and affiliates | Payment processing for paid plans and payment-enabled forms | US | [Learn more](https://stripe.com/privacy) |
For the broader provider and subprocessor list, see [GDPR & Mokaform](/help/resources/gdpr).
### 4.1 Media providers [#41-media-providers]
Mokaform also uses Klipy, Pexels, and Unsplash to provide optional media search in the form builder:
| Provider | Purpose | Region | Link |
| ---------------------------------- | -------------------------------------- | ------ | ------------------------------------------------------ |
| Kikliko, Inc. (Klipy) | GIF search and media library content | US | [Learn more](https://klipy.com/support/privacy-policy) |
| Pexels, a Canva Germany GmbH brand | Video search and media library content | EU | [Learn more](https://www.pexels.com/privacy-policy/) |
| Unsplash Inc. | Photo search and media library content | US | [Learn more](https://unsplash.com/privacy) |
These integrations are handled server-side by Mokaform. They are disclosed here for transparency, but they do not set cookies in a respondent's browser through Mokaform and do not receive respondent IP addresses, browser metadata, or form submissions from the respondent's browser as part of Mokaform's current media search architecture.
## Article 5 - Consent and choices [#article-5---consent-and-choices]
Where required by law, Mokaform asks for your consent before setting optional cookies.
You can:
* accept optional cookies;
* reject optional cookies;
* choose cookie categories where available;
* change your choices through the cookie preferences link in the footer; and
* manage or delete cookies through your browser settings.
Rejecting optional cookies does not prevent you from using the core website or service, although some preferences or measurements may be limited.
## Article 6 - Browser controls [#article-6---browser-controls]
Most browsers let you block, delete, or limit cookies. Your browser settings may also let you block third-party cookies or clear cookies when you close the browser.
If you block all cookies, authentication, form editing, account access, preference storage, or other service features may not work correctly.
## Article 7 - Retention [#article-7---retention]
Cookie retention depends on the cookie type and provider.
Typical retention practices include:
| Cookie type | Retention approach |
| ---------------------- | ------------------------------------------------------------ |
| Session cookies | Usually deleted when the browser session ends |
| Consent cookies | Kept for a limited period so we can remember your choice |
| Authentication cookies | Kept for the session or account access period |
| Analytics cookies | Kept according to provider settings and your consent choices |
| Security cookies | Kept for the period needed to protect the service |
## Article 8 - International transfers [#article-8---international-transfers]
Mokaform is based in FR and uses EU infrastructure for hosting, storage, file uploads, and email.
Some cookie or analytics providers are located in the US or may process personal data outside the EU. Where applicable law requires transfer safeguards, Mokaform relies on appropriate mechanisms such as data processing agreements, Standard Contractual Clauses, adequacy decisions, and supplementary measures where appropriate.
## Article 9 - Updates [#article-9---updates]
We may update this Cookie Policy from time to time. If we make material changes, we will update this page and may notify customers through the service or by email where appropriate.
## Useful links [#useful-links]
* [Mokaform Cookie Policy](/cookie)
* [Mokaform Privacy Policy](/privacy)
* [Mokaform Privacy Notice](/help/resources/privacy-policy)
* [GDPR & Mokaform](/help/resources/gdpr)
* [Mokaform Data Processing Agreement](/help/resources/data-processing-agreement)
* [CNIL: Cookies and trackers](https://www.cnil.fr/en/cookie-regulation-cnil-continuing-action-plan-initiated-2019-and-has-imposed-two-fines-shein-and)
# Data Processing Agreement (/help/resources/data-processing-agreement)
Review the Mokaform Data Processing Agreement for business customers processing form responses and personal data.
Last updated: July 8, 2026
This Data Processing Agreement ("DPA") forms part of the agreement between Mokaform SAS, located at 61 RUE de Lyon, 75012 Paris, France ("Mokaform", "Processor", "we", "us", or "our"), and the customer using Mokaform's services ("Customer", "Controller", or "you").
This DPA applies when Mokaform processes Personal Data on behalf of Customer in connection with the Mokaform form builder, form hosting, response collection, storage, export, notification, integration, and related services (the "Services").
## 1. Definitions [#1-definitions]
For this DPA:
* "Agreement" means the Mokaform Terms of Service, an applicable order form, or another written agreement governing Customer's use of the Services.
* "Applicable Data Protection Laws" means data protection and privacy laws that apply to the processing of Personal Data under this DPA, including Regulation (EU) 2016/679 (the "GDPR") where applicable.
* "Controller", "Processor", "Data Subject", "Personal Data", "Personal Data Breach", "processing", and "Supervisory Authority" have the meanings given in the GDPR.
* "Customer Data" means data submitted to, collected through, stored in, or otherwise processed by the Services on behalf of Customer, including form responses and uploaded files.
* "Subprocessor" means another processor engaged by Mokaform to process Personal Data on behalf of Customer.
* "Technical and Organizational Measures" or "TOMs" means the security measures described in Schedule 2 and any additional measures Mokaform makes available.
Terms not defined in this DPA have the meanings given in the Agreement.
## 2. Roles of the parties [#2-roles-of-the-parties]
For Customer Data processed through forms created or managed by Customer:
* Customer is the Controller or Processor, as applicable to Customer's own relationship with Data Subjects.
* Mokaform is the Processor or Subprocessor, as applicable, processing Customer Data on behalf of Customer.
For account registration, billing, website analytics, product analytics, support, fraud prevention, service administration, and security data that Mokaform determines how and why to process, Mokaform acts as an independent Controller. That processing is described in the [Mokaform Privacy Policy](/privacy).
## 3. Subject matter and purpose [#3-subject-matter-and-purpose]
Mokaform will process Personal Data only to provide, secure, maintain, support, and improve the Services, and only as instructed by Customer through:
* the Agreement;
* this DPA;
* Customer's use and configuration of the Services;
* documented support requests; and
* other written instructions agreed by the parties.
The details of processing are described in Schedule 1.
## 4. Customer instructions [#4-customer-instructions]
Mokaform will process Personal Data only on documented instructions from Customer unless required to do otherwise by EU law, Member State law, or other law applicable to Mokaform. If such legal requirement applies, Mokaform will inform Customer before processing unless the law prohibits notice on important public interest grounds.
Mokaform will promptly inform Customer if, in Mokaform's opinion, an instruction infringes Applicable Data Protection Laws.
Customer is responsible for ensuring that its instructions are lawful and that Customer has all notices, consents, lawful bases, and rights required to collect and process Personal Data through the Services.
## 5. Confidentiality [#5-confidentiality]
Mokaform will ensure that personnel authorized to process Personal Data are bound by confidentiality obligations or are under an appropriate statutory duty of confidentiality.
Mokaform will limit personnel access to Personal Data to those who need access to provide, support, secure, or maintain the Services.
## 6. Security [#6-security]
Mokaform will implement and maintain appropriate Technical and Organizational Measures designed to protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or unauthorized access.
The current TOMs are described in Schedule 2. Mokaform may update its TOMs over time, provided that updates do not materially reduce the overall level of protection for Personal Data processed under this DPA.
Customer is responsible for securely configuring its account, forms, integrations, exports, notifications, users, and access permissions.
## 7. Subprocessors [#7-subprocessors]
Customer gives Mokaform general written authorization to engage Subprocessors for the purposes described in this DPA.
Mokaform will:
* maintain a public or otherwise available list of material Subprocessors;
* impose data protection obligations on Subprocessors that are no less protective in substance than those in this DPA;
* remain responsible for Subprocessors' performance of their data protection obligations where required by Applicable Data Protection Laws; and
* notify Customer of material Subprocessor changes through the Services, the GDPR resource page, email, or another reasonable channel.
Customer may object to a new Subprocessor on reasonable data protection grounds by contacting [security@mokaform.com](mailto:security@mokaform.com) within 30 days after notice. If the parties cannot resolve the objection, Customer may stop using the affected Services and terminate the affected portion of the Agreement according to the Agreement.
## 8. Assistance with Customer obligations [#8-assistance-with-customer-obligations]
Taking into account the nature of processing and the information available to Mokaform, Mokaform will provide reasonable assistance to Customer with:
* responding to Data Subject requests;
* meeting security obligations under Applicable Data Protection Laws;
* performing data protection impact assessments where the processing by Mokaform is relevant;
* consulting with Supervisory Authorities where legally required; and
* documenting compliance with this DPA.
Mokaform may charge reasonable fees for assistance that requires significant work outside standard product functionality or support.
## 9. Data Subject requests [#9-data-subject-requests]
If Mokaform receives a request from a Data Subject relating to Personal Data processed on behalf of Customer, Mokaform will, where legally permitted, direct the Data Subject to Customer or notify Customer.
Mokaform will not respond to such request on Customer's behalf unless Customer instructs Mokaform to do so or Mokaform is legally required to respond.
## 10. Personal Data Breach [#10-personal-data-breach]
Mokaform will notify Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Data.
Where available, Mokaform's notice will describe:
* the nature of the Personal Data Breach;
* the categories and approximate number of affected Data Subjects;
* the categories and approximate number of affected records;
* likely consequences;
* measures taken or proposed to address the breach; and
* measures proposed to mitigate possible adverse effects.
Mokaform's notice is not an admission of fault or liability. Customer is responsible for determining whether it must notify a Supervisory Authority or affected Data Subjects.
## 11. Audits and information [#11-audits-and-information]
Mokaform will make available information reasonably necessary to demonstrate compliance with this DPA.
Customer may request an audit no more than once per calendar year, unless a Personal Data Breach or material non-compliance gives Customer a reasonable basis for an additional audit.
Audits must:
* be conducted during normal business hours;
* be subject to reasonable confidentiality obligations;
* avoid disruption to Mokaform's business and other customers;
* be limited to systems, records, and personnel relevant to Customer's Personal Data; and
* be performed by Customer or an independent auditor that is not a Mokaform competitor.
Customer will bear audit costs unless the audit reveals material non-compliance by Mokaform with this DPA.
## 12. International transfers [#12-international-transfers]
Mokaform and its Subprocessors may process Personal Data in countries outside the European Economic Area.
Where a transfer mechanism is required by Applicable Data Protection Laws, Mokaform will rely on one or more appropriate safeguards, including:
* an adequacy decision;
* the European Commission Standard Contractual Clauses adopted under Commission Implementing Decision (EU) 2021/914;
* the United Kingdom International Data Transfer Addendum or other applicable UK transfer mechanism;
* another lawful transfer mechanism; and
* supplementary measures where appropriate.
For transfers from Customer to Mokaform or from Mokaform to Subprocessors that require the EU Standard Contractual Clauses, the relevant modules and annex details are incorporated by reference as described in Schedule 4 unless the parties execute a separate transfer agreement.
## 13. Return and deletion [#13-return-and-deletion]
During the term of the Agreement, Customer may access, export, and delete Customer Data using available product functionality.
After termination or expiry of the Agreement, Mokaform will delete or return Personal Data according to the Agreement, Customer's instructions, and Mokaform's standard deletion and backup lifecycle, unless applicable law requires continued storage.
Deleted Customer Data may remain in backups for a limited period until overwritten or deleted through standard backup rotation. Mokaform will protect backup data under this DPA while retained.
## 14. Customer responsibilities [#14-customer-responsibilities]
Customer is responsible for:
* deciding what Personal Data to collect through forms;
* providing required notices to Data Subjects;
* obtaining and documenting any required consent;
* selecting a lawful basis for processing;
* honoring Data Subject rights;
* configuring form retention, exports, integrations, notifications, and workspace access;
* avoiding unnecessary collection of sensitive or regulated data; and
* ensuring Customer's use of the Services complies with Applicable Data Protection Laws.
Customer will not instruct Mokaform to process Personal Data in a way that violates Applicable Data Protection Laws.
## 15. Government and legal requests [#15-government-and-legal-requests]
If Mokaform receives a legally binding request from a public authority for Personal Data processed on behalf of Customer, Mokaform will, where legally permitted:
* promptly notify Customer;
* review the request for legal validity;
* disclose only the Personal Data legally required; and
* reasonably cooperate with Customer's lawful efforts to challenge or narrow the request.
## 16. Liability [#16-liability]
Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Agreement, unless Applicable Data Protection Laws require otherwise.
Nothing in this DPA limits liability that cannot legally be limited.
## 17. Term [#17-term]
This DPA begins when Mokaform first processes Personal Data on behalf of Customer and continues while Mokaform processes Personal Data on behalf of Customer.
## 18. Changes [#18-changes]
Mokaform may update this DPA from time to time. If an update materially reduces Customer's rights or Mokaform's obligations, Mokaform will provide reasonable notice. Continued use of the Services after the effective date of an updated DPA constitutes acceptance unless the Agreement provides another process.
## Schedule 1 - Details of processing [#schedule-1---details-of-processing]
| Item | Description |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Subject matter | Processing Personal Data to provide Mokaform's form builder, hosting, response collection, storage, export, notification, integration, analytics, support, security, and related services. |
| Duration | For the term of the Agreement and until Personal Data is deleted or returned according to the Agreement, this DPA, and applicable law. |
| Nature of processing | Collection, recording, organization, structuring, storage, retrieval, consultation, use, transmission, disclosure by transmission, restriction, erasure, and destruction. |
| Purpose | Providing, securing, maintaining, supporting, and improving the Services. |
| Data Subjects | Customer users, workspace members, form respondents, people whose data is included in form responses, support contacts, and other individuals whose Personal Data is submitted to the Services by Customer. |
| Categories of Personal Data | Account data, contact details, identifiers, authentication data, billing-related data, form questions, form responses, uploaded files, signatures, payment-related form data, respondent metadata, respondent country metadata, usage data, device and log data, support communications, integration data, and any other Personal Data Customer chooses to submit to the Services. |
| Sensitive data | The Services are not intended for unnecessary collection of special categories of Personal Data. Customer is responsible for determining whether it collects sensitive data and for ensuring a valid lawful basis and safeguards. |
| Frequency | Continuous while Customer uses the Services. |
## Schedule 2 - Technical and organizational measures [#schedule-2---technical-and-organizational-measures]
Mokaform maintains measures designed to protect Personal Data, including:
### Governance [#governance]
* Internal responsibility for privacy and security.
* Vendor review for service providers that may process Personal Data.
* Contractual confidentiality and data protection commitments.
### Access control [#access-control]
* Least-privilege access to production systems.
* Role-based access controls where appropriate.
* Authentication controls for personnel and users.
* Periodic review of access where appropriate.
### Data protection [#data-protection]
* HTTPS/TLS encryption in transit.
* Encryption at rest where supported by infrastructure and storage providers.
* Logical separation of customer workspaces and records.
* Controls designed to prevent unauthorized access, disclosure, alteration, or deletion.
### Operations [#operations]
* Monitoring and logging for reliability, abuse prevention, and security.
* Backup and recovery practices.
* Vulnerability review and remediation practices.
* Incident response procedures.
### Personnel [#personnel]
* Confidentiality obligations for personnel.
* Access limited to personnel with a business need.
* Security and privacy guidance for personnel handling Personal Data.
### Subprocessor management [#subprocessor-management]
* Review of subprocessors that process Personal Data.
* Written data protection terms with subprocessors where required.
* Transfer safeguards for international processing where required.
## Schedule 3 - Subprocessors [#schedule-3---subprocessors]
Mokaform's current subprocessor information is published on the [GDPR & Mokaform](/help/resources/gdpr) page.
Customer authorizes Mokaform to use the subprocessors listed there and subprocessors performing materially similar functions, subject to the notice and objection process in this DPA.
## Schedule 4 - International transfer clauses [#schedule-4---international-transfer-clauses]
Where the EU Standard Contractual Clauses are required for a transfer of Personal Data under this DPA:
* Module Two applies where Customer is a controller and Mokaform is a processor.
* Module Three applies where Customer is a processor and Mokaform is a subprocessor.
* Clause 7, the optional docking clause, is included.
* Clause 9, Option 2, general written authorization for subprocessors, applies with the notice period described in this DPA.
* Clause 17 is governed by the law of France unless another EU Member State law is required.
* Clause 18 courts are the courts of France unless another competent forum is required.
* Annex I details are completed by the information in the Agreement, this DPA, and Schedule 1.
* Annex II details are completed by the TOMs in Schedule 2.
* Annex III details are completed by the subprocessor list referenced in Schedule 3.
If the United Kingdom International Data Transfer Addendum or another transfer mechanism is required, the parties will apply the relevant mechanism in a manner consistent with this DPA and the Agreement.
# Fair Use Policy (/help/resources/fair-use-policy)
Understand Mokaform fair-use signals, extensive usage thresholds, review steps, and service reliability commitments.
Mokaform is designed to be generous by default. This Fair Use Policy keeps things simple while protecting performance
for everyone. Most teams will never reach these limits. If sustained usage suggests youโve outgrown our standard
plans, weโll work with you on a tailored plan โ no surprise paywalls or throttling.
## Summary [#summary]
* Most customers never hit these limits.
* We look at sustained patterns over time, not one-off spikes.
* If you consistently exceed the signals below for 3โ4 months, weโll suggest a custom plan to keep everything running smoothly.
### Who this applies to [#who-this-applies-to]
This policy applies to all Mokaform plans. Itโs designed to keep the experience fast and reliable for everyone while giving high-growth teams room to scale.
## When usage becomes โextensiveโ [#when-usage-becomes-extensive]
These are practical signal posts. Occasional spikes are fine. What matters is steady load over time.
| Area | Signal of extensive usage |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Submission volume | About 20,000+ submissions per month for 3โ4 consecutive months |
| File intake | Roughly 100 GB per month, or 500 GB total stored files over multiple months |
| Notifications | Around 40,000+ email notifications per month for multiple months |
| Account sharing | Mokaform Pro is licensed for a single organization. Sharing premium features outside your company isnโt allowed and may lead to suspension or termination. |
### What โconsistentโ means [#what-consistent-means]
A steady pattern over time matters more than a spike. If we see elevated usage for 3โ4 consecutive months, weโll reach out with options so your workflows stay fast and reliable.
## What happens if you exceed the signals [#what-happens-if-you-exceed-the-signals]
* Weโll contact your billing owner with recent usage insights and options.
* Weโll propose a custom plan sized to your observed patterns. Billing occurs quarterly at the start of each quarter and is added to your current subscription.
* If a custom plan isnโt a fit, weโll provide reasonable time to migrate with minimal disruption. No surprise throttling.
### Examples [#examples]
A 2-week spike above thresholds โ **no action**. Spikes alone donโt trigger changes.
Submissions and notifications stay elevated for four straight months โ weโll recommend a custom plan so performance
remains predictable.
## FAQs [#faqs]
No. Weโll reach out first and work with you on options rather than abruptly throttle.
No. They are guidance signals that prompt a conversation if sustained.
Let us know in advance and weโll make sure your forms stay fast. [**Contact us**](mailto:contact@mokaform.com).
## Definitions [#definitions]
* **Submissions:** completed form responses received by Mokaform.
* **File intake:** the total size of files uploaded through your forms that are stored with Mokaform.
* **Notifications:** system-sent emails triggered by form activity.
## Our commitment [#our-commitment]
* Keep pricing clear and predictable.
* Prioritize performance and reliability for all customers.
* Partner with high-growth teams to scale responsibly.
# GDPR and Mokaform (/help/resources/gdpr)
Learn how Mokaform approaches GDPR, form response data, subprocessors, controller and processor roles, and data subject rights.
This page is for general information only and is not legal advice. You should
work with your legal advisor to decide how GDPR applies to your organization
and your forms.
## Overview [#overview]
Mokaform is operated by Mokaform SAS, a French company located at 61 RUE de Lyon, 75012 Paris, France. Because Mokaform is based in the European Union, we build our service around European privacy and data protection expectations.
This page explains how Mokaform approaches GDPR for customers who create forms, respondents who submit forms, and people who use the Mokaform website or product.
## What is GDPR? [#what-is-gdpr]
The General Data Protection Regulation, or GDPR, is the European Union data protection law that governs how personal data is collected, used, stored, shared, protected, and deleted.
GDPR may apply to you if your organization is based in the European Union, if you offer goods or services to people in the European Union, or if your forms collect personal data from people in the European Union.
## Is Mokaform GDPR compliant? [#is-mokaform-gdpr-compliant]
Mokaform is designed to support GDPR-compliant use by our customers.
Our main commitments are:
* We do not sell personal data.
* We process customer form response data to provide the Mokaform service.
* We use technical and organizational safeguards to protect personal data.
* We support export and deletion workflows for form responses.
* We make a [Data Processing Agreement](/help/resources/data-processing-agreement) available for business customers.
* We require subprocessors that process personal data for Mokaform to protect that data under appropriate contractual terms.
Mokaform can help you run GDPR-aware forms, but you remain responsible for your own forms, notices, lawful basis, consent choices, data retention, and respondent requests.
## Do you have a Data Processing Agreement? [#do-you-have-a-data-processing-agreement]
Yes. Mokaform provides a [Data Processing Agreement](/help/resources/data-processing-agreement) for customers who use Mokaform as a business, organization, or professional user.
Unless a separately signed agreement says otherwise, the DPA forms part of the customer agreement when Mokaform processes personal data on behalf of a customer.
## Who is the controller and who is the processor? [#who-is-the-controller-and-who-is-the-processor]
For form responses collected through your forms:
* You, the form creator or customer, are generally the controller. You decide what data to collect, why you collect it, who receives it, and how long it should be kept.
* Mokaform is generally the processor. We host, store, transmit, and otherwise process form response data to provide the service to you.
For account, billing, support, security, analytics, and website data about Mokaform customers and visitors, Mokaform generally acts as a controller. More detail is available in our [Privacy Policy](/privacy).
## What happens with form response data? [#what-happens-with-form-response-data]
Mokaform does not own the responses submitted through your forms. The customer who created the form controls that data.
As a form creator, you are responsible for:
* Telling respondents what data you collect and why.
* Choosing an appropriate lawful basis for collection.
* Avoiding unnecessary personal data.
* Exporting, deleting, or retaining responses according to your own legal obligations.
* Responding to respondent requests when GDPR or other privacy laws apply.
Mokaform helps by providing product controls to access, export, and delete responses. Mokaform stores response data and uploaded files in AWS regions located in the European Union. Mokaform may derive respondent country locally from IP address using GeoLite2 data created by MaxMind. We do not share respondent IP addresses with MaxMind or another third-party geolocation provider for this lookup, and we do not derive city, precise location, or individual-level inferences from GeoLite2 data. When you delete response data from Mokaform, we remove it from active systems and delete remaining backup copies according to our normal backup lifecycle, unless we must keep limited data for legal, security, or fraud-prevention reasons.
## How does Mokaform use customer personal data? [#how-does-mokaform-use-customer-personal-data]
Mokaform uses customer account and usage data to:
* Create and manage accounts.
* Provide, secure, monitor, and improve the service.
* Process billing and subscriptions.
* Respond to support requests.
* Send service notices and transactional messages.
* Detect abuse, fraud, and security issues.
* Comply with legal obligations.
Mokaform does not sell personal data and does not use form response data to target advertising.
## Security measures [#security-measures]
Mokaform applies security measures appropriate to the nature of the service and the data processed, including:
* Encryption in transit using HTTPS/TLS.
* Access controls based on least privilege.
* Authentication and account security controls.
* Environment separation and restricted production access.
* Logging, monitoring, and security review processes.
* Backup and recovery practices.
* Vendor review for services that may process personal data.
* Confidentiality obligations for personnel and service providers.
Customers are responsible for configuring their forms appropriately, limiting access to their workspace, choosing what data to collect, and avoiding collection of sensitive data unless they have a valid legal basis and adequate safeguards.
## Subprocessors [#subprocessors]
Mokaform uses subprocessors to provide hosting, storage, authentication, payments, analytics, monitoring, customer support, and related service operations.
| Provider or category | Purpose | Region | May process form submissions | Link |
| --------------------------------------------------------- | ------------------------------------------------------------------------------------ | ------ | ---------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| Render Services, Inc. | Application and website hosting, deployment, networking, and runtime logs | EU | Yes, for traffic, logs, and hosted application processing | [Learn more](https://render.com/dpa) |
| Amazon Web Services, Inc. and affiliates | Storage, backups, file uploads, and related infrastructure services | EU | Yes | [Learn more](https://aws.amazon.com/compliance/gdpr-center/) |
| Logto, Inc. | Authentication and account access for Mokaform's EU tenant | EU | No | [Learn more](https://logto.io/legal/privacy-policy) |
| Stripe, Inc. and affiliates | Payment processing for paid plans and payment forms | US | Only for payment-related form data when payment features are used | [Learn more](https://stripe.com/privacy) |
| Segment.io, Inc. | Product and website analytics routing | US | No | [Learn more](https://segment.com/legal/privacy/) |
| Sentry.io | Error tracking, application monitoring, performance diagnostics, and crash reporting | US | No by default, except limited technical metadata and error context where necessary | [Learn more](https://sentry.io/legal/dpa/) |
| Google Analytics | Website analytics | US | No | [Learn more](https://policies.google.com/privacy) |
| Amazon Web Services, Inc. and affiliates (email services) | Transactional emails and optional form notifications | EU | Yes, if a customer includes response data in email notifications | [Learn more](https://aws.amazon.com/compliance/gdpr-center/) |
| Kikliko, Inc. (Klipy) | Optional GIF search and media library content, requested server-side by Mokaform | US | No | [Learn more](https://klipy.com/support/privacy-policy) |
| Pexels, a Canva Germany GmbH brand | Optional video search and media library content, requested server-side by Mokaform | EU | No | [Learn more](https://www.pexels.com/privacy-policy/) |
| Unsplash Inc. | Optional photo search and media library content, requested server-side by Mokaform | US | No | [Learn more](https://unsplash.com/privacy) |
We require subprocessors to process personal data only for the services they provide to Mokaform and to protect that data under appropriate contractual, security, and transfer safeguards.
MaxMind GeoLite2 is used as a local country lookup database, not as a request-based geolocation provider. Mokaform does not send respondent IP addresses to MaxMind for country detection, so MaxMind is not listed above as a subprocessor for that lookup.
For Klipy, Pexels, and Unsplash, Mokaform sends media search requests from Mokaform's servers. These providers do not receive respondent IP addresses, browser metadata, or form submissions from the respondent's browser as part of Mokaform's current media search architecture.
## International transfers [#international-transfers]
Some Mokaform subprocessors are located outside the European Economic Area or may process data from outside the EEA.
Where GDPR requires transfer safeguards, Mokaform relies on appropriate mechanisms such as adequacy decisions, the European Commission Standard Contractual Clauses, or equivalent transfer safeguards, together with supplementary measures where appropriate.
## Data subject requests [#data-subject-requests]
If a respondent contacts Mokaform about a form response, we will generally direct them to the customer that created the form, because that customer controls the form response data.
If you are a Mokaform customer and need help responding to a GDPR request, contact us at [security@mokaform.com](mailto:security@mokaform.com). We will provide reasonable assistance where the request relates to personal data Mokaform processes on your behalf.
## Useful links [#useful-links]
* [Mokaform Data Processing Agreement](/help/resources/data-processing-agreement)
* [Mokaform Privacy Policy](/privacy)
* [Mokaform Terms of Service](/terms)
* [Mokaform Fair Use Policy](/help/resources/fair-use-policy)
* [European Commission: data protection](https://commission.europa.eu/law/law-topic/data-protection_en)
* [European Commission: Standard Contractual Clauses Q\&A](https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/new-standard-contractual-clauses-questions-and-answers-overview_en)
* [CNIL guidelines and recommendations](https://www.cnil.fr/en/guidelines-and-recommendations)
# Privacy, compliance, and policy resources (/help/resources)
Find Mokaform GDPR information, privacy notices, cookie policy, Data Processing Agreement, fair-use policy, and abuse reporting.
Privacy language can feel complicated. These resources explain how Mokaform handles privacy, GDPR, data processing, legal notices, and platform policies.
## ๐ Find the right resource [#-find-the-right-resource]
Learn how Mokaform approaches GDPR, controller and processor roles,
subprocessors, and respondent rights.
Review Mokaform's DPA for customers processing personal data.
Read how Mokaform handles account, website, support, and service data.
Understand cookie categories and choices.
Report malicious, fraudulent, illegal, or abusive forms hosted on Mokaform.
Open the terms, privacy notices, cookie information, and Data Processing
Agreement.
Understand the usage signals that keep Mokaform fast and fair for everyone.
# Privacy Notice (/help/resources/privacy-policy)
Read how Mokaform collects, uses, protects, shares, and retains personal data for account holders, form creators, visitors, and respondents.
Last updated: July 8, 2026
This page explains Mokaform's privacy practices in a practical format. The
formal legal policy is available at [Mokaform Privacy Policy](/privacy).
## 2-minute summary [#2-minute-summary]
Mokaform SAS is a French company located at 61 RUE de Lyon, 75012 Paris, France. We provide a form builder for creating, publishing, and managing online forms.
What you should know:
* You remain in control of the forms you create and the responses you collect.
* We do not sell personal data.
* We do not use form responses or uploaded files for targeted advertising.
* Mokaform stores response data and uploaded files in AWS regions located in the European Union.
* Mokaform hosts the application in EU Render regions.
* Mokaform may use GeoLite2 data locally to determine a respondent's country from their IP address. We do not share the IP address with MaxMind for this lookup, and we do not derive city, precise location, or individual-level inferences from GeoLite2 data.
* We use service providers only to operate, secure, support, and improve Mokaform.
* Optional media search for GIFs, videos, and photos is handled server-side through media providers. Those providers do not receive respondent IP addresses, browser metadata, or form submissions from the respondent's browser.
* You can request access, correction, deletion, restriction, portability, or objection by contacting [security@mokaform.com](mailto:security@mokaform.com).
* If you create forms, you are generally responsible for telling respondents what you collect and why.
## Article 1 - General [#article-1---general]
Mokaform SAS ("Mokaform", "we", "us", or "our") operates [www.mokaform.com](https://www.mokaform.com/) and provides services for building dynamic, multi-step web forms, collecting responses, managing submissions, sending notifications, and connecting form data to other tools.
This Privacy Notice applies to:
* visitors to the Mokaform website;
* people who create or manage a Mokaform account;
* workspace members invited by a Mokaform customer;
* people who contact Mokaform for support, sales, security, or privacy matters; and
* respondents whose personal data is submitted through forms hosted by Mokaform.
For customer form responses, the form creator is generally the controller and Mokaform is generally the processor. More detail is available in [GDPR & Mokaform](/help/resources/gdpr) and the [Data Processing Agreement](/help/resources/data-processing-agreement).
## Article 2 - What personal data Mokaform collects [#article-2---what-personal-data-mokaform-collects]
Mokaform may collect and process the following categories of personal data.
| Category | Examples | Context |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Account and identity data | Name, email address, login identifiers, workspace membership, role, account settings | When you create an account, log in, join a workspace, or manage your profile |
| Authentication data | Authentication events, session data, tenant identifiers, security logs | When you access Mokaform through our Logto EU tenant |
| Billing data | Subscription plan, invoices, billing contact details, VAT or tax information, payment status | When you subscribe to a paid plan or use paid features |
| Payment data | Payment method details and transaction metadata handled by Stripe | When you pay for a subscription or collect payments through a form |
| Product usage data | Features used, forms created, submission counts, workspace activity, settings, device data, browser data, IP address, country-level location signals, logs | When you use the website, dashboard, editor, forms, or related services |
| Support data | Messages, attachments, diagnostic information, contact details | When you contact support, security, sales, or privacy teams |
| Form content and responses | Form questions, hidden fields, uploaded files, signatures, answers, respondent metadata, respondent country metadata, and integrations configured by the form creator | When a customer creates a form or a respondent submits a form |
| Local country lookup data | IP address processed locally to derive respondent country only; no city, precise location, or individual-level inference | When a respondent submits a form where country detection is used |
| Media search and selection data | Search terms, selected media identifiers, media URLs, provider attribution, and related technical API data | When a customer searches for or selects GIFs, videos, or photos from Mokaform's media library |
| Cookie and marketing preference data | Cookie consent choices, analytics identifiers, campaign source, unsubscribe status | When you browse the site or interact with marketing communications |
We ask customers not to collect unnecessary sensitive personal data through Mokaform unless they have a valid legal basis and appropriate safeguards.
## Article 3 - Legal bases and purposes [#article-3---legal-bases-and-purposes]
We process personal data only when we have a lawful basis and a defined purpose.
### 3.1 Providing Mokaform [#31-providing-mokaform]
| Data | Legal basis | Purpose |
| ------------------------------- | ------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Account and identity data | Contract | Create and manage accounts, workspaces, authentication, access permissions, and user settings |
| Form content and response data | Customer instructions; contract; legitimate interest in service operation | Host forms, collect responses, store submissions, process file uploads, show dashboards, export data, and run integrations |
| Billing and payment data | Contract; legal obligation | Process subscriptions, invoices, taxes, payment disputes, refunds, and accounting records |
| Product usage and log data | Legitimate interest; contract | Operate, monitor, troubleshoot, secure, and improve the service |
| Support data | Contract; legitimate interest | Respond to requests, diagnose issues, investigate abuse, and improve support |
| Local country lookup data | Customer instructions; contract; legitimate interest in service operation | Determine respondent country at country level only, without sharing the respondent's IP address with MaxMind or another third-party geolocation provider |
| Media search and selection data | Contract; legitimate interest | Provide optional GIF, video, and photo search in the form builder, return selected media, keep provider attribution, and troubleshoot media features |
### 3.2 Security and abuse prevention [#32-security-and-abuse-prevention]
We process limited data to protect Mokaform, customers, respondents, and the public from fraud, spam, misuse, unauthorized access, security incidents, and violations of our terms.
This may include IP addresses, device details, usage patterns, authentication events, technical logs, and form activity metadata.
### 3.3 Communications and marketing [#33-communications-and-marketing]
We may send transactional emails about your account, security, billing, service changes, and forms.
We may also send product updates or marketing communications where permitted by law. You can opt out of non-essential marketing emails by using the unsubscribe link or contacting us.
### 3.4 Cookies and analytics [#34-cookies-and-analytics]
We use cookies and similar technologies to run the site, remember preferences, measure usage, understand performance, and improve Mokaform.
You can manage cookie preferences through the cookie banner where available. More detail is available in the Mokaform Cookie Policy linked from the website footer.
### 3.5 Legal requirements [#35-legal-requirements]
We may process or disclose personal data where necessary to comply with legal obligations, respond to lawful requests, protect rights and safety, enforce our agreements, or support a business transaction such as a merger, acquisition, or asset transfer.
## Article 4 - Service providers and subprocessors [#article-4---service-providers-and-subprocessors]
We use service providers to operate Mokaform. They may process personal data only for the services they provide to us and under appropriate contractual obligations.
Our current subprocessor list is maintained on [GDPR & Mokaform](/help/resources/gdpr). It includes providers for hosting, storage, authentication, payments, email, analytics, monitoring, and diagnostics.
Mokaform also uses optional media content providers for GIF, video, and photo search. These requests are handled by Mokaform server-side. We do not intentionally share respondent IP addresses, browser metadata, or form submissions with Klipy, Pexels, or Unsplash as part of those media search features.
Mokaform may use GeoLite2 data created by MaxMind to determine a respondent's country from their IP address. This lookup is performed locally by Mokaform. We do not share respondent IP addresses with MaxMind or another third-party geolocation provider for this purpose, and we do not derive city, precise location, or individual-level inferences from GeoLite2 data. GeoLite2 attribution is available on our [Attributions](/attributions) page.
We do not sell personal data.
## Article 5 - Retention [#article-5---retention]
We keep personal data only for as long as needed for the purposes described in this notice, unless a longer retention period is required or permitted by law.
Typical retention rules:
| Data | Retention approach |
| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Account data | Kept while your account is active, then deleted or anonymized after account closure according to our deletion process |
| Form responses, respondent country metadata, and uploaded files | Controlled by the form creator; deleted from active systems when the customer deletes them, then removed from backups through normal backup rotation |
| Billing and accounting data | Kept as required for tax, accounting, payment, audit, and legal obligations |
| Support messages | Kept as long as needed to handle the request and maintain support history |
| Security logs | Kept for a limited period needed for security, fraud prevention, investigation, and service reliability |
| Cookie and analytics data | Kept according to cookie settings, consent choices, and provider retention settings |
If we cannot delete data immediately because it is stored in backups, archives, or logs, we continue to protect it and delete it according to the applicable lifecycle.
## Article 6 - Your rights [#article-6---your-rights]
Depending on your location and the type of data involved, you may have rights to:
* access your personal data;
* receive a copy of your personal data;
* correct inaccurate or incomplete data;
* request deletion;
* restrict processing;
* object to processing;
* request portability;
* withdraw consent where processing is based on consent;
* object to direct marketing; and
* file a complaint with a data protection authority.
To exercise your rights, contact [security@mokaform.com](mailto:security@mokaform.com).
If your request concerns a response submitted to a customer form, we may direct you to the form creator because the form creator controls that response data.
We may ask for information needed to verify your identity before acting on a request. If we cannot fulfill a request, for example because we must keep limited data for legal, security, or fraud-prevention reasons, we will explain where required by law.
## Article 7 - How to contact us [#article-7---how-to-contact-us]
For privacy requests, contact:
**Mokaform SAS**\
Attn: Privacy Team\
61 RUE de Lyon\
75012 Paris\
France
Email: [security@mokaform.com](mailto:security@mokaform.com)
We may need to verify your identity before acting on a request.
## Article 8 - Complaints [#article-8---complaints]
If you are in the European Union, you may file a complaint with your local data protection authority.
Mokaform is based in France. The French supervisory authority is the CNIL:
* [CNIL complaints](https://www.cnil.fr/en/plaintes)
* [CNIL contact information](https://www.cnil.fr/en/contact-us)
## Article 9 - Security and confidentiality [#article-9---security-and-confidentiality]
Mokaform uses technical and organizational measures designed to protect personal data against unauthorized access, alteration, disclosure, loss, or destruction.
These measures include:
* HTTPS/TLS encryption in transit;
* encryption at rest where supported by infrastructure providers;
* account authentication and access controls;
* role-based and least-privilege access where appropriate;
* monitoring, logging, and incident response processes;
* vendor review for providers that may process personal data;
* backup and recovery processes; and
* confidentiality obligations for personnel and service providers.
No internet service is completely risk-free. Customers are responsible for configuring their forms, workspaces, exports, notifications, and integrations appropriately.
If a personal data breach occurs and notification is required by law, Mokaform will notify affected customers, individuals, or supervisory authorities as required.
## Article 10 - International transfers [#article-10---international-transfers]
Some service providers are located outside the European Union or may process data outside the European Union.
Where required, Mokaform relies on appropriate safeguards such as adequacy decisions, Standard Contractual Clauses, data processing agreements, and supplementary measures.
The current provider list and regions are available in [GDPR & Mokaform](/help/resources/gdpr).
## Article 11 - Updates [#article-11---updates]
We may update this Privacy Notice from time to time. If we make material changes, we will update this page and may notify customers through the service or by email where appropriate.
## Useful links [#useful-links]
* [Mokaform Privacy Policy](/privacy)
* [Mokaform Cookie Policy](/help/resources/cookie-policy)
* [GDPR & Mokaform](/help/resources/gdpr)
* [Mokaform Data Processing Agreement](/help/resources/data-processing-agreement)
* [Mokaform Terms of Service](/terms)
* [Mokaform Fair Use Policy](/help/resources/fair-use-policy)
# Report abuse (/help/resources/report-abuse)
Report malicious, fraudulent, illegal, phishing, spam, or abusive forms hosted on Mokaform and learn what details to include.
Mokaform does not allow malicious, fraudulent, illegal, or abusive use of the platform. If you find a Mokaform form that appears to violate our [Terms of Service](/terms), please report it.
Open the report form in a new page if the embedded form does not load.
## When to report a form [#when-to-report-a-form]
Report a form if you believe it is being used for:
* phishing, credential theft, fake login pages, or attempts to collect passwords, private keys, access tokens, or authentication secrets;
* fraud, scams, impersonation, deceptive claims, or misleading requests for money or personal data;
* spam, unsolicited messages, malware, malicious scripts, forced downloads, pop-ups, or attempts to install software without consent;
* collection of payment card details outside approved payment features;
* unlawful collection or misuse of personal data, sensitive data, children's data, government IDs, health data, biometric data, or financial data;
* harassment, threats, hate, intimidation, doxxing, non-consensual content, or content that encourages violence or self-harm;
* sexual exploitation, child sexual abuse material, grooming, or any attempt to exploit minors;
* infringement of intellectual property, trademarks, copyright, or privacy rights;
* automated abuse, scraping, excessive requests, or attempts to bypass security, rate limits, or access controls;
* content that is illegal in the relevant jurisdiction; or
* any other use that creates security, privacy, legal, operational, or safety risk.
## What to include [#what-to-include]
Please include as much of the following as you can:
* the full Mokaform form URL;
* a short description of the issue;
* screenshots or copied text that show the abuse, if safe to provide;
* why you believe the form is harmful, fraudulent, illegal, or unauthorized;
* whether you are the affected person, the rights holder, a respondent, or another reporter; and
* an email address if you want us to contact you for follow-up.
Do not submit passwords, private keys, payment card numbers, government ID scans, health records, or other highly sensitive information unless it is strictly necessary to explain the report. If a screenshot contains sensitive data, redact it where possible.
## What happens next [#what-happens-next]
We review abuse reports and may take action where appropriate, including:
* disabling or restricting a form;
* removing content;
* suspending or terminating an account;
* limiting suspicious usage;
* contacting the form owner;
* preserving evidence where legally necessary; or
* cooperating with authorities where required by law.
We may not be able to share the outcome of an investigation, especially when privacy, security, legal, or account confidentiality limits apply.
## Urgent safety issues [#urgent-safety-issues]
If there is an immediate risk of harm, contact local emergency services or law enforcement first. The abuse report form is not an emergency channel.
For security vulnerabilities in Mokaform itself, contact [security@mokaform.com](mailto:security@mokaform.com).
# Form analytics and drop-off (/help/results/analytics-drop-off)
Use Mokaform analytics to understand views, starts, completions, funnel metrics, question drop-off, time analysis, and traffic sources.
Analytics help you see where respondents arrive, start, slow down, and leave. Use them to improve completion and response quality.
Extended analytics are available on PRO. Free accounts can use shorter visits date ranges such as today, yesterday,
last 24 hours, and last 7 days; longer visits ranges require PRO.
## Core metrics [#core-metrics]
| Metric | What it means |
| ------------------- | ------------------------------------------ |
| Views | The form became visible in the browser. |
| Starts | The respondent interacted with the form. |
| Completions | The respondent submitted the form. |
| Completion rate | Completed submissions compared with views. |
| Drop-off rate | Started sessions that did not complete. |
| Completion duration | How long completed sessions took. |
A view is counted when the form is actually visible. If an embedded form sits far down a page and a visitor never
scrolls to it, that visit may not count as a form view.
## Funnel and page metrics [#funnel-and-page-metrics]
For multi-page forms, funnel metrics show how respondents move through each page.
Use page metrics to find:
* Pages where many respondents leave.
* Pages that take unusually long.
* Pages that receive views but few answers.
* Branches that are rarely reached.
When a page has high drop-off, check whether it contains too many required questions, unclear copy, sensitive fields, file uploads, payments, or a large jump in effort.
## Question drop-off [#question-drop-off]
Question drop-off shows where respondents get stuck at the field level.
Look for:
* A high view count with a low answer count.
* Questions that are viewed but skipped.
* Open text questions that follow easier choice questions.
* Fields that require information respondents may not have nearby.
Fixes that often help:
* Add help text.
* Make optional fields optional.
* Split a dense page into smaller pages.
* Replace long text fields with choices where possible.
* Move payment, signature, or file upload fields later in the form.
## Time analysis [#time-analysis]
Time-on-page helps identify confusing sections. A slow page is not always bad; it may simply contain a long-answer question. Compare time with drop-off before changing the form.
Good signals:
* High time and high completion: people are engaged.
* High time and high drop-off: people may be confused or blocked.
* Low time and high drop-off: people may not understand the value or may hit friction immediately.
## Traffic sources and device data [#traffic-sources-and-device-data]
Mokaform can use respondent session metadata to help explain performance by context.
Useful dimensions include:
* Referrer.
* Device type.
* Browser.
* Operating system.
* Country.
* Browser language.
Use this to compare channels. For example, mobile social traffic may need a shorter form than desktop traffic from an email campaign.
## What is not tracked [#what-is-not-tracked]
Mokaform avoids counting some events to keep analytics meaningful.
* Bot-like sessions may be excluded from tracking.
* Answer edits are not counted as new answers.
* Completed forms do not create abandonment events after submission.
* Initial page and question reach events are ordered after the respondent starts interacting.
## Improve a weak completion rate [#improve-a-weak-completion-rate]
Check whether the problem is traffic quality, first-page clarity, or later-page friction.
Review the highest drop-off page and the first unanswered question on that page.
Remove non-essential required fields.
Add context before sensitive questions.
Test the form on mobile and publish the improved version.
Compare analytics after a meaningful number of new responses.
## What to explore next [#what-to-explore-next]
Review individual submissions and exports.
Replace high-friction inputs with simpler blocks.
Shorten forms by showing only relevant questions.
# Results and automation (/help/results)
Review Mokaform response summaries, inspect submissions, analyze drop-off, export data, and connect follow-up workflows.
๐ Responses are coming in! Use these guides to understand the results, spot opportunities, and automate what happens next.
## ๐ Explore your results [#-explore-your-results]
Review aggregate results, inspect submissions, download files, and export response data.
Understand visits, starts, completion, page funnel data, question drop-off, and traffic sources.
Send emails, post channel alerts, sync spreadsheets, create tasks, and trigger webhooks.
# View form responses (/help/results/viewing-responses)
Review Mokaform response summaries, inspect individual submissions, download PDFs, export data, analyze answers, and manage uploaded files.
Congratulations! People are responding to your form. We'll show you how to view, analyze, and act on the data.
## 1. Access your responses [#1-access-your-responses]
Navigate to your workspace dashboard.
Find your form in the forms list.
Look for the **Responses** column.
Click the response number (e.g., "2", "15", "47").
**Alternative:** click your form name to open the builder, then go to the **Submissions** tab.
**What the numbers mean:**
* **"0"** โ no completed responses yet
* **Number** โ total completed responses (clickable)
* **Completion %** โ how many people who started also finished
A completion rate above 80% is excellent. Below 60% suggests your form may be too long or confusing.
## 2. Use the Summary tab [#2-use-the-summary-tab]
The Summary tab gives you an aggregate view before you open individual responses.
| Metric or section | What it tells you |
| ------------------ | ---------------------------------------------------------------------------------------------------- |
| Views | How many times the form was opened. |
| Starts | How many visitors began answering. |
| Submissions | How many completed the form. |
| Completion rate | The percentage of starters who submitted. |
| Average time | How long completed submissions usually take. |
| Question summaries | Charts, counts, averages, rankings, matrix results, NPS score, or heatmap summaries where supported. |
Use Summary when you need a quick read on performance. Use Submissions when you need to inspect a specific respondent, download files, or export rows.
## 3. View individual submissions [#3-view-individual-submissions]
**What you'll see:**
* Complete answers for every field
* Submission timestamp and completion time
* Device information (mobile, tablet, desktop)
* IP location (if enabled)
**Organization tools:**
* **Chronological order** โ newest first by default
* **Sortable columns** โ sort by any field or timestamp
* **Search** โ find specific responses quickly
* **Filters** โ show only responses meeting certain criteria
### Check response quality [#check-response-quality]
**Look for:**
* โ
Complete responses with all required questions answered
* โ
Thoughtful, detailed answers
* โ
Valid contact information
* โ ๏ธ Spam or fake responses
* โ ๏ธ Duplicate submissions
* โ ๏ธ Nonsensical text in open fields
If you notice spam, add a CAPTCHA or require email verification in your form settings.
## 4. Export your data [#4-export-your-data]
| Format | Best For | Includes |
| ------------------ | --------------------------------------------------------- | --------------------------------------- |
| **CSV** | Analysis, imports, Google Sheets, and lightweight exports | All downloaded responses and timestamps |
| **XLSX** | Spreadsheet review in Excel-compatible tools | All downloaded responses and timestamps |
| **Individual PDF** | Applications, approvals, signed forms, and records | One completed submission |
Go to the Submissions tab and click **Export**.
Choose CSV or XLSX for a bulk response download.
Click **Download**.
Export to CSV for the most flexibility in analyzing your data.
### Download one submission as PDF [#download-one-submission-as-pdf]
Use individual PDFs when each response is a record you need to store, forward, or review outside Mokaform.
Open the Submissions tab.
Find the response row.
Click the PDF download action for that submission.
### Download uploaded files [#download-uploaded-files]
File upload answers show their attachments inside the response. Open the submission or response table and use the file download action to save the uploaded file.
## 5. Analyze your data [#5-analyze-your-data]
**Response patterns:**
* Total submission count
* Completion rate (started vs. finished)
* Average completion time
* Device breakdown (mobile vs. desktop)
**Question insights:**
* Most popular choices in multiple-choice
* Average ratings in scale questions
* Common themes in open-ended responses
* Questions with high skip rates
**Geographic and timing:**
* Where responses come from
* When people respond most
* Response velocity (how quickly they come in)
Even with few responses, look for common themes in open-ended answers, popular choices, rating patterns, and
demographic patterns.
## Troubleshooting [#troubleshooting]
**Check:** Is your form published and accessible? Are you sharing the correct link? Is your call-to-action
compelling? Have you shared in the right places?
**Solutions:** Share more widely across channels, improve your sharing message, consider incentives, ask colleagues
to test and share, and check that the form works on mobile.
**Possible causes:** questions are unclear, the form is too long, or respondents don't understand the purpose.
**Solutions:** add clarifying text to confusing questions, shorten the form, improve the introduction and context,
and add CAPTCHA to reduce spam.
**Form improvements:** shorten by removing non-essential questions, break long forms into multiple pages, add
progress indicators, improve question clarity, and test the mobile experience.
**Engagement improvements:** strengthen your value proposition, set time expectations ("Takes 2 minutes"), explain
why their input matters, and improve visual design.
***
## Data privacy and security [#data-privacy-and-security]
**Your responsibilities**
* Only collect data you actually need
* Be transparent about how you'll use responses
* Provide privacy policy information
* Secure personal information appropriately
* Follow GDPR, CCPA, or industry-specific requirements
**Mokaform's protection**
* All data encrypted in transit and at rest
* Regular security updates and monitoring
* Compliance with major data protection standards
* Secure data centers
Use strong passwords and don't share login credentials. Export and store data securely.
***
## What's next [#whats-next]
Build more forms to gather additional insights.
Share your form more widely.
Improve your form's appearance.
# Custom domains and branded email (/help/share/custom-domains-email)
Set up Mokaform custom form domains, branded form paths, DNS records, and verified email sending domains for notifications.
Custom domains make public forms feel like part of your brand. Email sending domains help respondent and team notifications come from a trusted, verified sender.
Custom form domains, custom subdomains, custom form paths, and branded email sending domains require a PRO account.
## Domain types [#domain-types]
| Feature | What it controls |
| --------------------------- | ------------------------------------------------------------------ |
| Custom form domain | The domain or subdomain used in public form links. |
| Custom form path | The path for a specific form on a selected domain. |
| Default organization domain | The domain used by default for new or shared forms. |
| Email sending domain | The domain used by custom sender addresses in notification emails. |
## Set up a custom form domain [#set-up-a-custom-form-domain]
Open organization settings and go to the domain area.
Add the domain or subdomain you want to use.
Copy the DNS records shown by Mokaform into your DNS provider.
Wait for DNS propagation, then verify the domain.
Select the domain when sharing a form or make it the default for the organization.
Use a subdomain such as `forms.example.com` when you do not want to change your main website DNS.
## Configure a form path [#configure-a-form-path]
After a domain is verified, use a readable path for each form.
Examples:
* `/contact`
* `/customer-feedback`
* `/event-registration`
* `/jobs/designer-application`
Keep paths short, lowercase, and stable. If a link has already been sent to respondents, changing it can break campaigns or printed QR codes.
## Set up a branded email sending domain [#set-up-a-branded-email-sending-domain]
Use a verified sending domain when email notifications should come from your organization instead of Mokaform's default sender.
Open organization settings and find the email sending domain section.
Add the domain you want to send from.
Add the required DNS records at your DNS provider.
Verify the domain in Mokaform.
In email notification actions, choose the verified domain and sender details.
If DNS records become invalid later, email actions that rely on the custom domain may be blocked or disabled until the
domain is fixed and verified again.
## DNS tips [#dns-tips]
* DNS changes can take minutes or hours to propagate.
* Copy record names and values exactly.
* Some DNS providers automatically append your root domain to record names.
* Avoid duplicate records with conflicting values.
* If verification fails, compare the records in your DNS provider with the records shown in Mokaform.
## Troubleshooting [#troubleshooting]
DNS may not have propagated yet, or the record name may have been entered in the wrong format for your DNS provider.
Check both the name and value, then verify again.
Confirm the custom domain is verified and selected for the form link. If the form has moved, open the latest link
from the Share tab.
The email sending domain must be active before it can be used. Verify the DNS records and try again.
QR codes contain the exact URL used when they were generated. Download a new QR code after changing domains or
paths.
## What to explore next [#what-to-explore-next]
Share the correct live URL.
Use branded sender details in email actions.
Configure SEO previews, closed messages, and access controls.
# Embed forms on your website (/help/share/embed-forms)
Embed Mokaform forms as inline widgets, popups, popovers, sliders, side tabs, or full-screen forms on your website.
Embedding keeps respondents on your website while Mokaform handles the form experience.
## Embed styles [#embed-styles]
| Style | Best for | Behavior |
| ------------------ | ------------------------------------------ | -------------------------------------------------- |
| Widget | Contact pages, landing pages, blog posts | The form appears inline inside the page. |
| Full screen widget | Dedicated survey pages | The form fills the available container or screen. |
| Popup | Campaign pages and CTAs | A button or link opens the form in a modal. |
| Popover | Lightweight website feedback | A compact corner-style launcher opens the form. |
| Slider | Lead capture and contextual feedback | The form slides in from the side. |
| Side tab | Persistent feedback or support entry point | A tab stays on the left or right edge of the page. |
If compatibility matters more than visual effect, start with the widget embed. It is the simplest option for most
website builders.
## Add an embed [#add-an-embed]
Open your form and publish the latest version.
Go to the **Share** tab.
Choose the embed style you want.
Configure size, button text, colors, position, and submit behavior.
Save the embed, copy the code, and paste it into your website's HTML area.
Use the embed link instead of the full HTML code when a tool only accepts URL embeds.
## Configuration options [#configuration-options]
Mokaform embed code uses `data-mf-*` attributes. The generated code handles these for you, but understanding them helps when you work with developers.
Common attributes include:
* `data-mf-widget`, `data-mf-popup`, `data-mf-popover`, `data-mf-slider`, or `data-mf-side-tab`.
* `data-mf-link` for the public form URL.
* `data-mf-width`, `data-mf-height`, and `data-mf-auto-height` for inline sizing.
* `data-mf-full-screen` for full-screen widget behavior.
* `data-mf-button-text`, `data-mf-button-color`, and `data-mf-button-size` for launcher buttons.
* `data-mf-popup-size`, `data-mf-slider-position`, and `data-mf-side-tab-position`.
* `data-mf-hide-on-submit` to hide an embed after a successful submission.
* `data-mf-background` and `data-mf-opacity` for visual blending.
## Passing data into embedded forms [#passing-data-into-embedded-forms]
You can pass URL parameters through the form link used by the embed.
```text
https://your-form-link?utm_source=website&plan=pro
```
Use this for attribution, prefilled fields, or branch logic. Define the matching URL parameters in Mokaform before relying on them in rules or copy.
## Website builder notes [#website-builder-notes]
| Platform type | Recommendation |
| --------------------------- | ---------------------------------------------------------------------------------- |
| Custom website | Paste the full embed code before the closing body tag or in the target HTML block. |
| CMS or no-code builder | Use a custom HTML/embed block when available. |
| Tools that block JavaScript | Use the public form link or URL embed instead. |
| Email clients | Use the email embed instructions from the Share tab, not the website embed code. |
## Troubleshooting [#troubleshooting]
Confirm the form is published, the embed was saved before copying code, and the page allows custom JavaScript.
Test on a blank page with only the embed code to rule out site-level conflicts.
For inline widgets, check height and auto-height settings. Some website builders wrap embeds in containers with
fixed heights, so the parent block may need adjustment too.
Make sure the launcher element still has the generated Mokaform attributes. Avoid removing the `data-mf-*`
attributes when styling the button.
Test a simpler style, such as widget or full-screen. Popups and side panels can conflict with mobile page builders,
sticky headers, or custom overflow settings.
## What to explore next [#what-to-explore-next]
Learn every share option.
Pass campaign data into embedded forms.
Measure embedded form performance.
# Publish and share forms (/help/share)
Publish Mokaform forms, share links, embed forms, create QR codes, download PDFs, and configure custom domains.
Your form is readyโnow let's put it in front of the right people.
## ๐ฃ Choose how to share [#-choose-how-to-share]
Publish, copy or customize the link, generate QR codes, download a PDF, share templates, and update link previews.
Add inline embeds, popups, popovers, sliders, side tabs, and full-screen embeds to a website.
Verify domains for public form URLs and notification sender addresses.
# Publishing and sharing forms (/help/share/publishing-sharing)
Publish Mokaform forms, customize share links, embed on websites, generate QR codes, download PDFs, and set social previews.
Your form is ready. Now let's get it to the people who need to fill it out.
* How to make your form live
* All share options: link, customized link, QR code, web embed, email embed, PDF, template, and social preview
* How to fix common problems
***
## 1. Make your form live [#1-make-your-form-live]
When you havenโt published your form yet, or after youโve updated it, publish it to push your changes live.
Navigate to the edit section.
Publish your form with the button at the top right.
Done. Your form is live and has a permanent link.
***
## 2. Share your form [#2-share-your-form]
In the **Share** tab, pick the method that fits your situation.
### Share a link [#share-a-link]
**Best for:** emails, messages, social posts
Stay on the Share tab.
Click **Copy** next to the link.
Paste it in your email, message, or post.
***
### Customize the link [#customize-the-link]
**Best for:** branded campaigns, printed QR codes, and links that should be easy to read
Use the customized link option when you want to change the form path or use a verified organization domain.
Custom paths and custom domains are available on PRO.
Open the Share tab and find the link section.
Choose the domain or subdomain you want to use.
Enter a short path, such as `customer-feedback`, `contact`, or `event-registration`.
Save the custom URL, then copy and test it in an incognito window.
If the link has already been sent, printed, or embedded, changing the domain or path means you also need to update
those places.
***
### Embed on your website [#embed-on-your-website]
**Best for:** contact pages, blog posts, landing pages
| Style | Description | Best For |
| --------------- | --------------------- | ---------------- |
| **Standard** | Form appears inline | Contact pages |
| **Full screen** | Takes over screen | Focused surveys |
| **Popup** | Button opens modal | Landing pages |
| **Slider** | Slides in from side | Exit intent |
| **Side tab** | Tab on edge of screen | Always available |
| **Popover** | Widget in corner | Chat-style |
Scroll to "Embed in a Web Page".
Click your preferred style.
Customize button text, colors, and size.
Click **Save embed**, then **Get the code**.
Copy the HTML code and paste it in your website's HTML editor.
Click **Copy embed link** instead, then paste that link directly in your editor.
The **Standard** style works with most website builders and has the fewest compatibility issues.
***
### Embed in email [#embed-in-email]
**Best for:** email marketing campaigns (Mailchimp, HubSpot)
Click **See instructions** in "Embed in an email".
Check if your form works with email. If you see a yellow warning, remove unsupported fields.
Click **Copy** to get the email code.
Open your email marketing tool and switch to code view (`<>` icon).
Paste the code.
**Unsupported fields:** Date, File upload, Signature, Payment. This only works with email marketing tools, not Gmail
or Outlook.
***
### Generate a QR code [#generate-a-qr-code]
**Best for:** posters, business cards, events, physical locations
Click the *QR code icon* (next to the email icon).
Download the QR code.
Print it on your materials.
**When to use:** conference booth, restaurant feedback, event signup, poster campaigns.
***
### Download as PDF [#download-as-pdf]
**Best for:** offline review, printable forms, approvals, and records
The Share tab can generate a blank PDF version of the form.
Open the Share tab.
Find the PDF option.
Click **Download**.
Use the PDF as a blank copy of the questionnaire. To download a completed response as PDF, use the Submissions tab instead.
***
### Customize social media preview [#customize-social-media-preview]
**Best for:** Facebook, LinkedIn, Twitter, WhatsApp shares
Saving custom social preview metadata is available on PRO.
Look at the **Preview** section on the right and click **Customize**.
Upload an icon (512ร512px recommended) and a preview image (1200ร630px recommended).
Edit the title and description, then click **Save preview**.
Now when someone shares your link, it shows your custom image and text.
***
### Share as a template [#share-as-a-template]
**Best for:** sharing form designs with your team
Scroll to the "Template" section and click **Create**.
Fill in the template name, category, and privacy, then upload a preview image.
Click **Create**, then **Copy link** to share.
People who click can copy your form to their workspace.
***
## 3. Troubleshooting [#3-troubleshooting]
**Check:** Is it published? Does the link work when you test it? Did you tell people how long it takes?
**Solutions:** Make it shorter (under 10 questions), add "Takes 2 minutes" to your message, explain why their input
matters, and send a reminder after a week.
Usually caused by sending the preview link instead of the published one, or the form isn't published yet.
1. Go to the Share tab.
2. Copy the link from the text box (not the browser address bar).
3. Make sure it says "Published" at the top.
4. Test the link in an incognito window.
**Check:** Did you click "Save embed" before copying code? Did you paste as HTML (not plain text)? Does your website
allow JavaScript?
**Solutions:** Create a test page with just the embed code, try the "Standard" style (most compatible), and check
the browser console for errors (**F12** โ **Console**).
***
## Best practices [#best-practices]
**Timing**
* **Business surveys:** TuesdayโThursday, 10amโ3pm
* **Consumer surveys:** evenings (7โ9pm) or weekends
* **Avoid:** Monday mornings and Friday afternoons
**Your message**
* Tell them how long: "2-minute survey"
* Explain why: "Your feedback shapes our next update"
* Make it easy: put the link prominently
* Say thank you
**Follow up**
* Wait a week before sending a reminder
* Change your message for the reminder
* Don't send more than two reminders
***
## What's next [#whats-next]
See what people are saying.
Make your form look better.
Build your next form.
# Address question (/help/build/question-types/address)
Use the Mokaform Address question to collect structured postal addresses for applications, orders, registrations, and intake forms.
`EXTRA_TYPE: ADDRESS`
Use **Address** when the answer should be a postal address with structured parts.
## Use it for [#use-it-for]
* Shipping, billing, location verification, event logistics, field service, and customer records.
* Workflows that need address components in exports or integrations.
* Forms where a single [Long text](/help/build/question-types/long-text) address would be too hard to process.
## Settings to check [#settings-to-check]
* **Required address parts** based on the workflow.
* **Country or region assumptions** in the description.
* **Privacy wording** if the address is sensitive.
* **Integration mapping** to destination address fields.
## Workflow notes [#workflow-notes]
Address data can be sensitive. Collect it only when it is required and make sure the destination integration can receive the parts you collect. If you only need a broad location, use [Short text](/help/build/question-types/short-text) or [Dropdown](/help/build/question-types/dropdown) instead.
## Related types [#related-types]
Collect a simple location label.
Collect country or region from a list.
# Checkbox question (/help/build/question-types/checkbox)
Use the Mokaform Checkbox question for opt-ins, acknowledgements, confirmations, and standalone yes/no agreements.
`TYPE: CHECKBOX_OPTION`
Use **Checkbox** when the respondent should actively tick a statement.
## Use it for [#use-it-for]
* Newsletter opt-ins, terms acknowledgements, eligibility confirmations, and consent statements.
* Independent yes/no confirmations.
* Optional add-ons where each item stands alone.
## Settings to check [#settings-to-check]
* **Required** if the box must be checked to submit.
* **Label wording** so the statement is clear without extra context.
* **Default value** only when prechecking is appropriate and compliant.
* **[Legal](/help/build/question-types/legal) copy** if the checkbox represents consent.
## Workflow notes [#workflow-notes]
Checkbox answers export as a boolean-like value. Use [Legal](/help/build/question-types/legal) when you need a dedicated consent block with agreement language, and use [Multiple choice](/help/build/question-types/multiple-choice) when the respondent is selecting from a list rather than confirming a statement.
## Related types [#related-types]
Use for consent agreements.
Use for a direct binary question.
# Contact question (/help/build/question-types/contact)
Use the Mokaform Contact question to collect grouped names, email addresses, phone numbers, and contact details in one block.
`EXTRA_TYPE: CONTACT`
Use **Contact** when a form needs several contact fields together.
## Use it for [#use-it-for]
* Lead capture, applications, registrations, customer intake, and support requests.
* Workflows that require a name plus contact methods.
* Forms where grouped contact fields reduce setup time.
## Settings to check [#settings-to-check]
* **Required fields** inside the group.
* **Labels** so respondents know which details are expected.
* **[Email](/help/build/question-types/email) and [Phone](/help/build/question-types/phone) needs** before making both mandatory.
* **Integration mapping** if the destination tool expects separate fields.
## Workflow notes [#workflow-notes]
Contact is convenient for common contact details. If a workflow needs precise control over each field, use separate [Short text](/help/build/question-types/short-text), [Email](/help/build/question-types/email), [Phone](/help/build/question-types/phone), and [Website](/help/build/question-types/website) questions instead.
## Related types [#related-types]
Collect email only.
Collect phone only.
# Date question (/help/build/question-types/date)
Use the Mokaform Date question to collect calendar dates for appointments, deadlines, birthdays, bookings, and applications.
`TYPE: DATE`
Use **Date** when the answer should be a calendar date.
## Use it for [#use-it-for]
* Appointment dates, event dates, deadlines, birthdays, availability, and application dates.
* Exports that need a consistent date column.
* Automations that rely on a date value in another tool.
## Settings to check [#settings-to-check]
* **Required** when scheduling depends on it.
* **Date limits** if the answer must be in a valid range.
* **Format and language** so the picker matches the respondent audience.
* **Timezone context** in the question text when the date is tied to a time-sensitive event.
## Workflow notes [#workflow-notes]
Date fields are not supported in email embeds. If you plan to embed the form directly in an email campaign, link to the form instead or remove Date from the email-embedded version.
## Related types [#related-types]
Collect a time of day.
Schedule form open and close dates.
# Dropdown question (/help/build/question-types/dropdown)
Use the Mokaform Dropdown question when respondents choose one structured answer from a long list of options.
`TYPE: DROPDOWN`
Use **Dropdown** when a list has many options and you want to keep the form compact.
## Use it for [#use-it-for]
* Countries, departments, product lists, roles, locations, categories, and fixed time slots.
* Forms where a long visible option list would slow people down.
* Integration mappings that need one standardized value.
## Settings to check [#settings-to-check]
* **Required** state.
* **Placeholder** such as `Select a country`.
* **Default value** if one option should be preselected.
* **Option names** before connecting integrations.
## Workflow notes [#workflow-notes]
Dropdown answers are structured and easy to export. Keep option labels stable after workflows are connected. If respondents need to select several items, use [Multiple choice](/help/build/question-types/multiple-choice) configured for multiple selection.
## Related types [#related-types]
Use for visible choices.
Use when the list is not fixed.
# Email question (/help/build/question-types/email)
Use the Mokaform Email question to collect validated email addresses for follow-up, notifications, CRM sync, and exports.
`TYPE: EMAIL`
Use **Email** when you need a valid email address for follow-up, receipts, respondent notifications, or deduplication.
## Use it for [#use-it-for]
* Contact forms, lead forms, applications, registrations, and support requests.
* Respondent email notifications.
* Unique submission rules based on email address.
## Settings to check [#settings-to-check]
* **Required** if the workflow depends on contacting the respondent.
* **Placeholder** such as `name@example.com`.
* **Default value** when the email comes from a known link or URL parameter.
* **Unique submission key** in form settings if each email should submit once.
## Workflow notes [#workflow-notes]
Email answers are especially useful in integrations. Map them to respondent email actions, CRM fields, spreadsheet columns, and webhook payloads. If you plan to send respondent emails, test the full flow with a real inbox before sharing the form.
## Related types [#related-types]
Collect a phone number.
Collect grouped contact details.
# File upload question (/help/build/question-types/file-upload)
Use the Mokaform File upload question to collect documents, screenshots, images, attachments, and supporting files.
`TYPE: FILE_UPLOAD`
Use **File upload** when the response needs a file, not just text.
PRO removes the free plan's file upload size limit and enables unlimited file uploads.
## Use it for [#use-it-for]
* Resumes, portfolios, screenshots, invoices, identity documents, design files, and evidence attachments.
* Support forms where a screenshot makes triage faster.
* Applications where reviewers need source material.
## Settings to check [#settings-to-check]
* **Required** only when the file is necessary.
* **Accepted file types** if only certain formats are useful.
* **File size guidance** in the description.
* **Privacy wording** when collecting sensitive files.
## Workflow notes [#workflow-notes]
File upload fields are not supported in email embeds. Shared files may also affect storage and privacy workflows. Make sure reviewers know where to download attachments from submissions.
## Related types [#related-types]
Collect a link instead.
Collect approval.
# Heatmap question (/help/build/question-types/heatmap)
Use the Mokaform Heatmap question to collect clicks, selections, and visual feedback on images, layouts, products, or designs.
`TYPE: HEATMAP`
Use **Heatmap** when respondents should select a point or area on an image.
## Use it for [#use-it-for]
* Product feedback, visual preference testing, body maps, UI research, shelf placement, and design review.
* Questions where coordinates or image regions matter more than text.
* Summary views that show where people clicked.
## Settings to check [#settings-to-check]
* **Image quality** and aspect ratio.
* **Instructions** explaining what respondents should select.
* **Required** state.
* **Mobile preview** to confirm the image is large enough to use.
## Workflow notes [#workflow-notes]
Heatmap works best with clear images and one task per question. If respondents need to explain why they selected an area, add a [Long text](/help/build/question-types/long-text) question immediately after it.
## Related types [#related-types]
Use layout image blocks for context.
Ask for the reason behind a click.
# Question types and form blocks (/help/build/question-types)
Compare Mokaform question types and blocks for text, choices, ratings, files, payments, signatures, consent, media, and layout.
๐งฑ Every good form starts with the right building blocks. Question blocks collect answers, layout blocks shape the page, and hidden blocks carry data used by logic, links, and integrations.
Start with the data you need after submission. If the answer must be filtered, charted, mapped to an integration, or
exported cleanly, prefer a structured question type over free text.
## ๐ ๏ธ Build a great question step by step [#๏ธ-build-a-great-question-step-by-step]
Choose the question type that matches the answer format you need.
Write the label, description, placeholder, and options.
Configure validation, required state, default value, limits, and answer choices.
Add logic, variables, or URL parameters if the question should control later steps.
Test the question on desktop and mobile, then check the Summary and Submissions tabs after a test response.
## ๐งญ Find the right question type [#-find-the-right-question-type]
| Goal | Use |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Collect a one-line answer | [Short text](/help/build/question-types/short-text) |
| Collect a paragraph | [Long text](/help/build/question-types/long-text) |
| Validate contact details | [Email](/help/build/question-types/email), [Phone](/help/build/question-types/phone), [Website](/help/build/question-types/website) |
| Collect a full contact or address | [Contact](/help/build/question-types/contact), [Address](/help/build/question-types/address) |
| Offer one or many options | [Multiple choice](/help/build/question-types/multiple-choice), [Checkbox](/help/build/question-types/checkbox) |
| Choose from a long list | [Dropdown](/help/build/question-types/dropdown) |
| Compare rows on one scale | [Matrix](/help/build/question-types/matrix) |
| Ask for ordered preferences | [Ranking](/help/build/question-types/ranking) |
| Measure sentiment | [NPS](/help/build/question-types/nps), [Opinion scale](/help/build/question-types/opinion-scale), [Rating](/help/build/question-types/rating), [Likert scale](/help/build/question-types/likert-scale) |
| Collect numbers, dates, or times | [Number](/help/build/question-types/number), [Date](/help/build/question-types/date), [Time](/help/build/question-types/time) |
| Collect files, approvals, money, or image clicks | [File upload](/help/build/question-types/file-upload), [Signature](/help/build/question-types/signature), [Payment](/help/build/question-types/payment), [Heatmap](/help/build/question-types/heatmap) |
| Confirm consent | [Legal](/help/build/question-types/legal) |
## โจ Explore every question type [#-explore-every-question-type]
One-line free-text answers.
Paragraph answers and open feedback.
Validated email addresses for follow-up and automation.
Phone numbers with phone-specific formatting.
Links, portfolios, and company websites.
Quantities, budgets, ages, scores, and measurements.
Dates, deadlines, birthdays, and appointments.
Preferred times, slots, and availability windows.
Structured single-select or multi-select choices.
Standalone opt-ins and confirmations.
Compact lists with many possible answers.
Repeated row-by-column ratings.
Ordered preferences and priorities.
Binary decisions.
Required consent and agreement.
Recommendation score from 0 to 10.
Numeric scales with endpoint labels.
Visual scores such as stars.
Agreement, frequency, importance, or attitude.
Documents, screenshots, images, and attachments.
Drawn approvals and acknowledgements.
Stripe-backed payment collection.
Clicks or selections on an image.
Grouped contact information.
Structured postal addresses.
## ๐ Complete block type reference [#-complete-block-type-reference]
These `TYPE`, `EXTRA_TYPE`, and editor constants are useful when you are reading exports, mapping integrations, or discussing a form with support.
| Category | TYPE values |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Text questions | `SHORT_TEXT`, `LONG_TEXT` |
| Contact questions | `EMAIL`, `PHONE`, `WEBSITE` |
| Choice questions | `MULTIPLE_CHOICE_OPTION`, `CHECKBOX_OPTION`, `DROPDOWN`, `MATRIX`, `RANKING`, `YES_NO` |
| Rating questions | `NPS`, `OPINION_SCALE`, `RATING`, `LIKERT_SCALE` |
| Other questions | `NUMBER`, `DATE`, `TIME`, `FILE_UPLOAD`, `SIGNATURE`, `PAYMENT`, `HEATMAP`, `LEGAL` |
| Extra question blocks | `CONTACT`, `ADDRESS` |
| Layout text | `HEADING`, `PARAGRAPH`, `LABEL`, `TITLE`, `HEADING_1`, `HEADING_2`, `HEADING_3`, `FORM_HEADING`, `SMALL_TEXT`, `DEFAULT_TEXT`, `LARGE_TEXT` |
| Layout media and content | `IMAGE`, `VIDEO`, `DIVIDER`, `CALLOUT`, `BULLET_LIST`, `ORDERED_LIST` |
| Structure | `PAGE`, `PAGE_REDIRECT`, `ROW`, `COLUMN` |
| Extra and editor structure | `GROUP`, `END_SCREEN`, `THANK_YOU_REDIRECT_SCREEN`, `PAGE_BREAK` |
| System structure | `PAGE_LAYOUT_CONTENT`, `PAGE_LAYOUT_MEDIA`, `HIDDEN_CONTAINER`, `MATRIX_HEADER`, `MATRIX_ROW`, `MATRIX_COL`, `RANKING_CHOICE` |
| Hidden data | `VARIABLE`, `URL_PARAMETER`, `LOGIC` |
## ๐ What to explore next [#-what-to-explore-next]
Use answers to personalize branches, calculations, and integrations.
Understand the full path from workspace setup to submissions and automation.
Publish and share the finished form.
# Legal consent question (/help/build/question-types/legal)
Use the Mokaform Legal question when respondents must agree to terms, consent language, policies, or required acknowledgements.
`TYPE: LEGAL`
Use **Legal** for agreement language that must be accepted before submission.
## Use it for [#use-it-for]
* Terms acceptance, privacy acknowledgements, waivers, GDPR consent, and policy confirmations.
* Forms that collect sensitive or regulated information.
* Consent steps before payment, signature, file upload, or application submission.
## Settings to check [#settings-to-check]
* **Required** for mandatory agreements.
* **Agreement text** reviewed by the right legal or compliance owner.
* **Links** to policies or terms if respondents need to inspect details.
* **Placement** near the final submission step.
## Workflow notes [#workflow-notes]
Legal captures agreement as part of the submission record, but it does not replace legal advice. Keep the language specific to the form and avoid collecting consent you do not need.
## Related types [#related-types]
Use for simpler confirmations.
Collect a drawn approval.
# Likert scale question (/help/build/question-types/likert-scale)
Use the Mokaform Likert scale question for agreement, frequency, importance, satisfaction, and attitude statements.
`TYPE: LIKERT_SCALE`
Use **Likert scale** when respondents react to a statement on an ordered scale.
## Use it for [#use-it-for]
* Agreement, frequency, importance, confidence, quality, and satisfaction statements.
* Research surveys that need comparable attitude data.
* Summary reporting with score distribution.
## Settings to check [#settings-to-check]
* **Balanced options** from negative to positive or low to high.
* **Neutral option** if neutrality is meaningful.
* **Required** state.
* **Statement wording** that asks about one idea at a time.
## Workflow notes [#workflow-notes]
Keep scales consistent across related questions. Mixing 4-point and 5-point scales in the same survey makes analysis harder. Use [Matrix](/help/build/question-types/matrix) if you need the same Likert options across many statements.
## Related types [#related-types]
Use for repeated statements.
Use for numeric scales.
# Long text question (/help/build/question-types/long-text)
Use the Mokaform Long text question to collect paragraphs, explanations, project briefs, research responses, and open feedback.
`TYPE: LONG_TEXT`
Use **Long text** when respondents need room to explain something in their own words.
## Use it for [#use-it-for]
* Feedback, comments, descriptions, and support context.
* Project briefs, application answers, research responses, and testimonials.
* Questions where the important detail is not predictable enough for choices.
## Settings to check [#settings-to-check]
* **Required** only when the form cannot be processed without the explanation.
* **Placeholder** for a short example, not a full instruction.
* **Default value** when you are preloading known context.
* **Minimum or maximum length** if the answer must be substantial or concise.
## Workflow notes [#workflow-notes]
Long text is best for qualitative review. It exports cleanly, but it is not ideal for charts or routing. If an answer should trigger logic or a specific integration path, add a structured choice question before the long text, such as [Multiple choice](/help/build/question-types/multiple-choice) or [Dropdown](/help/build/question-types/dropdown).
## Related types [#related-types]
Use for one-line answers.
Use for analyzable categories.
# Matrix question (/help/build/question-types/matrix)
Use the Mokaform Matrix question to ask repeated rows with the same answer choices for ratings, comparisons, and surveys.
`TYPE: MATRIX`
Use **Matrix** when several items should be answered on the same scale.
## Use it for [#use-it-for]
* Feature ratings, satisfaction surveys, agreement grids, importance scoring, and comparative research.
* Questions where rows are items and columns are repeated answer choices.
* Compact surveys that would otherwise repeat the same rating question many times.
## Settings to check [#settings-to-check]
* **Rows and columns** with clear, balanced labels.
* **Required** behavior for each row.
* **Default values** if prefilled answers are appropriate.
* **Mobile readability** before publishing.
## Workflow notes [#workflow-notes]
Matrix can shorten a form, but it can also become dense on small screens. Use it when the repeated structure helps respondents answer faster. For more detailed comments on each item, split the question into separate pages or pair the matrix with [Long text](/help/build/question-types/long-text).
## Related types [#related-types]
Use for one attitude statement.
Use for one visual score.
# Multiple choice question (/help/build/question-types/multiple-choice)
Use the Mokaform Multiple choice question for structured answers that are easy to analyze, route, export, and sync.
`TYPE: MULTIPLE_CHOICE_OPTION`
Use **Multiple choice** when respondents choose from a list of options.
## Use it for [#use-it-for]
* Categories, preferences, segments, plans, departments, products, and source attribution.
* Logic branches and integration triggers.
* Questions you want to summarize with counts or percentages.
## Settings to check [#settings-to-check]
* **Single-select or multi-select** behavior.
* **Required** state.
* **Other option** if the list may be incomplete.
* **Randomize options** when answer-order bias matters.
* **Default value** when the answer can be preselected.
## Workflow notes [#workflow-notes]
Multiple choice is one of the best question types for workflow automation. Use stable option labels before mapping to Slack, Google Sheets, Airtable, Notion, Jira, Linear, Asana, or webhooks. If the list is long, use [Dropdown](/help/build/question-types/dropdown).
## Related types [#related-types]
Use for standalone confirmations.
Use for long lists.
# NPS question (/help/build/question-types/nps)
Use the Mokaform NPS question to measure recommendation likelihood and collect follow-up feedback from detractors and promoters.
`TYPE: NPS`
Use **NPS** for a 0 to 10 recommendation score.
## Use it for [#use-it-for]
* Customer loyalty, product sentiment, onboarding feedback, event follow-up, and support satisfaction.
* Tracking promoters, passives, and detractors over time.
* Summary reporting where the NPS score matters more than individual ratings.
## Settings to check [#settings-to-check]
* **Prompt wording** that identifies what the respondent is recommending.
* **Required** state.
* **Follow-up logic** for low, neutral, or high scores.
* **Optional [Long text](/help/build/question-types/long-text)** after the score to collect the reason.
## Workflow notes [#workflow-notes]
NPS is most useful when asked consistently. Avoid changing the wording often if you compare results over time. Use logic to ask detractors for issue details and promoters for testimonials or referrals, often with a [Long text](/help/build/question-types/long-text) follow-up.
## Related types [#related-types]
Use for custom numeric scales.
Ask for the reason behind the score.
# Number question (/help/build/question-types/number)
Use the Mokaform Number question for quantities, budgets, scores, ages, measurements, totals, and numeric exports.
`TYPE: NUMBER`
Use **Number** when the answer must be numeric and should be sortable, filtered, calculated, or exported as a number.
## Use it for [#use-it-for]
* Quantity, age, budget, price, revenue, team size, priority score, or measurement.
* Calculations with variables.
* Integration fields that expect a numeric value.
## Settings to check [#settings-to-check]
* **Minimum and maximum** values.
* **Prefix or suffix** such as `$`, `%`, `kg`, or `people`.
* **Decimal and separator behavior** if precision matters.
* **Default value** when prefilled from known data.
## Workflow notes [#workflow-notes]
Number questions are better than [Short text](/help/build/question-types/short-text) for reporting because exports and integrations can keep the value numeric. Use clear units in the label or suffix so respondents do not mix currencies, periods, or measurement systems.
## Related types [#related-types]
Collect a bounded rating.
Collect money through Stripe.
# Opinion scale question (/help/build/question-types/opinion-scale)
Use the Mokaform Opinion scale question for numeric sentiment, effort, likelihood, importance, and satisfaction ratings.
`TYPE: OPINION_SCALE`
Use **Opinion scale** when respondents should choose a number on a bounded scale.
## Use it for [#use-it-for]
* Satisfaction, effort, confidence, likelihood, importance, and priority.
* Product research and customer experience surveys.
* Questions that need averages or score distributions in the Summary tab.
## Settings to check [#settings-to-check]
* **Scale range** that matches the question.
* **Endpoint labels** such as `Not important` and `Very important`.
* **Required** state.
* **Default value** only when preselection is intentional.
## Workflow notes [#workflow-notes]
Use balanced labels. Do not mix a neutral low label with an emotional high label. Add [Long text](/help/build/question-types/long-text) after low scores when you need context.
## Related types [#related-types]
Use for recommendation score.
Use for agreement statements.
# Payment question (/help/build/question-types/payment)
Use the Mokaform Payment question to collect money through Stripe for orders, donations, fees, bookings, and paid forms.
`TYPE: PAYMENT`
Use **Payment** when the form needs to collect money before or during submission.
## Use it for [#use-it-for]
* Event tickets, deposits, paid consultations, products, donations, and application fees.
* Workflows where payment status should be reviewed with the submission.
* Confirmation emails that should mention the paid order or next step.
## Settings to check [#settings-to-check]
* **Amount and currency**.
* **Product or payment description**.
* **Required** state and placement near the end of the form.
* **Confirmation email** if respondents need a receipt or next step.
## Workflow notes [#workflow-notes]
Payment fields are not supported in email embeds. Test the full payment flow before sharing the form publicly, including failed or cancelled payment paths.
## Related types [#related-types]
Collect numeric values without payment.
Notify your team after paid submissions.
# Phone question (/help/build/question-types/phone)
Use the Mokaform Phone question to collect phone numbers with phone-specific formatting for follow-up and integrations.
`TYPE: PHONE`
Use **Phone** when a respondent may need to be called, texted, or matched to an existing contact record.
## Use it for [#use-it-for]
* Sales inquiries, support callbacks, bookings, event registrations, and applications.
* Forms where a phone number is more reliable than email.
* CRM and help desk records that have a dedicated phone field.
## Settings to check [#settings-to-check]
* **Required** only when phone contact is part of the workflow.
* **Default country** if most respondents are in one region.
* **Placeholder** for an example number.
* **Default value** if the number is known from a previous step.
## Workflow notes [#workflow-notes]
Phone numbers are personal data. Collect them only when your team will use them. If the form is international, test the field with multiple country formats before publishing.
## Related types [#related-types]
Collect an email address.
Collect full contact details.
# Ranking question (/help/build/question-types/ranking)
Use the Mokaform Ranking question to collect ordered preferences, priorities, feature rankings, and choice comparisons.
`TYPE: RANKING`
Use **Ranking** when the order matters more than a single choice.
## Use it for [#use-it-for]
* Prioritizing features, ordering preferences, choosing top criteria, and comparing alternatives.
* Product research, event planning, hiring criteria, and roadmap input.
* Summary views that should show highest-ranked items.
## Settings to check [#settings-to-check]
* **Choice labels** that are short enough to reorder easily.
* **Number of choices** so the ranking task is not exhausting.
* **Required** state.
* **Instructions** telling respondents whether to rank all items or only the most important ones.
## Workflow notes [#workflow-notes]
Ranking is more demanding than [Multiple choice](/help/build/question-types/multiple-choice). Use it when the order has a real decision impact. If you only need a favorite option, use [Multiple choice](/help/build/question-types/multiple-choice).
## Related types [#related-types]
Use for one or more selected
choices.
Use for scored opinions.
# Rating question (/help/build/question-types/rating)
Use the Mokaform Rating question for visual scores such as stars, satisfaction ratings, quality scores, and quick feedback.
`TYPE: RATING`
Use **Rating** when a visual score is faster to answer than a numeric scale.
## Use it for [#use-it-for]
* Product reviews, service quality, event feedback, course feedback, and quick satisfaction checks.
* Forms where respondents expect a familiar star-style interaction.
* Summary reporting with average rating and distribution.
## Settings to check [#settings-to-check]
* **Maximum rating** and visual shape.
* **Required** state.
* **Label text** explaining what low and high ratings mean.
* **Default value** only when preselection is intentional.
## Workflow notes [#workflow-notes]
Rating is fast, but it can be vague without labels. Add a short [Long text](/help/build/question-types/long-text) follow-up when the rating is below a threshold so your team knows what to fix.
## Related types [#related-types]
Use for numeric labels.
Use for recommendation scoring.
# Short text question (/help/build/question-types/short-text)
Use the Mokaform Short text question to collect names, codes, brief answers, identifiers, and one-line free-text responses.
`TYPE: SHORT_TEXT`
Use **Short text** when the answer should fit on one line.
## Use it for [#use-it-for]
* Names, company names, job titles, IDs, and short labels.
* Answers that are unpredictable but still brief.
* Values you may pass into email, Slack, webhooks, or CRM fields.
## Settings to check [#settings-to-check]
* **Required** when the answer is necessary to process the submission.
* **Placeholder** for an example such as `Acme Inc.` or `Order #12345`.
* **Default value** when the answer can be prefilled from known data.
* **Character limits** if downstream tools have length limits.
## Workflow notes [#workflow-notes]
Short text answers appear as plain values in submissions and exports. They are easy to map to integrations, but harder to chart than choice fields. If you expect a small fixed set of answers, use [Multiple choice](/help/build/question-types/multiple-choice) or [Dropdown](/help/build/question-types/dropdown) instead.
## Related types [#related-types]
Use for paragraphs.
Use for fixed lists.
# Signature question (/help/build/question-types/signature)
Use the Mokaform Signature question to collect drawn approvals, acknowledgements, confirmations, and signed form responses.
`TYPE: SIGNATURE`
Use **Signature** when a respondent should sign as part of the submission.
## Use it for [#use-it-for]
* Waivers, approvals, acknowledgements, permission forms, intake forms, and internal sign-offs.
* Forms where the signature should be included in submission review or PDF records.
* Workflows that need a visible approval step before submission.
## Settings to check [#settings-to-check]
* **Required** for mandatory approvals.
* **[Legal](/help/build/question-types/legal) or consent text** near the signature.
* **Mobile usability** so signing works comfortably on small screens.
* **PDF download** if signed submissions need to be archived.
## Workflow notes [#workflow-notes]
Signature fields are not supported in email embeds. If signature matters, send respondents to the full form link rather than trying to collect it inside an email.
## Related types [#related-types]
Collect consent language.
Download signed responses as PDF.
# Time question (/help/build/question-types/time)
Use the Mokaform Time question to collect preferred times, availability windows, appointment times, and scheduling details.
`TYPE: TIME`
Use **Time** when you need a time of day rather than a date.
## Use it for [#use-it-for]
* Preferred callback times, appointment windows, delivery windows, and meeting availability.
* Forms where the date is already known.
* Integrations that need a structured time value.
## Settings to check [#settings-to-check]
* **Required** if the workflow cannot continue without a time.
* **Placeholder** or help text explaining the expected timezone.
* **Default value** for prefilled internal forms.
* **Time limits** if only business hours or event hours are valid.
## Workflow notes [#workflow-notes]
Time answers need timezone context. Add the timezone to the label, description, or surrounding text when respondents may be in different locations.
## Related types [#related-types]
Collect a date.
Offer fixed time slots.
# Website question (/help/build/question-types/website)
Use the Mokaform Website question to collect URLs, portfolios, social profiles, company websites, and online references.
`TYPE: WEBSITE`
Use **Website** when the answer should be a link.
## Use it for [#use-it-for]
* Company websites, portfolio links, LinkedIn profiles, public documents, and product pages.
* Application forms where reviewers need to inspect external work.
* Lead forms where website enrichment or CRM mapping happens later.
## Settings to check [#settings-to-check]
* **Required** only when the URL is essential.
* **Placeholder** such as `https://example.com`.
* **Default value** when the link is known from a previous workflow.
* **Help text** explaining which type of link you expect.
## Workflow notes [#workflow-notes]
Website values export as URLs and can be sent to integrations. If respondents may paste several links, use [Long text](/help/build/question-types/long-text) instead, or ask separate Website questions for each required URL.
## Related types [#related-types]
Collect a short free-text value.
Collect an attachment instead of a
link.
# Yes/No question (/help/build/question-types/yes-no)
Use the Mokaform Yes/No question for clear binary decisions, eligibility checks, routing logic, and simple confirmations.
`TYPE: YES_NO`
Use **Yes/No** when the answer has exactly two meaningful states.
## Use it for [#use-it-for]
* Eligibility questions, screening, consent checks, feature usage, and binary preferences.
* Logic branches such as "Do you need an invoice?" or "Are you an existing customer?"
* Summary views that should show a simple yes/no split.
## Settings to check [#settings-to-check]
* **Required** if the branch or workflow depends on the answer.
* **Question wording** so "Yes" and "No" are unambiguous.
* **Logic rules** for each branch.
* **Follow-up text** when one answer requires explanation.
## Workflow notes [#workflow-notes]
Yes/No is clearer than a two-option [Multiple choice](/help/build/question-types/multiple-choice) question when the answer is a true binary. If the answers are not literally yes and no, use [Multiple choice](/help/build/question-types/multiple-choice) with custom labels.
## Related types [#related-types]
Use for confirmations.
Use for custom labels.
# Terms and privacy (/help/resources/terms-privacy)
Access Mokaform terms, privacy notices, cookie information, data processing terms, policies, and legal resources.
## Overview [#overview]
Use these pages to review the legal and privacy information that applies to Mokaform accounts, hosted forms, respondents, providers, and customer data processing.
Review the terms for accounts, forms, uploads, integrations, billing,
acceptable use, and customer responsibilities.
Review the DPA for customers using Mokaform to process personal data.
Open the formal Privacy Policy and Cookie Policy.
Open practical privacy and cookie notices written for readability.
# Privacy and cookie policies (/help/resources/terms-privacy/policies)
Review the formal Mokaform privacy policy and cookie policy for personal data, cookies, providers, retention, and rights.
## Overview [#overview]
Policies are the formal legal documents for Mokaform's privacy and cookie practices.
Read the canonical policy for how Mokaform collects, uses, shares, stores,
and protects personal data.
Review the formal policy for cookies and similar technologies.
# Privacy and cookie notices (/help/resources/terms-privacy/notices)
Read customer-friendly Mokaform privacy and cookie notices for account holders, form creators, visitors, and respondents.
## Overview [#overview]
Notices explain Mokaform's privacy and cookie practices in a practical format for customers, account users, visitors, and respondents.
Read the practical privacy notice for customers, visitors, account users,
and respondents.
Understand cookie categories, consent choices, provider links, and
server-side media providers.