Track Conversions on Your Registration Pages

Looking to track your registrations in Google Analytics for example? Do you need to send an event to third-party software when someone fills out the registration form? This article will help you.

If you would like to track registrations using the Facebook Pixel in Events Manager, please refer to our dedicated article.


Insert Custom Code

Our Custom code integration is accessible to our customers with a yearly Pro plan or a monthly Pro plans (with a minimum subscription of 3 months), Business, and Enterprise plans.

Go to your Settings menu and then Account settings.

Click on App marketplace and select the Custom code card.

Paste your code.

Choose if you want your code to be applied on your Registration pages and/or the Company page.

Choose if you want to enable the integration on the new events you will create.

Click on Enable integration and check on the Integration menu that the status is green and "Enabled".

The Custom code integration you've just set up will not be enabled by default on events previously created. You need to enable it manually on each event.

How it works

To trigger something after a registration you need to know when it is successful. This is why we provide the following method:

livestorm.on('registration-success', function () {   

We also provide specific methods for any kind of pixels:

  • livestorm .addPixel to add a link to an image-based pixel
  • livestorm .addTag to add a tag-based pixel like a javascript file or an iframe.

To display a tracking pixel after registration

livestorm.on('registration-success', function () {   

To execute a tracking script after registration

livestorm.on('registration-success', function () {
  livestorm.addTag('script', 'src', 'https://TRACKINGSCRIPT.js')   

To execute a tracking iframe after registration

livestorm.on('registration-success', function () { 
  livestorm.addTag('iframe', 'src', 'THE LINK HERE') 


Here's an example of a common advertising network.

Example using Google Tag Manager

<!-- Google Tag Manager -->
<!-- End Google Tag Manager -->
livestorm.on('registration-success', function () {
  fbq('track', 'CompleteRegistration')

Others examples

There are other advertising platforms that rely on conversion pixels that you can plug into Livestorm. Among which:

  • Adroll
  • Quora (use the tracking method after loading the main tag)

Send Events via Zapier

Another easy way to track registrations is to send events via Zapier once someone has registered. Then you can send events to Adroll or even Google Analytics.

For Google Analytics, you don't need to use this method to track registrations as we have a native Google Analytics integration. You may check out our dedicated page to learn more about this ➡️ Connect Google Analytics & Livestorm

In any case, here's the Zapier example to track registrations. The first step will be the trigger called " New registrant" and then the action called "Create a Measurement".

You'll need to fill in the necessary fields for the trigger "New registrant" and the action "Create a Measurement in Google Analytics".

Using Google Tag Manager

Instead of using the custom code you can just load Google Tag Manager and handle the code on GTM's end. You can define triggers that will help you create the action within Google Tag Manager. See here for the guide on Setting up and Installing Tag Manager.

1. First, you need to launch GTM. 

2. Then, you need to add the scripts that you want to launch from GTM. So in the tag configuration, you can add all of your pixels and scripts that need to be loaded.

Note: You can create different tags if needed. This is useful for example if you want to load ad tracking scripts on event registration, and an entirely different set of scripts on PageLoad for example.

3. You need to define the triggers that will launch these tags, but you can also set up a trigger for event registration confirmed.

Another script should be used when someone completes their registration.

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