Release notes
The release notes describe new features, enhancements, and fixes for the ReachFive platform. The latest release notes are found below. For previous releases, check out the sidebar.
For upcoming changes that require your attention, see the Attention page.
Other releases
The following shows other ReachFive releases for your convenience.
SDK repository | Latest version | Docs |
---|---|---|
MavenCentral |
||
SFCC Cartridge |
22 May 2025 (v2.135)
ReachFive v2.135
introduces several improvements and needed bug fixes.
We’re happy to announce that you now have customizable templates for MFA registration journeys.
We’ve also added device metadata variables for MFA templates.
As well, we made it possible to configure the redirect to home link for the Email confirmation hosted page.
Additionally, dark mode is now available on analytics pages.
As always, we made some general improvements and fixed a few items for you.
Customizable templates for MFA registration journeys
You can now customize your MFA enrollment templates for email and SMS to reflect the user’s registration journey.
The dynamic {{action}}
variable, previously introduced for the /identity/v1/mfa/stepup
endpoint, is now available in the /identity/v1/mfa/credentials/emails
and /identity/v1/mfa/credentials/phone-numbers
endpoints.
This variable is set based on the action specified in the request, enabling its use in email and SMS enrollment templates.
This allows you to include conditional logic in the templates to deliver tailored messages to users based on their action or the specific MFA registration path they are following.
How does it work? 🤔
-
You pass
action
in the request body of the/identity/v1/mfa/credentials/emails
or/identity/v1/mfa/credentials/phone-numbers
endpoint.action
is a free string (snake_case
). It must match the action value in the template./mfa/credentials/emails
endpoint example{ "email": "user@example.com", "redirect_url": "https://www.example.com/redirect", "action": "enroll_email", (1) }
1 Here action
isenroll_email
. -
Assuming a successful call,
action
is included in the response token. -
The token is used to trigger the email and/or SMS enrollment template, which contains the
{{action}}
logic, sending the user the appropriate message for their MFA registration journey.Example templateHello {{user.name}}, {% if action == "enroll_email" %} Use this code to enroll your email for MFA: {{verification_code}} {% endif %} {% if action == "enroll_phone" %} Use this code to enroll your phone number for MFA: {{verification_code}} {% endif %}
- Want to know more?
Device metadata variables for MFA templates
It’s always nice to know the exact information from any MFA action. With this release, you can now send your users the relevant device information related to MFA step-up and registration with the following added variables:
-
{{ip}}
-
{{userAgent}}
-
{{operatingSystem}}
-
{{deviceClass}}
-
{{deviceName}}
For more on this topic, see MFA templates.
Email confirmation hosted page redirect option
You can now choose to enable or hide the option for users to return to your site’s home page after confirming their email via hosted pages. Previously, the option to return to the home page was displayed without the option to hide it. Now, you must choose to Display a link to redirect to homepage in the Hosted Pages settings. Otherwise, no link is displayed on the email confirmation page.
To display the redirect to home page link:
-
Go to
in the ReachFive Console. -
Click Display a link to redirect to homepage.
-
Don’t forget to Save your input.
Dark mode available on analytics pages
We have now enabled dark mode for our analytics pages continuing our improvements for an aesthetically pleasing and streamlined user experience in the ReachFive Console.

General improvements
-
We added a timeout when retrieving cluster IPs to ensure optimal performance.
-
You can now retrieve the user’s phone number from B.connect (official site).
-
We improved sorting for exporting segments to ensure filtering options prioritise type for easier use.
Fixes
Item | Fixed |
---|---|
There were a few minor issues with the Roles and Profiles pages in the ReachFive Console. This includes an orphan character and some responsiveness issues. |
✓ |
There was an additional user event ( |
✓ |
There was a minor discrepancy (disappearing custom fields) between the information fetched when calling Get user profile and Get profile custom field schema when custom scopes were removed. |
✓ |
In some limited cases, there were some errors when linking a ReachFive user profile with a social provider. |
✓ |
There were some minor issues where existing custom fields weren’t appearing on some user profiles. |
✓ |
There was a minor issue where the Name fields on some imported user profiles were being incorrectly encoded. |
✓ |