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

SDK repository	Latest version	Docs
Core SDK		Core SDK
UI SDK		UI SDK
Android SDK	MavenCentral `11.0.0`	Android SDK
iOS SDK		iOS SDK
SFCC Cartridge	SFCC Cartridge `20.9.1`	Salesforce cartridge

identity core

identity ui

MavenCentral 11.0.0

Reach5

SFCC Cartridge 20.9.1

Salesforce cartridge

23 July 2026 (v2.162)

Production ✅

ReachFive v2.162 brings a few new features and updates:

Custom social providers
Accurate updated_keys on import events

As always, we made some general improvements and fixed a few items for you.

Release highlight

Custom social providers

You can now create custom social providers directly in the ReachFive Console.

When ReachFive does not already ship a connector for your identity provider, you configure the provider yourself and use it like any other social login.

What you can configure

Provider identity: Display name, provider key, logo, color, and visibility for hosted pages and widgets
OAuth 2.0 connection: Authorization, token, and user info HTTPS endpoints, client credentials, scopes, and optional PKCE
Attribute mappings: Standard OpenID Connect claims by default, with optional custom overrides to profile fields

After you save the provider, pass its provider key to the Core SDK, UI SDK, or /oauth/authorize the same way you use built-in providers such as facebook or google.

For full setup steps and examples, see Custom social providers.

Accurate `updated_keys` on import events

Previously, import jobs could emit user_updated and managed_user_created user events with an empty updated_keys array even when the profile was updated. Now, updated_keys lists only the fields that were actually changed, so you can reliably react to import updates in webhooks, Pub/Sub hooks, and other integrations.

For example, when an import adds a birthdate to an existing profile, the event can look like this:

{
  "type": "user_updated",
  "canal": "job",
  "job_type": "import",
  "updated_keys": [
    "birthdate",
    "birth_day",
    "birth_month",
    "birth_year",
    "age"
  ]
}

For more details, see updated_keys.

General improvements

In the ReachFive Console, the user profile now displays a partial birth date from birth_day and birth_month when the birth year is unavailable on the profile (for example due to provider limitations or data-processing requirements).

Age is not calculated when the year is missing.
You can now see the session type under the Session devices tab in the ReachFive Console for a user.

Fixes

Item Fixed

Item	Fixed
In some cases, the `updated_at` field was not updated when profile fields changed, such as after suspending a user.	✓
Temporarily, a `risky_login_notification` event was being generated even when the RBA template was not configured, meaning no notification was sent to the user.	✓
In some limited instances, the user’s IP address was not updated when the user’s location changed.	✓

In some cases, the updated_at field was not updated when profile fields changed, such as after suspending a user.

✓

Temporarily, a risky_login_notification event was being generated even when the RBA template was not configured, meaning no notification was sent to the user.

✓

In some limited instances, the user’s IP address was not updated when the user’s location changed.

✓