> For the complete documentation index, see [llms.txt](https://docs.amondo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amondo.com/platform-guides/build/activation-tiles/forms.md).

# Form Tiles

Form Tiles capture structured audience responses inside an Imprint. They are used for lead capture, sign-ups, surveys, competitions and other data collection flows.

Form Tiles render in embedded Web SDK Imprints when they are included in the published layout. The form appears in the same Imprint or Frame experience as other activation Tiles, so no additional integration code is required beyond the standard Web SDK embed.

The Web SDK uses the public form page renderer for Form Tiles. Standalone hosted form links are available only when a standalone form page has been published.

### What you can do with Form Tiles

**Collect structured responses**\
Use fields to capture the data needed for the activation, such as contact details, preferences or survey answers. Form fields can include short text, email, multiple-choice and Yes/No inputs.

**Keep the journey inside the Imprint**\
Embedded Web SDK rendering lets audiences complete the form without leaving the host page.

**Combine with other activation Tiles**\
Use Form Tiles alongside Clickthrough, Quiz, Poll and Reveal Tiles in the same Collection and Imprint.

### Supported inputs

| Input type      | Use for                                                            |
| --------------- | ------------------------------------------------------------------ |
| Short text      | Names, handles, brief answers or free-text feedback                |
| Email           | Contact details for sign-ups, registrations or follow-up           |
| Multiple choice | Surveys, preferences, qualification questions or segmented opt-ins |
| Yes/No buttons  | Binary consent, opt-in, qualification or preference questions      |

Multiple-choice fields should use clear, mutually exclusive answer options. Use the Yes/No button variant for binary questions, and keep option labels short so they remain easy to scan on mobile.

### Web SDK behaviour

* Form Tiles are rendered from the published Imprint layout.
* No extra Web SDK configuration is required.
* Embedded Form Tiles use the public form page renderer; standalone hosted form links depend on a standalone page being published.
* Client-side validation runs per field and before submission.
* When a submission cutoff has passed, the form blocks submission and shows the configured closed-state messaging.
* Final CTA links only navigate when the URL uses a safe protocol. Unsafe-protocol final CTA links are stripped.
* Form Tiles emit canonical funnel events on embedded and standalone surfaces, including `form_viewed`, `form_started`, `field_filled`, `form_submitted` and `form_completed`.

See [Web SDK](/developer-guides/websdk.md) for embed setup and [Web SDK Events](/developer-guides/websdk-events.md) for analytics events.