Click Follow in the Release Notes section to be notified when new releases are available.

• Announcement Date: September 3, 2026
• Release Date: September 24, 2026

Verato MDM Cloud

Identity

New Features and Improvements

Quarantined Records Visible in Demographics Queries
Organizations using Applied Overlay Quarantine can now see quarantined source and attribute data in demographicsQuery responses. This completes quarantine visibility across the Link query APIs: identityIdQuery, nativeIdQuery, and sourceRecordsQuery already returned quarantined data before this release. Quarantined data is returned in a dedicated quarantinedData section, separate from active identity data. 

Search and matching for demographicsQuery continue to run only against active, non-quarantined records and demographics, so existing match behavior is unchanged.

New Notifications for Quarantine Status Changes
Organizations using Applied Overlay Quarantine now receive a notification when a record moves into quarantine (quarantineApplied) and another when it is released (quarantineReleased). Both are delivered through Verato's existing searchNotifications model. Each notification identifies the affected record by source, native ID, and Link ID. The notification body contains no demographic data.

Audit Trail for Quarantine and Un-quarantine Actions
Organizations with audit logs enabled can now see the full quarantine lifecycle in the Audit Log in Verato MDM Cloud™. Releases from quarantine are now recorded too, including the source record, the Link ID, and the user who released it.

New Permission for Resolving Quarantined Records
Data stewards and system administrators can now resolve quarantines directly on stewardship tasks. This permission is included by default in both roles, so no setup is required to start using it.

Applied Overlay Task Enhancements

Table View for Applied Overlay tasks
Stewards resolving Applied Overlay tasks can now switch to a flat table layout that lists every record linked to an identity side-by-side, one row per record. This makes it faster to spot record-level differences across a full set of linked records before resolving a task — particularly useful in high-volume or complex identity scenarios. The record the overlay was originally applied to always appears as the first row for quick reference.

Applied Overlay Comparison View

Stewards resolving Applied Overlay tasks can now see exactly what changed on a record without cross-referencing it manually. Opening a task now shows Previous Value and Applied Value side by side, with the changed attributes (for example, an updated SSN or date of birth) called out directly in the task view. A "Show unchanged attributes" option and a "Show Related Records" panel remain available to pull in full record context and every linked value across source records when needed. This is enabled by default for all customers, with no configuration required.

Smart Steward Recommendations

Clearer AI recommendations in the stewardship workflow
When a Smart Steward recommendation is available for a potential match task, it now appears inline with the specific action it supports — Accept, Accept & Link, or Accept & Merge — so stewards can see what the AI is suggesting and act on it in one step.

Household Membership Notifications

Improved Reliability for Household Membership Notifications 
Organizations relying on household-change notifications to keep downstream systems in sync could occasionally miss an update — when two internal processes updated the same household record within milliseconds of each other, the resulting notification was sometimes dropped rather than delivered. This was a high-priority issue affecting customers using household-level event notifications. The underlying timing conflict has been resolved so that household membership changes now reliably generate their notification, even when updates occur in rapid succession. For further details on household notifications, please refer to the Service / Body values table.

Person Data Model: Preferences

Expanded Preferences Data Model
Organizations managing communication preferences can now capture source attribution, validity windows, and lifecycle status on each preference record, giving visibility into conflicting preferences reported by different systems. At the channel level, organizations can also track opt-out dates for audit trails, per-channel language preference, and a specific contact endpoint. All new fields are optional, so existing preference records are unaffected.

"preferences": [
 {
   "name": "TEXT",
   "type": "TEXT",
   "status": "TEXT",          
   "source": "TEXT",          
   "validFrom": "DATE",       
   "validTo": "DATE",         
   "channels": [
     {
       "type": "CODE_SET",
       "isOptedIn": "BOOLEAN",
       "lastOptedInDate": "DATE",
       "lastOptedOutDate": "DATE",  
       "frequency": "TEXT",
       "preferredStartTime": "TIME",
       "preferredEndTime": "TIME",
       "contactValue": "TEXT",      
       "language": "CODE_SET"       
     }
   ]
 }
]

Bug Fixes

Prevented Match Same Source Tasks No Longer Close When Record Is Re-posted
Data stewards at organizations using Prevented Match Same Source could see open tasks close automatically, marked as "Automatic Update," when a source system resent a record with no changes. This could remove same-source duplicates from the review queue before a steward had resolved them. This has been resolved: these tasks now stay open until a steward closes them, or until a real change to the records makes the task no longer valid. No action is required.

SSNs and Dates of Birth No Longer Missing from Default Query Responses
When the same source record was posted more than once with different SSN or date-of-birth values, Verato stored every value, but query responses in the DEFAULT format returned only one SSN and one date of birth. DEFAULT responses now return every distinct SSN and date of birth stored on the record.

Resolved Intermittent Authentication Errors 
Users working in Verato MDM Cloud™ could intermittently see 401 (unauthorized) errors while opening stewardship tasks or updating records, even though they were signed in with valid access. The errors appeared as "Error While Retrieving UMPI Stack" or as a failed request when a task loaded. This has been resolved.

Insights

New Features and Improvements

Snowflake Share View Enhancements

Household Demographics Now Available via Snowflake Share
Organizations with household demographics enabled can now query household-level views, including household composition, summary counts, and demographics, directly through their Snowflake Share connection, without reaching into Verato's primary database. The new Share views include: VERATO_HOUSEHOLDING, VERATO_HOUSEHOLDING_SUMMARY, and VERATO_HOUSEHOLDING_DEMOGRAPHICS.

New Snowflake Share View for Health Facility Task Records
Organizations reviewing tasks in their Snowflake environment can now use a new VERATO_TASKS_HEALTH_FACILITIES_RELATED view to see every record associated with a task's link ID, matching the pattern already available for VERATO_TASKS_RELATED and VERATO_TASKS_PRACTITIONERS_RELATED. This is especially useful for tasks comparing more than two link IDs, where the base task views only capture the trigger and link record.

MDM Cloud Insights Reports Enhancements

Consistent Match Score Rounding in the Task Analysis Report
Organizations using the Task Analysis Report will now see match scores rounded to three decimal places consistently across the Match Score filter and the task-count-by-match-score chart, in line with the same precision update made to the underlying match score data.

Improved User Group Names in the Task by Steward Chart in Task Analysis
When tasks were assigned to a user group rather than an individual, the Task by Steward chart in the Task Analysis report could display a system-generated user group ID (e.g., UG||12345) instead of a readable group name. This has been resolved — the report now correctly identifies user group assignments and displays the corresponding user group name.

Preferences and Consents Fields Now Available in Reporting Views
Organizations using Operational Reports or Snowflake Share can now see the newly expanded Preferences and Consents fields reflected in the Person Dimension and Full Demographics views, completing the reporting-layer rollout of the expanded preferences model.

Bug Fixes

Corrected Response Time Charts in User and Usage Analysis
Users could see inflated Average and p95 API Response Time values in the User and Usage Analysis charts due to a calculation error. This has been resolved — the underlying query logic now correctly weights response times, bringing reported values in line with actual performance.

Corrected Licensed User Counts in User Analysis
The Total Licensed Users widget in User Analysis was showing incorrect counts due to an issue in the underlying user-to-customer mapping logic. This has been fixed, and the widget now accurately reports licensed user counts.