03 September 2026 (v2.165)
Staging 🧪
ReachFive v2.165 brings a few new features and updates:
As always, we made some general improvements and fixed a few items for you.
Merged profiles now list changed fields
When two profiles are merged, the user_updated_by_merge event on the surviving profile now includes updated_keys, so webhooks and Pub/Sub hooks can see which fields the merge changed.
For example, Ada has no company.
You merge Grace into Ada; Grace’s profile has company: Acme.
Ada’s profile survives, keeps her existing fields, gains company, and the event lists which fields specifically changed:
{
"type": "user_updated_by_merge",
"updated_keys": [
"company" (1)
]
}| 1 | As per the example, Ada now has company: Acme and the event lists company as the field that changed. |
For more details, see updated_keys, Merging rules, and the mergeUsers endpoint.
Control which custom fields Dialog Insight receives
You can now choose which custom fields ReachFive forwards to Dialog Insight.
Previously, every custom field on the profile was sent with the message. If Dialog Insight did not already define that parameter, the send could fail.
In the ReachFive Console at , select Dialog Insight and use Custom Fields to send only the fields your Dialog Insight messages need.
For more details, see Dialog Insight.
General improvements
-
Now, the Data Breach Detection scanning job emits a single
leaked_credentials_usageevent per profile, even when several identifiers on that profile match leaked credentials.
Fixes
| Item | Fixed |
|---|---|
ReachFive Console |
|
There was temporarily an issue with type-ahead search when searching for Job reports in the ReachFive Console. |
✓ |
In some cases, long webhook URLs were being truncated in the ReachFive Console which made it difficult to see or interact with the full URL. |
✓ |
