You can show or hide registration form fields with visibility conditions. This lets you define who should see the different fields, customizing the player experience.

You can currently limit visibility based on:

Visibility condition based on date and time, as well as GET parameters, is "static" as it does not depend on players' actions throughout the game.

Instead, visibility conditions based on metric data and form fields can adjust dynamically. What each player sees depends on what he/she does each time the game is played or the registration form is filled.

Adding a date or time range to your form field will hide the field before and after the given range.

This allows you to show different fields based on when a player visits your campaign. This could be a way to test the conversion rate with different fields included or to keep a campaign fresh if it is running for a longer period of time.

Read more about date and time visibility and how else it can be used on your campaign here.

With metric data visibility conditions you can show players different fields based on how they behave in the game. This only works if your registration page comes after the game.

Maybe you would do this if only game winners were eligible to win a prize. You can ask winners for their postal code, and then if they win a prize, it will be local to them.

In the example below, players are asked for their gender only if they answer the quiz question correctly ("yes").
​
​You can expand the video to full-screen in the bottom-right corner.

Form fields visibility condition lets you show players different fields based on what they select elsewhere in the form.

For example, if you have a drop-down menu with several options, including an "other" option. For people who select "other", you can then show an input field asking them to elaborate.

In the example below, players are asked for their ring size if they indicate in the form that they are women. Then, if they cannot find their size in the drop-down menu, they are prompted to enter their size.

​You can expand the video to full-screen in the bottom-right corner.

GET parameters visibility condition lets you show players different fields based on parameters in the URL.

In the example below, the registration form has a checkbox for newsletter sign-up. You can use GET parameter visibility condition to show this checkbox only to players who have not already subscribed to the newsletter.

This is only possible if the campaign URL includes a UTM parameter tracking whether or not people have signed up to the newsletter. The live ULRs can be, for example:

You can expand the video to full-screen in the bottom-right corner.