Agent-readable docs index: /docs/llms.txt. Full docs in one file: /docs/llms-full.txt. Download /docs/docs.zip to grep all markdown files locally.

Collect contacts with published signup forms

Forms collect customer details into your workspace. Convert supports hosted, embedded, and popup form formats, with configurable fields, content, styling, consent, and a destination contact list. An in-app banner is a separate form kind with its own display configuration.

Build a signup form

  1. Open Forms and choose the form format or a starter design.
  2. Select the destination list owned by the current workspace.
  3. Add the fields you need, such as email, phone, first name, dropdown, or custom text.
  4. Add explicit consent for the channel and purpose the customer is subscribing to.
  5. Review required fields, labels, and confirmation behavior, then inspect the preview.
Ask only for useful data. A form intended for email updates should explain the email subscription clearly rather than implying consent to every channel.

Publish and install

Publish after reviewing the draft. Convert stores a published configuration snapshot. Use the hosted URL or installation instructions generated by the form's settings. Hosted form routes use /f/:public_id on your Convert application origin.
Use generated embed instructions instead of inventing scripts or endpoints. Test the published form on the actual page where visitors will see it, including a small mobile viewport and keyboard navigation.

Check submissions

Submit a controlled test with a fictional or authorised contact and verify the resulting contact list, mapped fields, and preference state. View form submissions and analytics, and distinguish page views from successful submissions.
Subscribe to form.submitted through customer webhooks if your application needs notifications. A form signup can also participate in segment rules and contact-created journeys when the configured list and trigger match.

Pause, archive and edit

Pause or archive through the form lifecycle actions when you need to stop intake. Review the published version after editing; a saved draft and the currently public configuration can differ until you publish again.
Next: manage contacts, review consent, or create a welcome automation.
Use a dedicated test list before connecting a form to a live welcome automation. A new contact can trigger published workflows.