v1.12.7

Released 8 October 2026: Omi the Studio assistant, image specs and generator, the Custom Email Provider add-on, optional event badges, new publish checks.

Released 8 October 2026.

Check before your next publication

Receipt Host App links: only the link in the Receipt Host App tab opens the app. A link that ends in the campaign's ID, from an older email or instruction sheet, shows the sign-in screen but refuses the password. Send staff the current link or a new sheet.
Activity messages: an Activity can't publish with an empty Check-in Confirmation Message or Message If Event Ended, or an empty Booking Confirmation Message when it takes bookings. These were optional before, so check running events.
Shared leaderboard rewards: a leaderboard reward linked to several skill games needs at least one unit per game, or publishing is blocked.

Platform

Omi, the Studio assistant. Ask Omi, at the bottom of every Studio page, answers your questions from this Help Center and lists the pages it used. In a campaign, it reads the campaign's saved settings and the step you're on. See Get help in Studio.

Solve with AI explains validation errors. On the Action Required banner, and on each issue in the validation window, Solve with AI asks Omi to explain the error and give the steps to fix it. See Validation & publishing.

Help pages open from Studio. Guide, at the top of a screen, opens the help page for it in your organisation's language. A ? or Learn more beside a tricky setting opens the page that explains it. See Open the help page for a screen.

Image specs and an image generator. Image fields have See specs, which shows the size and format the image needs. Most also have Generate: choose a design, then Use this image fills the field and adds the image to Images & Files. In the validation window, a missing image offers Generate the image or See specs. See Image & asset specs.

Badges are optional on Activities. Only treasure hunt objects still need a badge to publish. A game's result screen opens with the game's own message. Before, it could say "Badge Unlocked!" even after a loss. Its badge, if it has one, sits at the bottom, below Go to summary, whether the player won or lost. After an Activity check-in, the badge sits below the Check-in Confirmation Message. See Gamification badges.

Theme copies are named after their campaign. A campaign created from a template gets its own copy of the template's theme, named after the theme and the campaign, such as "Winter - Winter Wonderland 2027". Campaigns made from one template can then be told apart in the theme list. See Templates: export, import, and reuse.

Photos in form answers open full size. In Participants, under Participation Form Answers, a photo opened only as a small thumbnail. It now opens with zoom, rotation and Download. A file that can't be previewed, such as a PDF, has a Download button. See About participation forms.

More of Studio is in French. Screens that still showed English in a French Studio, such as Webhooks, Functions and the 3D model wizard, are translated. A few French labels changed on the way: Gated Content, for example, reads Contenu à accès restreint instead of Contenu Garanti.

Games

Players at their limit can't start again by signing in. A player who had reached the play limit could sign in again, for example from another phone with the same email, and start the game. The game now refuses them. See Test your game.

Simple Game lotteries confirm only real entries. After signing in, a player could see the lottery participation message even though no entry was recorded. See Simple Game (instant win).

Publishing a running game keeps its attribution slots. Publishing the campaign again while a game runs leaves each attribution slot's quantity as you set it. Stock left over in one slot still carries into the next. See Configure outcomes.

A leaderboard reward shared by several games needs a unit per game. Publishing stops when a leaderboard reward linked to several skill games has fewer units than games, which would leave some games with nothing to award. Raise its quantity, or give each game its own reward. See Game validation errors.

Events

An Activity's messages must be filled in. Publishing needs the Check-in Confirmation Message and the Message If Event Ended, and the Booking Confirmation Message when the Activity takes bookings, so attendees always see a message. One language is enough. See Configure check-in and Event validation errors.

Booking dates show in your time zone. The Start Date filter in Participants > Bookings listed times in UTC. It now uses your organisation's time zone, like the table. See Access bookings & tickets.

Transactions

Receipt Host App: a new link, sign-in sessions and an end date. Only the link in the Receipt Host App tab opens the app. A device stays signed in for about 10 hours, and changing the password signs every device out. The app closes 7 days after the campaign's last prize slot ends, or 7 days after the game's end date if prizes have no slots: note your final Progression totals before then. See Give your staff access.

Treasure Hunts

Hunt objects ask for the hunt's terms. With terms at Touchpoint Level, an object page let participants through without the hunt's own terms. Each object page now asks for them, and accepting once covers the whole hunt. Publishing no longer warns that terms are off for each hunt object or offer. See Set opt-in for a hunt.

Integrations

Custom Email Provider: notifications through your own platform. This new email add-on, an alternative to Cheetah and Salesforce Marketing Cloud, hands each campaign email to a Function that sends it through your own email service. See Connect your email platform.

Developers

Function executions are kept 60 days. Records in a Function's Executions tab used to expire after 24 hours. Load more no longer repeats the first page, and the count reads 20+ while more remain. See Test and monitor functions.

Failed outbound calls say why. A TIMEOUT or UNAVAILABLE error names the call, the host and the reason, such as dns lookup failed or connection refused. See Function SDK reference.

Booking and ticket events with an empty group_context run Functions. They used to trigger nothing. Now they run every subscription that has no Group filter. See Platform event functions.

notification.sent.v1 carries the finished email. With Custom Email Provider, the event adds provider, rendered and sender. See Event reference.

Admin & Access

New users' email addresses are checked. A user created with a space around their address couldn't sign in. Spaces are now removed when the user is created, and a malformed address is refused with "email must be a valid email address". See Assign users to organisations.

Custom HTML in the email header and footer only with Custom. In Organization Settings > Notifications, Custom Content shows only when Section Type is Custom, as a code editor. Saving no longer asks for custom content with Default System or None. See Organisation settings and About notifications.