Legacy Signup Forms vs. Built-In Signup Forms

read
Last updated at:

Overview

Klaviyo's native Signup Form Builder streamlines the process of adding a signup form to your website. Using the drag-and-drop interface, it's no longer necessary to hardcode forms into specific pages on your website. If you're using Shopify, Bigcommerce, Magento 1, or WooCommerce, a short snippet of code is added to your site when you integrate with Klaviyo. This is what enables us to publish signup forms directly to your site.

If you're using a custom integration or one that's not listed above, simply paste this snippet of code into the header of your site once and, going forward, whenever you publish a new form in Klaviyo, it will appear automatically.

Please note that the process has not changed to edit the opt-in related pages for a particular list; to edit your account's default email forms, navigate to the Preferences Pages tab.

Built-in signup forms will not render for browsers using Internet Explorer. Legacy signup forms will continue to render for those using any type of web browser.

Key Differences Between the Built-In and Legacy Signup Forms

  Legacy Built-In
Setting Up Legacy signup forms must be hardcoded into the specific page(s) on which you would like the form to appear.

Through your integration, or after a one-time installation of code on in the header of your website, signup forms will appear automatically on your site when published. One exception to this is embedded forms, which require you to paste a small snippet of code where you would like the embedded form to display on your site.

Building the Form

Legacy signup forms must be manually built and configured outside of Klaviyo. 

Head to the Signup Forms tab in the lefthand sidebar in your account. This is where you can build and edit the forms that appear on your site using our new drag-and-drop interface.
Support Because legacy forms use custom HTML and CSS, our support team is unable to assist with troubleshooting legacy forms.

Email and Chat Support

 

x
Was this article helpful?
20 out of 47 found this helpful