Table of Contents maxLevel 3
April 2, 2024
Introducing Event deletion APIs
To offer you more control and efficiency in managing your events, we developed a new set of API functionalities that will enable you to archive and delete past events and their associated content.
These new features are designed to streamline your workflow and help maintain the relevancy of your data, by removing past events and tickets data.
| Info |
|---|
In upcoming releases, ADMIN users will be able to archive & delete Events (and their tickets) directly from back-office by clicking a button in the Events list. |
Edit Event > New behaviour and UX for "Transfer Rules"
Alongside the new UI of the Edit Event screen, we generalized the new UX introduced by the "Activation Rules" to the Transfer Rules. An individual display (one row per rule) and a new 'Edit' icon have been added to provide a more intuitive and controlled way of managing transfer rules, ensuring that changes are precise and limited to the intended scope.
...
New mobile logs for "Max active devices reached"
We introduced a new mobile log type (user.max-devices.reached) in order to collect mobile data when max devices is reached for one spectator.
February 21, 2024
Optimization of the feedback interface
...
We have taken this a step further by effectively utilizing this parameter, thereby further optimizing the volume of data returned to the feedback interface, by narrowing down to what is actually used in S-360. Currently, by setting the custom parameter additionalDiffParameters=lightPayload=true, only relevant data to S-360 will be returned to the feedback interface improving performances of both systems.
New flexibility for Mobile Features configuration in the back-office
In the past, enabling or disabling specific functionalities often required a new build of the application. This process was not only time-consuming and labor-intensive but also presented challenges in tracking which app version included specific features.
Most critically, this system did not allow for quick adjustments during live events, such as tournaments, where the ability to swiftly enable or disable features could be crucial.
To address these challenges, we've introduced new settings keys that define these mobile features :
| Location | Key | Description | Default Value |
|---|---|---|---|
| Application Settings | ticket.reminder.non-transferred | Number of minutes before sending an in-app reminder for not yet transferred tickets | 0 (disabled) |
| Application Settings | ticket.reminder.non-assigned | Number of minutes before sending an in-app reminder for not yet assigned tickets | 0 (disabled) |
| Application Features | enable-accept-reject-transfer | Enable the Accept/Reject transfer feature | TRUE |
| Application Features | enable-resale-ticket-shop-s360 | Enable the S360 ticket shop resale feature | FALSE |
Mobile logs
New mobile logs search
...
| Info |
|---|
If you want to preserve mobile logs for a period extending beyond the default 13 months, we strongly advise utilizing the 'Mobile logs' export feature and store the generated file into a Data-Privacy compliant space. |
Campaigns enhancements
Simplified User Interface for Campaign Creation
We're enhancing the user interface to clearly differentiate between CSV-based and manual campaigns. This simplification will streamline the campaign creation process, making it more intuitive and efficient for organizers.
Within "SCHEDULING OPTIONS" section, two tabs will be visible Upload CSV and Use Filters.
| Info |
|---|
Please note that these 2 modes are exclusive and nor meant to be used in combination → it's either you run your campaign using "Upload CSV" OR you "Use Filters", but not both at the same time. |
Upload CSV
Use Filters
Ticket-based filtering for notification Campaigns
Until now, our notification campaign system lacked the functionality to target specific spectator segments, particularly:
- Spectators holding more than X "transferrable" tickets for an event, who might be encouraged to transfer their extra tickets.
- Spectators possessing tickets in a specific status (Downloaded, Pending transfer, Controlled)
These limitations restricted the organizers' ability to run targeted and efficient notification campaigns.
| Status filter new options (EXACT MATCH on the selected status) | Number of "transferable" tickets |
|---|---|
|
|
Campaign's impacted spectators count
Whenever a new campaign is created or an existing one is updated, the system will now calculate the number of impacted spectators at that very moment. This count will be always visible on the Campaigns list in the column Impacted spectators.
We added an information icon in the "Impacted spectators" column. When users hover over this icon, a tooltip will appear displaying the message: “The numbers may vary between the scheduled time and the time of sending.”
Impacted spectators may vary depending on the campaign status :
| Status | Impacted spectator |
|---|---|
| SCHEDULED | Estimates based on the spectator's list at the time of campaign creation or update → displayed in italics |
| SENT | Real number of targeted spectators → displayed in plain text, not in italics |
| CANCELLED | Automatically reset to zero. This ensures accuracy in campaign records and avoids any potential confusion regarding campaign reach. |
January 16, 2024
Progressive roll-out of new Search & Export behaviour
...
In line with these improvements, we have also fine-tuned the "Language" dropdown. This update involves a change in the title to make it clearer and more intuitive for our organizers. The revised title aims to provide a better understanding and facilitate easier navigation in selecting the campaign language.
December 13, 2023
Configure the available gender options from the Registration settings
In today's diverse world, inclusivity and respect for personal identity in data collection are not just ethical imperatives but essential components of effective and responsible practices.
We have now introduce the ability to select two new additional values (Other, Prefer not to say) that can be collected for Spectator's gender.
To do so, go the Registration settings and look for Available gender options (setting key: profile.display.gender.options) and select the additional options that suit your need and click Apply
Crowdin translation keys
- Other: gender_others_label
- Prefer not to say: gender_prefer_not_to_say_label
...