Open a template and switch to the Issuance form tab. The builder has a live preview beside it showing exactly what visitors will see, with a desktop/mobile toggle.
Form details
Enable turns the form on. Off, the link shows an unavailable page.
Form name is shown to visitors as the heading. Write it as an invitation rather than a description - "Join the club" reads better than "Membership form".
The public link is displayed here with a copy button.
Fields
Each field you add asks the visitor for one thing. A field has:
- A type - single-line text, a dropdown, or a date.
- A label - what the visitor sees.
- Required - whether they can submit without it.
- Options - for dropdowns only.
- Connects to - which template field the answer is written into.
Connects to is the important one. It's what turns "what the visitor typed" into "what appears on the pass". A field asking for a name should connect to the template's name field, so the answer shows up there.
If you later delete a template field that a form field was connected to, that form field is dropped the next time the form is saved. It has nowhere to put its answer, so keeping it would collect information that can never reach a pass.
Check the form tab after making significant changes to a template's fields.
Keep forms short. Every additional field costs you completions, and you can always ask for more later once someone is a pass holder. Name and email is usually enough; name alone is often enough.
Prefilling from the URL
Query parameters let a link carry answers with it. Map a parameter name to a template field, and ?member=10248 arrives with that value already filled in.
This is useful when you're sending the link to people you already know something about - an email campaign where you know each recipient's reference, or a per-customer link in an order confirmation.
Anything in a URL is visible and editable by the visitor. Prefill is a convenience, not a guarantee - don't use it for anything you need to trust. If a value must be correct, don't collect it through a public form at all; create the pass over the API.
Design
- Header image - your logo or a banner across the top. Recommended around 360x110 pixels, with a transparent background.
- Favicon - the small square icon in the browser tab.
- Background, component and font colours - the page, the form card, and the text.
- Button background, button font and button text - the submit button and its wording.
Button text is worth a moment's thought. "Get my pass" outperforms "Submit" because it says what happens next.
Watch the preview as you go, and check the mobile view - most people will open this on a phone.
Footer
An optional line at the bottom of the form, with its own text colour, plus an optional link.
Use it for a privacy policy link, a terms link, or a line explaining who's issuing the pass.
The footer takes plain text and a link, not markup - and links must start with http:// or https://. That's a deliberate restriction: the form is a page on our domain, so allowing arbitrary markup or other link types would let anyone configuring a form run code on it.
Legal consent
Add a consent message and choose whether ticking it is required.
If required, the visitor can't submit without ticking. Use it where you need explicit agreement to terms or to marketing contact. Keep the message short and link to the full policy in the footer.
Limits
Maximum passes caps how many passes the form may ever issue. Once reached, the form stops accepting submissions.
Use it for genuinely limited things - a capped event, a limited promotion, the first hundred sign-ups. Leave it empty for unlimited.
Publishing
Save the form. Before it accepts anything, PocketPass checks it's complete: a name, at least one field, a label on every field, options on every dropdown, a message if consent is required, and a valid URL if you've set footer link text. Anything missing is reported and the form stays off.
Bot protection is applied automatically - there's nothing to set up. If a form link shows an unavailable page, see My issuance form says it isn't available.
Test it before you publicise it
- Copy the public link.
- Open it in a private browsing window, so you're testing as a stranger rather than as a signed-in admin.
- Fill it in the way a real visitor would.
- Confirm you land on the install page and can add the pass.
- Check the pass in Passes and confirm the answers landed in the right fields.
That last step catches connected-field mistakes, which are the most common thing to get wrong and the least obvious from the form itself.
Where to go next
- What issuance forms are.
- Fields and regions - the template fields your form connects to.