Forms

Form structure

Mailrith forms are built from modular blocks that you combine in the form editor. Every form starts with an email capture field — this is required — and you can add more blocks to build a complete sign-up experience:

• Custom field inputs: map any of your workspace's custom fields as form inputs. When a subscriber submits the form, their values are saved directly to the corresponding field on their subscriber record.
• Text blocks: add headlines, paragraphs, or explanatory copy between fields. This lets you provide context for what you are collecting without needing a separate page element.
• Submit button: customize the label to match the form's context — "Subscribe", "Get Access", "Join the Waitlist", or anything else appropriate.

Forms can also apply one or more tags on submission. A subscriber who fills out your product updates form automatically receives the "product-updates" tag without a separate automation step — the acquisition and the categorization happen in the same action.

Submission settings

After a subscriber submits the form, Mailrith can do one of two things:

• Show a success message: the form fields are replaced with a confirmation message in-place. Best for embedded forms where you want to keep the visitor on the current page rather than sending them somewhere new.
• Redirect to a URL: the subscriber is sent to a confirmation page, resource download, or next step in your funnel. Best when you have a dedicated thank-you page or want to deliver a gated asset immediately after sign-up.

You can also configure behavior for returning subscribers — people who are already in your Mailrith audience when they submit the form. Mailrith can update their existing record and apply new tags without creating duplicate contacts, while still showing them the success experience.

Embed and share

Once a form is published, Mailrith generates an embed code that you paste into any HTML page or website builder. The embedded form connects directly to your Mailrith workspace and starts capturing subscribers immediately — no backend setup required on your end.

To get the embed code, open the form and navigate to the Share tab. Copy the provided snippet and paste it wherever you want the form to appear: a landing page, a blog sidebar, a product marketing page, or a checkout confirmation screen.

When you update a published form's content or submission settings, existing embeds automatically reflect the latest version. You do not need to re-copy and re-paste the embed code after making changes.

Form operations

From the forms list, you can manage the full lifecycle of each form:

• Duplicate: create a copy to test a variation or reuse a structure for a new campaign without starting from scratch. The duplicate is created as a draft so you can edit before publishing.
• Edit: update fields, submission settings, success messaging, redirect URL, or applied tags at any time. Existing embeds pick up changes automatically.
• Delete: remove a form when it is no longer needed. Mailrith asks for confirmation before deleting. Deleting a form does not remove subscribers who already submitted it — their records remain in the workspace.

Mailrith warns about unsaved changes before you navigate away from the form editor, so you will not lose work if you accidentally click a different section of the app.