Skip to main content

Participant tracking

You will likely want to closely monitor website traffic, page views, the success of your marketing campaigns, or your partners' influence on registrations to your event.

Updated over a week ago

There are several methods to track your participants.

Website tracking and statistics

This is the main tracking feature in Eventmaker, allowing you to connect your audience analytics tools, such as Google Analytics and Google Ads. You can also insert tags and pixels using custom scripts.

Website tab > Customize this website > Edit appearance and settings > Tracking and Statistics

Snippet on your website pages

You can insert a snippet section on your website pages to add custom scripts. Once created, a snippet is saved and can be reused on any page.

Website tab > Customize this website > Your page > New section > Snippet

Duplicate categories

Finally, you can simply duplicate your categories to generate other registration links so that registrations flow separately.

Participant UTM tags

Why use UTM?

As a marketer, you continuously track your performance: email campaigns, social networks, partnerships, SEO, banners, etc.

UTM tags (Urchin Tracking Module) allow you to precisely identify the origin of a participant at the time of registration.

They are automatically captured during the registration processes and associated with the participant's record to facilitate tracking and analysis of acquisition channels.


How do UTM tags work on Eventmaker?

Automatic population

When a visitor arrives at a registration form with UTM parameters in the URL, this information is automatically recorded.

The standard tags are:

  • utm_source

  • utm_medium

  • utm_campaign

They are then visible in the participant's record, under Origin.


Manual pre-filling: create an URL per acquisition channel

To analyze your marketing actions, it is recommended to create a dedicated URL per acquisition channel.

Naming convention to follow

your-form-url?utm_source=value1&utm_medium=value2&utm_campaign=value3

Separators used :

  • ? → starts the parameters

  • & → adds an additional parameter

  • = → assigns a value


Examples

https://sustain.eventmaker.io/registration/5ce687d9e5078e001f405834?utm_source=banniere1&utm_campaign=01_04_2018&utm_medium=site_web

⚠️ UTM cookie behavior (essential point)

When a visitor arrives on your site with UTM tags:

  • The UTMs are stored in a browser cookie

  • This cookie is persistent

  • The information can be automatically re-injected during a later registration

This means that:

If you test several UTM links without clearing your cookies, the old values may be retained.


Common testing example

  1. You register a participant via a link with utm_source=parrainage

  2. You then test another link without UTM

  3. Without clearing cookies → the old UTM values will be reused

This behavior is intentional and ensures consistent tracking in a real user journey.

We clarified the behavior to avoid any confusion.

However, there are exceptions which we illustrate below:


Case 1

The participant begins registration via the website (default UTM)
They complete it via a campaign without a custom UTM

➡ They keep the "website" UTM


Case 2

The participant starts via the website (default UTM)
They complete it via a campaign with a custom UTM

➡ They keep the custom UTM


Case 3

The participant starts their registration with a custom UTM

Even if they complete via:

  • another campaign with a different custom UTM

  • a campaign with the default UTM

➡ They keep the first detected custom UTM


In summary

First UTM = default

(Registration via website button)

Can be replaced by a custom UTM

First UTM = custom

(Registration via LinkedIn link with UTM)

First UTM retained because it starts the conversion


Recommended best practices

  • Create dedicated URLs per channel

  • Test in private browsing

  • Clear cookies between tests

  • Standardize your UTM naming

  • Avoid running multiple competing campaigns on the same segment

Did this answer your question?