April 2026 Release **Beta**

Production Release Date: April 29 - planned

The following features, planned for the upcoming April release, are currently available in Sandbox for Beta testing. Our Production release could differ from the information detailed here.

Deprecated Push Subscriptions

Bunchball Go push notifications have been removed from the platform. Users will no longer receive recognition alerts, even if they were previously subscribed.

Bunchball Go was deprecated in June 2025 and replaced with Impact+, which provides a more modern, integrated solution.

Product Updates

Recognitions Block Exchange List and Order

The Recognitions block now supports selecting multiple exchanges to display, instead of only one or all exchanges. You can also define the order that exchanges appear. Users will only see the exchanges from the defined list that they’re eligible for.

To modify the exchanges in an existing block, use the Recognitions block builder to define the list of exchanges and drag and drop them into your preferred order.

Product Fixes

• Fixed an issue in Impact where the color of the arrows on the call to action buttons didn't match the button text color.

• Fixed an issue for Nitro Studio administrators where resetting a password did not also reset the number of login attempts.

Discontinuation Notices

Legacy OAuth Tokens

Effective with the June 2026 release, legacy OAuth tokens used with blocks will be deprecated.

What this means for you?

• Impact and Recognitions blocks will require a JWT gamification token from the /gamification-token API.

• Legacy OAuth tokens will no longer be supported for blocks, and new features released in blocks may not work with the old token.

• If your program uses both blocks and web components, you must use two separate tokens:

  • A JWT gamification token for blocks

  • A legacy OAuth token for web components

To prepare for the upcoming token deprecation, you should take the following steps before June 2026.

1. Review the token used in your Impact block to ensure you’re using a JWT gamification token.

2. Review the token used in your Recognitions block to ensure you’re using a JWT gamification token.

3. Update your embed code to use a correct token if you're not using a JWT gamification token in all of your blocks. Use the steps detailed here to update.

4. Ensure you have two tokens enabled if you have both web components and blocks in the same environment:

   • A JWT gamification token for blocks

   • A legacy token for web components

Legacy OAuth tokens used in web components will continue to be supported until the official end-of-life date for web components is announced.

See also

Release Notes