Can I Use My Own Landing Page to Register Attendees?

With Livestorm, you can use your own landing pages to capture new registrations. Typically, if you want to track certain events, have a custom form or a custom design, you will want to use your own landing pages. There are two ways to do it at the moment: via our  Registration Widget or via our Zapier integration.


How to use Livestorm's registration widget

Once you have created and published your webinar you can grab the widget code of the registration form by clicking on this icon:

You can also grab it on your registration page when logged in to your Livestorm account:

Paste this code wherever you like (Wordpress, custom landing page, etc.). 

Pro tip: change the width attribute to change how fields are placed (if you need a column layout for example).

🚨GDPR compliance

If you choose to opt for Zapier, please make sure to collect consent from your registrants to use their data. This is required if you won't be using our registration page/widget.

When collecting consent please don't forget to store the time, IP address and the exact text of the consent for future references. 

Here's the consent your registrants have to give in order to register for your event on Livestorm :

" I agree to Livestorm's Terms of Service and the use of personal data as explained in Livestorm's Privacy Policy "

How to use Zapier to register someone from your landing page

Zapier is a tool that allows you to connect web apps together. An integration between two apps is called a Zap. A Zap is made up of a Trigger and an Action. Whenever the trigger happens in one app, Zapier will automatically perform the action in another app.

If you need to use your own custom HTML form, a Hubspot landing page, an Instapage landing page, or any other source, you must use Zapier to capture new registrations automatically in Livestorm.

You have a custom HTML form:

Zapier has a built-in feature called webhook. You can use them as API endpoints.

A webhook is a URL to which you are going to send your data. The webhook is like a recipient for data. Zapier provides webhooks to capture any kind of data and send it to a destination like Livestorm.

You webhook should look something like this:

Send some data in there and you're all set. Now, you can create forms and send the form data in that webhook. Then, all you have to do is create an action trigger with Livestorm.

Why do I need to create a Zap per session?

When you have multiple dates (sessions) you need to create a different zap for each date since the session cannot be set dynamically.

However, you can mark the "Which Session" above as "Custom Value" and then find a way to send it to Zapier dynamically. You have two options: send it as a hidden field from your form or search it inside a Google Sheet like explained  here.

You can find the session IDs in the URLs on your dashboard, when you filter your webinar with one.

You are using a landing page builder like Instapage

In Instapage, you want to add a webhook as a destination for your form. We suggest you to read this step by step tutorial on how to set up Zapier for Instapage.

Create a zap with your form submissions from Instapage. This will be the trigger. Then add an action with Livestorm:

You are using Hubspot

Even though we have a native Hubspot integration, it works only to send data to Hubspot, not from Hubspot to Livestorm. So if you want to create new registrations from Hubspot to Livestorm you will have to use Zapier.

To do so, create a Zap, and the trigger will be "New form submission":

When choosing a webinar to create the registration, you will have to set a webinar and a session. Even though session is noted as optional it is in fact mandatory. When the webinar is over, you can change the zap to create the registrant in a different session or a different webinar. Or you can create another zap.

Here is a Zap template to register people for your webinars using Hubspot forms

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.