To ensure a more intuitive and efficient approach, we have decided to phase out the standalone JWT integration. This move is rooted in our goal to streamline user recognition management. By gathering all user recognition settings in one place in the platform, we aim to make it easier for our customers to manage their JWT configuration (and other user recognition types). To mention some advantages,

If you have previously used JWT on your campaigns, the update will require that you transition your current JWT setup into our new, improved user recognition setup.

Timeline for the phase-out of the integrations

In this article, we will guide you on how to successfully transition your JWT integration setup to the new user recognition setup.

In essence, the fundamental functionality of JWT within our platform remains unchanged. The key shift lies in the configuration process, which we will explain in further detail in the next sections.

Our new approach brings all user recognition options, including JWT, under one roof within the platform's user recognition section. This simplifies the configuration process and offers a space where recognition settings can be managed more efficiently.

Besides efficiency, the user recognition setup also introduces some new features that allow for improved flexibility and a broader range of options in the JWT configuration.

In the following section, we will describe in more detail, what this means in practice.

We have maintained seamless compatibility of the old and new JWT setup, making it easy to transition an existing JWT setup into the new user recognition setup.

In the video below, we will show you how to transfer your JWT integration setup to the user recognition tab. The steps will be explained in detail in the following sections.

The first step in the transition is to enable user recognition on your campaign. You will find the user recognition section in the 'Advanced' tab.

Next, you need to select the user recognition type and algorithm.

The standalone JWT integration only supported JWS. This means, that if you are transferring the setup you have previously used in the platform, you should choose the JWS option in the user recognition tab.

The algorithm should also match the previously used signing algorithm.

Depending on what algorithm you are using, you will have to insert a key or secret. The secret/public key can be transferred directly from the JWT integration to the user recognition tab.

The sample can be partly reused from your existing JWT setup, however, there are small changes to pay attention to.

In the new user recognition setup, you must include a full URL with parameters including tokens to validate the key or secret provided.

The sample URL used in user recognition consists of three elements: a question mark, a parameter (often token or query), an equal sign, and the sample.

The query parameter name can be found in the JWT integration. Below you can see an example of how to add the ?parameter= to the sample.

It is also possible to fetch the sample including the parameter via the 'created from URL' value on a registration. In the below example, the parameter is 'user'. You can fetch the sample by copying everything that comes after the ? sign.

One of the biggest differences in the new setup is, that the matching of the form field with the JWT fields is done directly in the user recognition tab, instead of on the individual field in the registration form.

If you are in doubt about how the fields should be mapped up, you can always check how the JWT values were previously matched with the form field by going to the individual field in the registration form. See example below:

In the new user recognition setup, you have some additional validation options available.

The JWT integration only checks, if the JWT has expired. Per default, this is the only option that is enabled in the new user recognition setup. Unless you want to add additional validation, you can leave the settings like this.

Another new feature that has been made available is the option to define messages that are displayed to the player, if a token is missing, has expired or if the token was for some reason not accepted.

You can decide whether you want to: