splitforms.com
Get free key
WAITLIST · AJAX (VANILLA JS)

Waitlist for AJAX (vanilla JS)

Pre-launch capture form with optional referral source. Free for 500 submissions per month — no backend, no SDK, no plugin.

Get free access key Copy the code
500/mo free·no card·drop-in for AJAX (vanilla JS)
form.htmlhtml23 lines
01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New waitlist signup">
04 
05  <label for="email">Email *</label>
06  <input id="email" type="email" name="email" placeholder="you@example.com" required>
07  <label for="name">Name</label>
08  <input id="name" type="text" name="name" placeholder="Optional">
09  <label for="referral">How did you hear about us?</label>
10  <select id="referral" name="referral">
11    <option value="">Choose…</option>
12    <option>Twitter</option>
13    <option>Friend</option>
14    <option>Search</option>
15    <option>Newsletter</option>
16    <option>Other</option>
17  </select>
18 
19  <!-- honeypot — bots fill every field -->
20  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
21 
22  <button type="submit">Send</button>
23</form>
500
submissions / mo, free
3
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00AJAX (vanilla JS) + Waitlistplatform-specific integration guide

Why AJAX (vanilla JS) developers choose splitforms for waitlist

The waitlist on this page integrates with AJAX (vanilla JS)'s development workflow using the form markup in your AJAX (vanilla JS) project. Whether you're deploying to a static host or a server-rendered platform, the form posts standard <code>FormData</code> to splitforms, so your backend complexity stays at zero. AJAX (vanilla JS)'s ecosystem has strong tooling for UI, but form delivery is a separate concern that splitforms handles independently — Free includes spam filtering and a submissions dashboard; Starter adds email notifications and webhooks.

§ 00Quick answerHTML · marketing

Yes — this is the shortest safe path for AJAX (vanilla JS).

Use the HTML snippet on this page, keep the waitlist fields visible in your AJAX (vanilla JS) UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the HTML version, then replace YOUR_ACCESS_KEY.

The posted payload contains email, name, how did you hear about us?. Required fields are email.

native ajax (vanilla js) reality

Vanilla JS / AJAX forms have been the no-framework default since jQuery's heyday.

use case fit

Pre-launch waitlists let you capture demand before the product ships. The multi-step form qualifies the use case so launch-day conversions skew toward the highest-intent signups.

§ 01Waitlist × AJAX (vanilla JS)why this combination, in 80 words

Built for AJAX (vanilla JS) developers who hate operating a backend.

Splitforms is the form backend for AJAX (vanilla JS) sites. One POST endpoint, no SDK, no plugin — drop the waitlist into a page and ship.

Splitforms is the form backend for AJAX (vanilla JS) sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.

✦ what you get on the free plan
  • ✓500 form submissions per month
  • ✓2 forms on Free; unlimited forms on Pro
  • ✓Spam protection (honeypot + classifier)
  • ✓Webhooks: Slack, Discord, WhatsApp, custom
  • ✓CSV export of all submissions
  • ✓Email notifications (CC and BCC on Pro)
§ 02Copy-paste codeHTML · 23 lines

Drop into any AJAX (vanilla JS) project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a AJAX (vanilla JS) page, and ship. No build-time integration required.

form.htmlhtml23 lines
01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New waitlist signup">
04 
05  <label for="email">Email *</label>
06  <input id="email" type="email" name="email" placeholder="you@example.com" required>
07  <label for="name">Name</label>
08  <input id="name" type="text" name="name" placeholder="Optional">
09  <label for="referral">How did you hear about us?</label>
10  <select id="referral" name="referral">
11    <option value="">Choose…</option>
12    <option>Twitter</option>
13    <option>Friend</option>
14    <option>Search</option>
15    <option>Newsletter</option>
16    <option>Other</option>
17  </select>
18 
19  <!-- honeypot — bots fill every field -->
20  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
21 
22  <button type="submit">Send</button>
23</form>
§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first waitlist submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.

Create your form
key=sk_live_••••••••
STEP 02EMBED

Paste the waitlist into your AJAX (vanilla JS) project

Drop the form snippet into a AJAX (vanilla JS) page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.

snippethtml
<form action="https://splitforms.com/api/submit" method="POST">
  …
</form>
STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now
FROM contact@yoursite.com
New waitlist signup
Maya Iyer maya@studio71.co
Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?
§ 03bWaitlist Signup Form (Pre-Launch Lead Capture)template-specific playbook

The reason this waitlist exists.

Multi-step (Typeform-style) · webhooks into Loops / ConvertKit / Beehiiv.

why it matters

Waitlists are the cheapest growth tool a pre-launch product has — Superhuman, Notion, and Linear all built sizable waitlists before paid launch. The form captures email plus a question or two on use case ('what would you use this for?', 'what tools do you use today?') so the launch sequence segments by intent. Multi-step flow boosts completion vs a single form — the prospect commits in step 1 and answers the qualifying questions in step 2-3 with momentum. Push waitlist signups to a dedicated ESP audience (Loops, ConvertKit, Beehiiv) so launch-day emails segment by use case and target the highest-intent signups first.

route the submission
01

Step 1: capture email

Single email field — keep step 1 frictionless. Loss-rate from email-only is near-zero; once the email is in, momentum carries through later qualifying questions.

02

Step 2-3: qualify use case

One or two questions on use case ('what problem brings you here?', 'what tools do you use today?'). Optional but most users complete because they're invested by step 2.

03

Push to ESP segment

Webhook to Loops / ConvertKit / Beehiiv / Mailchimp into a 'waitlist' audience. Launch-day emails segment by use case so the highest-intent signups get the first invite waves.

§ 03cAJAX (vanilla JS) production notesnative path · deploy · gotchas

What changes when this waitlist lives in AJAX (vanilla JS).

These notes come from the AJAX (vanilla JS) platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

Vanilla JS / AJAX forms have been the no-framework default since jQuery's heyday. Without splitforms, the 'AJAX' part is one fetch line; the operational part is everything else: a backend route, an SMTP provider, a database for submissions, a honeypot or reCAPTCHA, a thank-you page, error handling for HTTP 4xx/5xx, retry logic. For 'JS-only on a static host' setups (Cloudflare Pages, GitHub Pages, S3), there's literally no server to run the route on — historically that meant Formspree, Formspark, Web3Forms, Basin. Splitforms is the modern entry: same shape, better free tier, better spam filtering, and signed webhooks from Starter.

deploy notes

Vanilla JS deploys to any static host — the snippet is HTML + inline <script>, no build step. CSP: if your site sets connect-src 'self', add https://splitforms.com to the directive or fetch is blocked. Browser support: native fetch is in every browser back to Edge 18 — the snippet runs without polyfills on every market-share-relevant browser. The progressive-enhancement variant (Pattern B) keeps the form working when JS fails to load — useful on flaky networks, ad-blocked clients, or for accessibility tools that disable JS.

AJAX (vanilla JS) gotcha

Forgetting e.preventDefault() reloads the page

Without preventDefault, the browser does its own form submission to wherever the form's action attribute points (or the current page) AND your fetch runs. You see a flash, the page reloads, and your handler's effects are lost.

AJAX (vanilla JS) gotcha

FormData includes ALL form fields — even disabled ones get dropped

new FormData(form) skips inputs without a name attribute, skips disabled inputs, skips unchecked checkboxes/radios. If a field doesn't show up in your splitforms inbox, check whether it's disabled at submit time.

AJAX (vanilla JS) gotcha

fetch() doesn't reject on HTTP 4xx/5xx — only network errors

If splitforms returns a 401 (bad key) or 429 (rate limit), fetch resolves successfully. You have to check res.ok or data.success yourself. Wrapping in try/catch only catches network failures, not HTTP errors.

AJAX (vanilla JS) gotcha

Double-click submit fires two requests

Without disabling the button on the first click, a quick double-click sends two POSTs. Both succeed; the user sees one success message; you see two submissions. Always set button.disabled = true at the start of the handler.

PATTERN A

Pattern A — fetch + FormData + status element

Single submit listener. new FormData(form) reads inputs, append the access key, POST. Update an aria-live status <p> with the result. ~25 lines, no library. Use the same wiring for the waitlist fields on this page.

pattern-a.htmlhtml16 lines
01<form id="cf">
02  <input name="email" type="email" required />
03  <textarea name="message" required></textarea>
04  <button type="submit">Send</button>
05  <p id="msg" aria-live="polite"></p>
06</form>
07<script>
08  document.getElementById("cf").addEventListener("submit", async (e) => {
09    e.preventDefault();
10    const fd = new FormData(e.currentTarget);
11    fd.append("access_key", "YOUR_ACCESS_KEY");
12    const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
13    const data = await r.json();
14    document.getElementById("msg").textContent = data.success ? "Thanks!" : (data.message || "Try again");
15  });
16</script>
PATTERN B

Pattern B — progressive enhancement (works without JS)

Form has a real action attribute and a redirect hidden field — works with JS disabled (browser POSTs natively, splitforms 302s). When JS is available, the listener intercepts for inline UX. Best of both worlds, no compromise. Use the same wiring for the waitlist fields on this page.

pattern-b.htmlhtml13 lines
01<form id="cf" action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
03  <input type="hidden" name="redirect"   value="/thanks.html" />
04  <input name="email" type="email" required />
05  <button type="submit">Send</button>
06</form>
07<script>
08  document.getElementById("cf").addEventListener("submit", async (e) => {
09    e.preventDefault();
10    const r = await fetch(e.target.action, { method: "POST", body: new FormData(e.target) });
11    if ((await r.json()).success) location.href = "/thanks.html";
12  });
13</script>
§ 04Field-by-field rundown3 fields · names you POST

What every field actually does.

Each field below ships in the waitlist template — rename, remove, or add your own. Splitforms accepts any name you POST.

emailREQUIRED
EMAIL

Email

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · you@example.com
name
TEXT

Name

Greeting + dashboard label so submissions don't all read 'anonymous'.

placeholder · Optional
referral
SELECT

How did you hear about us?

Dropdown — keeps responses normalised so you can filter the dashboard.

TwitterFriendSearchNewsletterOther
§ 05Waitlist on other frameworks22 frameworks · same backend

One backend. Every framework.

The same waitlist template works on every framework splitforms supports. Pick yours.

Waitlist for HTML/forms/html/waitlist →Waitlist for Next.js/forms/nextjs/waitlist →Waitlist for React/forms/react/waitlist →Waitlist for Vue/forms/vue/waitlist →Waitlist for Astro/forms/astro/waitlist →Waitlist for Svelte/forms/svelte/waitlist →Waitlist for Webflow/forms/webflow/waitlist →Waitlist for Carrd/forms/carrd/waitlist →Waitlist for WordPress/forms/wordpress/waitlist →Waitlist for Tailwind CSS/forms/tailwind/waitlist →Waitlist for Hugo/forms/hugo/waitlist →Waitlist for Gatsby/forms/gatsby/waitlist →Waitlist for Eleventy/forms/eleventy/waitlist →Waitlist for SvelteKit/forms/sveltekit/waitlist →Waitlist for Framer/forms/framer/waitlist →Waitlist for Nuxt/forms/nuxt/waitlist →Waitlist for Bootstrap/forms/bootstrap/waitlist →Waitlist for Jekyll/forms/jekyll/waitlist →Waitlist for JavaScript/forms/javascript/waitlist →Waitlist for Cloudflare Pages/forms/cloudflare/waitlist →Waitlist for Netlify/forms/netlify/waitlist →Waitlist for Vercel/forms/vercel/waitlist →
§ 06Questions9 answered

Waitlist on AJAX (vanilla JS) — FAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this waitlist work on AJAX (vanilla JS)?
Yes. The form is plain HTML with a single POST endpoint, so it runs on any AJAX (vanilla JS) site without server-side code, plugins, or SDKs. Drop the snippet into a AJAX (vanilla JS) page or component and submissions land in your splitforms dashboard.
02How much does the waitlist cost on AJAX (vanilla JS)?
Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.
03Can I customize the fields?
Yes. The template ships with sensible defaults (email, name, how did you hear about us?…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.
04How does spam protection work on the waitlist?
A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on AJAX (vanilla JS) as on any other framework.
05Can I send the waitlist submissions to Slack or Discord?
Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.
06Will it work on a static AJAX (vanilla JS) site?
Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.
07Should I show waitlist position / numbers?
Showing 'you're #347 in line' on the confirmation creates social proof but invites comparison. Showing total waitlist size ('join 2,500 people on the waitlist') without per-person position is the safer middle. Refer-a-friend mechanics that move people up the list (Robinhood-style) drive viral growth but require more eng work.
08How do I trigger launch invites in waves?
Tag waitlist signups by use case in the ESP audience (Loops, ConvertKit). Launch-day, segment by tag and send invite waves over 48-72 hours. Highest-intent / closest-fit goes first; broadest casts go last. Spreads server load and lets you triage onboarding support.
09Can I integrate with Loops / ConvertKit / Beehiiv?
Yes — webhook the JSON. Loops has direct webhook support and is purpose-built for product transactional + waitlist email. ConvertKit and Beehiiv accept via API or Zapier. All three handle the launch-sequence segmentation cleanly.
§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

FeatureWeb3FormsFormspreesplitforms
Free monthly submissions25050500
Custom fields beyond contactYesPro tierFree
Webhooks (Slack / Discord)Pro tierPro tierFree, signed
AI / MCP submission inboxNoNoYes
Long-term plan (3-year flat)——$59 every 3 years
§ 08More templates for AJAX (vanilla JS)0 adjacent patterns

Other ready-to-ship AJAX (vanilla JS) forms.

Same backend, different qualifying fields. Click through to copy the snippet.

✦ keep browsing on AJAX (vanilla JS)
    ✦ waitlist on other frameworks
    ✻ ✻ ✻

    Ship a waitlist on AJAX (vanilla JS) in 60 seconds.

    500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your AJAX (vanilla JS) project.

    Get free access key →Read the docs
    founders pricing locked in · early access open