Build a registration form and confirm every sign-up
A community coding workshop runs three sessions a month. The organiser needs a clean roster, wants to know the moment somebody signs up, and wants the attendee to get a confirmation without anybody typing one.
- The scenario
- A volunteer-run workshop with limited places. Sign-ups arrive from a landing page and a couple of social posts, and the organiser wants to know which is which.
- What you end up with
- A registration form you can paste onto any page, a Sheet roster with the campaign each sign-up came from, an alert to the organiser, and a receipt to the attendee.
- You need
- Sheets and Drive connected, and Gmail sending connected for the two emails
- A Pro workspace for submitter receipts. Owner alerts work on every plan; on Pro they come from your own Gmail
- The domain the sign-up page is published on
-
Setup › Questions › Edit questions
Open the Builder on the Event registration preset
Make the connection with New connection and name it
Saturday coding workshop— this is the name the Sheet takes in Drive, so make it specific enough to find. In its Setup's Basics, allow the site the form will be published on under Websites.Then, in Questions, select Edit questions. The Builder takes the whole window: your questions as a list on the left, the settings of the one you select beside it and, from 1280px wide, the live preview. A preset is a starting point, not a finished form: open Form heading and presets, and under Builder preset choose Event registration. The questions arrive with sensible types already chosen, for you to change to what your event actually needs.
Open full size
Save fields saves them to the connection; Close, or Esc, returns you to Setup. -
Builder
Replace the sample answers with your real ones
The preset's Session field arrives with generic options, and the Builder says so in as many words: these are sample answers, not a choice you have made. Replace them with your three sessions, one per line.
Open full size
Each field has a Label the visitor reads and a Parameter that becomes the Sheet column header. Keep parameters short and lowercase — you will type them again in formulas. Four fields is enough for a roster: who is coming, how to reach them, which session, and anything you need to know before they arrive.
Open full size
The preview renders the same markup the generated code produces, so what you check here is what your page will show. Narrower than 1280px, it is the Builder's Preview tab. Select Save fields. A connection that is already on a site says so beside its fields: the page needs the new code, copied again.
-
Setup › Submission handling
Leave the spam check on
Open full size
Every setting here already has a working default. The website list is not among them: it is in Basics, beside the connection's name. Spam check is on by default for a form built here and there is nothing to set up: no key to obtain, no account to create, no domain to register anywhere. It works on whatever domain you publish to, from the moment you publish.
Your visitors see nothing. When somebody starts filling in the form their browser quietly works on a short puzzle and sends the answer with the submission, normally long before they press send. Somebody who submits instantly may briefly see Finishing a quick anti-spam check… and then goes through as usual.
What it does, and what it does notIt makes bulk automated sending expensive, because every submission costs the sender real computing time. It is not a bot detector and will not stop a determined, well-resourced sender. Your allowed websites and your monthly limit are what cap who can reach the form and how much they can send, and both apply whether this is on or off.
How long answers are kept, under Security in Advanced, is a Pro choice between 7, 30 and 90 days. It governs Webtzm's own copy of what was submitted, not the Sheet — the roster keeps its rows either way.
-
Setup › Advanced › Extra Sheet columns
Decide what else the roster records
This is the only group that changes how many columns your Sheet has. Everything else changes what goes in a column.
Open full size
Each switch says how many columns it adds. For a workshop that advertises in two places, turn on Campaign and landing page. It adds six columns — source, medium, campaign, term, content and the landing URL — and answers “which post filled the morning session” without anybody guessing.
In Google output, leave Tuck Webtzm's own columns out of the way on. The record reference and delivery timestamps stay in the Sheet, grouped out of the way and marked as protected. They keep working; you just stop looking at them.
One question, several ticked answersSeveral answers in one cell decides how more than one selected answer is written into a single cell: commas, pipes, one per line, or a JSON list. Pick pipes if any of your answers can themselves contain a comma — otherwise a row with two answers reads the same as a row with one.
-
Setup › Advanced › Language and time
Set the timezone the roster is read in
Timestamps default to UTC, which is correct and unreadable. A workshop organiser reading “09:00” wants their own clock, not Greenwich's.
Open full size
Choose your own city. Visitor browser timezone is also available, and needs Browser and form language switched on under Extra Sheet columns. -
Setup › Advanced › Delivery and alerts
Turn on the alert and the receipt
Two different messages, to two different people, for two different reasons.
Open full size
The recipient of a receipt is a field on your own form, chosen explicitly. Webtzm will not guess which field holds an email address. - Email me for each submission tells the organiser that somebody signed up. It is in Submission handling, rather than here.
- Email me when a delivery needs review tells the organiser when a delivery needs attention. Leave this on — it is how you find out about a problem without watching the console.
- Send each person a receipt sends one confirmation to the attendee. Choose Email under Their email is in first.
- A submission sent twice is kept once is always on and cannot be turned off.
These need Gmail sending connectedReceipts, failure alerts and Pro's own-address alert are sent through your Gmail account. Until it is connected each switch is visible and unavailable, and Setup offers Connect Gmail beside it: Google opens in a small window of its own, and the connection you are setting up stays exactly as you left it.
-
Setup › Advanced › Get the form code
Copy the code
There is nothing to create: every section saved as you changed it. Get the form code, in Advanced, offers Copy form HTML, and the Builder's Code tab shows the same markup. This is the exact markup below — generated from the fields and settings you just chose, with your own form id in the
data-webtzm-formattribute.Generated form HTML — copied from the console, unedited <form class="wtzm-form" action="https://webtzm.com/submit" method="post" data-webtzm-form="YOUR_FORM_ID" data-wtzm-enhancement="client" data-wtzm-format-events="submit" data-wtzm-validation-style="red" data-wtzm-block-invalid="true" data-wtzm-validation-messages="true" data-wtzm-status-feedback="true" data-wtzm-lock-submit="true" data-wtzm-text-trim="true" data-wtzm-text-clean="true" data-wtzm-text-truncate="false" data-wtzm-text-max-chars="50000" data-wtzm-capture-referrer="false" data-wtzm-capture-utm="false" data-wtzm-capture-locale="false" data-wtzm-timestamp-zone="UTC"> <input type="hidden" name="_webtzm_form" value="YOUR_FORM_ID"> <div data-wtzm-field="name"> <label for="name">Full name <span class="wtzm-required" aria-hidden="true">*</span></label> <input id="name" type="text" name="name" placeholder="Enter full name" required> </div> <div data-wtzm-field="email"> <label for="email">Email <span class="wtzm-required" aria-hidden="true">*</span></label> <input id="email" type="email" name="email" placeholder="name@example.com" required> </div> <div data-wtzm-field="session"> <label for="session">Session <span class="wtzm-required" aria-hidden="true">*</span></label> <select id="session" name="session" required> <option value="">Select Session</option> <option value="Morning · 9am to 12pm">Morning · 9am to 12pm</option> <option value="Afternoon · 1pm to 4pm">Afternoon · 1pm to 4pm</option> <option value="Full day">Full day</option> </select> </div> <div data-wtzm-field="dietary_notes"> <label for="dietary_notes">Dietary notes</label> <textarea id="dietary_notes" name="dietary_notes" rows="4" placeholder="Enter dietary notes"></textarea> </div> <p data-wtzm-send-status role="status" aria-live="polite"></p> <button class="wtzm-submit" type="submit">Submit form</button> </form> <link rel="stylesheet" href="https://webtzm.com/assets/styles/public-form.css?v=20260906-public-form-10"> <link rel="stylesheet" href="https://webtzm.com/assets/styles/embed-files.css?v=20260906-public-form-10"> <script src="https://webtzm.com/assets/enhance-files.js?v=20260906-public-form-10" defer></script> <script src="https://webtzm.com/assets/enhance.js?v=20260906-public-form-10" defer></script>The attributes are the settingsEvery choice you made is stated on the
<form>element — the timezone, the validation style, whether the spam check runs. Change a setting later and you must copy this code again and replace what you published, because a page still carrying the old choice will not match what the form now enforces. -
Your own site
Publish it, and see what an attendee sees
Paste the block onto your sign-up page. The two stylesheets and two scripts do the visible work: they style the form, validate it in the browser, run the anti-spam check, and report the result inside the page.
Open full size
The form as published, using the stylesheet the generated code links. It inherits your page's width and typography rather than imposing a widget.
Open full size
A required field left empty. Nothing was sent, and nothing was recorded — this is a rejection before acceptance, so there is no submission to retry.
Open full size
Filled in and ready. The anti-spam check has already been solved in the background by this point, so pressing send does not wait for it.
Open full size
A real accepted submission, shown in the plain default text. A form's own Success message, if one is set, replaces this. Delivery is confirmed on your side, in Analytics.
What the organiser ends up with
One spreadsheet, one row per registration, and two emails per registration that nobody had to write.
| Column | Source | Note |
|---|---|---|
webtzm_id | Webtzm | Hidden and protected. Needed if you later let attendees change their own booking. |
name, email, session, dietary_notes | The form | Named after each field's parameter. |
utm_source … landing_url | UTM switch | Six columns. Which post or page the sign-up came from. |
accepted_at, synced_at | Webtzm | Hidden. Written in the timezone you chose. |
Open full size
The attendee gets a confirmation of their own, and it is deliberately thin:
Subject: We received your submission — Saturday coding workshop
Your submission to Saturday coding workshop has been received.
Reference: 83215b5a-e476-4773-b522-f36bace78aec
This confirmation intentionally does not repeat your submitted answers.
It confirms the submission and carries the reference, and it does not repeat what was submitted. That is on purpose: a confirmation lands in an inbox neither you nor the attendee controls, and an answer repeated there is an answer stored somewhere you never chose.
If you want a tidy version to share with volunteers — only the columns that matter, under readable names — the connection's Google output can add a clean view: a second tab in the same spreadsheet, live rather than copied, which updates itself and can never disagree with the record. It is for reading and sharing, not for editing.