Build Forms Faster with these Five Improvements

Duplicate forms, embed more than one on a single page, customize the thank-you page, and more with recent updates to Forms.
More control at every stage of the form creation and usage
Each update removes a specific friction point in how partners and SMBs create, deploy, and manage forms:
Form duplication.
 Copy any existing form with a single click. A preview of the duplicate appears before it's created, so you can confirm you have the right form before committing. This is particularly useful for partners running recurring webinars who reuse the same structure each time, and for enterprise deployments like Italiaonline that require consistent consent fields across many forms.
Multiple forms on one page.
 A small change to the embed script now lets partners place two or more distinct forms on the same page with isolated CSS — no more iframe workaround. Each form renders and behaves independently.
Customizable submission settings.
 After a visitor submits a form, you can now show a success page with a custom thank-you heading and message or redirect them to any URL. If desired, show a "go back" button so they can submit again without refreshing the page.
Geolocation-based form translations.
 Validation error messages (like "invalid email" and "invalid phone number") that were previously hardcoded in English now display in the visitor's language based on their location — automatically, with no configuration needed.
Notification translations.
 Form submission notification emails now follow the recipient's language rather than being locked to the language the form was built in. Notifications are configured the same way as automations, making the behavior consistent across the platform.
Why it matters
These five updates address a range of common complaints from partners managing forms at scale. Recreating a form from scratch for every webinar, working around the one-form-per-page limitation with iframes, landing international visitors on English error messages, and building separate notifications for different language markets were all real friction points. This sprint resolves all of them in one release.
Who it's for
Businesses running recurring events or webinars who want to reuse form configurations
Businesses operating in multilingual markets (e.g., Italiaonline, other non-English deployments)
Any business that wants more control over the post-submission experience
How to get started
Duplicate a form
Go to Partner Center or Business App > Marketing > Forms
Find the form you want to copy and click "Duplicate"
Review the preview of the new form before confirming
Rename and edit the duplicate as needed
Note: Automations are not copied when duplicating forms.
Embed multiple forms on one page
Get the embed script for each form from its Share / Embed settings
Add both scripts to your page, no iframe needed
Each form renders with isolated CSS and won't interfere with the other
Customize what happens after form submission
In the Form Builder, open Settings > Submission
Choose to redirect to a URL on submit, or set a custom thank-you heading and message.
Toggle on the "Resubmit button" if you want visitors to be able to submit again without a page refresh
Set up notification translations
Go to the form's "Notifications" tab
Configure notifications the same way as an automation. The recipient's language is applied automatically
Note: Geolocation-based translations for validation errors are automatic and require no setup.
FAQs
Q: Does duplicating a form copy everything: fields, settings, conditional logic?
A: Yes. The duplicate is a complete copy of the original. Review it in the preview before saving and adjust anything that needs to be specific to the new use case.
Q: Do I need to configure anything for geolocation translations to work?
A: No. Validation error translations (email, phone format, etc.) apply automatically based on the visitor's location for all forms.
Q: Can I embed more than two forms on a single page?
A: Yes. The change removes the previous one-form limitation. Each form runs with isolated CSS regardless of how many are on the page.
Q: If I hide the go-back button, can visitors still resubmit?
A: Without the go-back button, visitors would need to manually refresh the page to submit again. Enabling the button removes that friction.
Q: Will existing form notifications change languages automatically after this update?
A: Going forward, notifications will follow the recipient's language. Notifications previously locked to a campaign language will now use the unified translation logic.