24 April 2025 (v2.134)

ReachFive v2.134 introduces a couple of improvements and needed bug fixes. We have improved the error messaging when passing the check_updated_at field with the Management API. We also ensure now that Identity Fraud Protection (IFP) is activated for signups for all accounts with this feature.

As always, we fixed a few items for you.


Improved check_updated_at error messaging

The check_updated_at field helps you validate user data freshness.

We have improved the error messaging for when the request payload’s updated_at value is older (or the same age as) than the database’s updated_at value by making the error code more specific as shown below.

This helps differentiate from other causes for an error such as a formatting issue.

{
  "error_id": "XOpYpK04Zl",
  "error_description": "Validation failed",
  "error": "invalid_request",
  "error_details": [
    {
      "field": "updated_at",
      "message": "Can't update the profile since the provided `updated_at` value is anterior to the current record",
      "code": "check_updated_at_failed" (1)
    }
  ]
}
1 The error "code" is now check_updated_at_failed.


IFP activation on signup

ReachFive’s Identity Fraud Protection (IFP) module analyzes events to determine if a particular IP is exhibiting suspicious behaviour. In particular, the Identity Fraud Protection module consumes login and signup attempts where it determines if the IP is suspicious or not. If the Identity Fraud Protection module determines that the IP is suspicious, the IP is flagged and siloed into a separate database where its access is immediately blocked.

For those who integrate IFP with the backend, you should ensure the True Client IP Key is enabled.


Fixes

Item Fixed

Users who created a Lite profile with a phone number were unable to sign up with a social account if that same phone number existed on the social account.

✓

The ReachFive Console was temporarily not detecting system preferences for light or dark mode.

✓

There were some minor inconsistencies with the error.socialAccountEmailAlreadyInUse error message.

✓

There were data structure issues when exporting Segments from the ReachFive Console.

✓