Back to Help

Creating an HTML email subscribe form

If you are coming from an email service provider such as Mailchimp, you will be familiar with the concept of HTML-based email forms.

These forms allow you to collect a subscriber or customer’s email address, name, and other (custom) details easily using a little HTML on your website.

Vero subscribe forms

Vero also supports email forms, with one key difference. Traditionally, when a contact fills out an email form, they are added to a list. In Vero, rather than being added to a list, a customer that fills out a web form triggers an event. That event could be as simple as Subscribes to blog.

You can then use this event to create a segment or trigger a workflow to automatically send email and/or push messages: so you get twice the power from a single web form!

Step 1. Create a form

To generate a form, head to Forms and you’ll be shown Vero’s point-and-click interface to create a form:

Subscribe form properties

Vero forms always collect the customer’s email address, but you can collect any fields you want. You can view the fields you’ve used in previously, on the left-hand side.

You must then define the event that will be triggered when the customer fills out this particular form.

The final part of our form builder allows you to define what your customers see after completing the form:

Subcribe form event trigger

Step 2: Copy and paste your new form

Select ‘Generate form’ to generate the HTML for your new form:

Subscribe form code

Select copy to clipboard and paste this code in your CMS or website and you are good to go!

By default, we’ll show them a confirmation screen that looks like this:

Subscribe form success

You can define a screen/landing page to direct contacts to if they fail to complete the form successfully (i.e., enter an invalid email) or when they do complete the form successfully. Generally, this would be a custom “Thanks for subscribing” page.

Didn't find what you were looking for?

Get in touch, we're always happy to help. Email us at:

Improve our docs

Our help docs are open to everyone, help us make them better by contributing on Github and you'll be our new best friend!

Search Results: