Click Follow in the Release Notes section to be notified when new releases are available.
- Announcement Date: September 03, 2026
- Release Date: September 17, 2026
As Verato continues the transition toward the unified MDM Cloud experience, both interfaces—the current platform and the new MDM Cloud — will coexist for a period of time. Features and updates may be delivered to each interface independently, depending on where they provide the most value for customers during this transition.
Verato MDM Cloud
Identity
New Features and Improvements
Quarantine Workflow Enhancements
Quarantined Records Visible in Demographics Queries
Organizations using Applied Overlay Quarantine can now see quarantined source and attribute data directly in demographicsQuery responses. Previously, quarantined data was tracked internally but not exposed through this API, so integrators reviewing an entity's records could not distinguish a quarantined match from an active one. Active-match search and ranking continue to reflect only non-quarantined data, so existing match behavior is unchanged.
New Notifications for Quarantine Status Changes
Organizations using Applied Overlay Quarantine now receive a notification the moment a record moves into quarantine, and again when it's released, using Verato's existing notification delivery model.
Audit Trail for Quarantine and Un-quarantine Actions
Organizations with audit logs enabled can now see when a record was quarantined as part of an overlay, and get a full audit record when a record is released from quarantine. Previously, un-quarantine actions were not tracked anywhere, leaving a gap in the audit trail.
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.
Reporting and Match Score Precision
More Precise Match Score Reporting
Organizations comparing match score data across Looker and Operational Reports will see consistent results going forward. Match scores are now stored with three decimal places of precision instead of two, eliminating the rounding mismatches that previously caused the same records to group differently between the two tools.
Potential Match Tasks
Improved Reliability for Potential Match Tasks
Some customers using Potential Match experienced tasks closing automatically when related records were deleted. This has been resolved, and Potential Match tasks will now stay open until a steward manually closes a task, or a valid change to the record occurs where the task should automatically close.
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.
Sample schema for Preferences
"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
Improved Reliability for Prevented Match Same-Source Tasks
Some customers using Prevented Match Same Source experienced tasks closing automatically with no underlying change to the record. This has been resolved, and Prevented Match Same Source tasks will now stay open until a steward manually closes a task, or a valid change to the record occurs where the task should automatically close.
Resolved Intermittent Authentication Errors
Organizations calling UMPI through the MDM Cloud UI experienced intermittent 401 errors in production. 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.
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.
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.