Where Your Form Appears
One form, one address, many places to put it
Every form has a single public web address, and everything else is a way of pointing at it. There is no separate published copy and no per-channel version — a change to the form takes effect everywhere at once.
This article covers the address itself, the surfaces a form can appear on, and the parameters the address accepts.
The form's own address
| Aspect | Detail |
|---|---|
| Shape | Your Zyntro address, then /public/forms/, then your account identifier, then the form's identifier. |
| Where to find it | The form's name in My Forms links straight to it. That is the quickest way to copy it. |
| Stability | It never changes. Renaming a form, restyling it or editing its fields leaves the address alone, so existing links and embeds keep working. |
| Draft forms | Reachable and completable. Draft affects visibility to Segmentation Intelligence, not public access. |
| Authentication | None. Anyone with the link can complete the form. |
Warning: Treat the address as public. There is no login in front of a form, and as of October 2026 the password option on the creation screen is not enforced. Do not put questions on a form that you would be uncomfortable having a stranger answer.
Surfaces a form can appear on
| Surface | How it works | Requires |
|---|---|---|
| A shared link | Send the address in an email, a message, a social post or a document. The most common way by far. | Nothing. |
| A QR code | Generated from the form's row menu. It encodes the address with a campaign value attached, so scans are attributable without extra work. | Nothing. |
| Embedded in a web page | Place the form inside a page using an inline frame pointing at its address. | Somewhere you can edit the page's markup. |
| Inside an artefact | Artefacts are the interactive experiences you build to share with clients — calculators, assessments, guides, dashboards. A form can be dropped into one, and the embed code is generated for you. | A Published form. |
| Offered to an AI agent | Connected agents can be given your forms, so an agent in a conversation can point somebody at the right one. | A Published, public form. |
| Referenced by Segmentation Intelligence | SI can reference a form in the email, SMS and broadcasts it generates. | A Published form. |
| Wired into another Zyntro flow | Several features accept a form to use at a particular point — covered in its own article. | Varies by feature. |
Important: Several of these surfaces only offer Published forms. A Draft form works perfectly at its own address, but it will not appear as an option when you are placing a form inside an artefact, and connected AI agents cannot see it. If a form is missing from a picker, check its status first.
Parameters the address accepts
| Parameter | What it does |
|---|---|
| Your own hidden-field parameters | Any parameter a hidden field is configured to read is picked up and recorded. This is how campaign and source tracking works. |
| A contact identifier | Pre-fills the form from a contact you already hold. Use it in links you send to known people. |
| Skip the welcome screen | Jumps straight to the fields. The builder's own preview uses this, and it is occasionally useful in an embed where an introduction screen would waste space. |
| Booking pre-selection | Pre-selects a time and location on a form that takes bookings, so somebody arriving from a link lands on a chosen slot. |
| Legacy renderer | Forces the previous form renderer. A fallback, not something to use routinely. |
Info: An embed parameter appears in generated embed code but currently has no effect (as of October 2026). The form renders identically with or without it. Leave it in place if a generated snippet includes it — it does no harm — but do not expect it to change anything.
Tip: Because every surface points at the same address, you fix a typo once. The flip side is that there is no way to vary a form by channel — if you need different questions for different audiences, duplicate the form and use two addresses.
