May 2026 LiveRamp Clean Room Release Notes
This release introduces stronger governance controls for analysis rules and template-based workflows, new protections in question authoring, expanded export behavior for Clean Compute, and several quality-of-life improvements.
Product Updates – General Availability
Organization Default Analysis Rules
Clean Room now supports default Analysis Rules at the organization level for data connections.
Organization-level defaults: Data owners can define baseline Analysis Rule settings on a data connection.
Automatic inheritance for datasets: When that data connection is provisioned as a dataset, the dataset inherits those Analysis Rule settings automatically.
Clear separation of rule scopes: Data connection Analysis Rules and dataset Analysis Rules remain independently managed after provisioning.
This helps organizations establish consistent governance standards earlier in the data onboarding workflow and reduces the need to repeat the same settings across datasets.
Product Updates – Limited Release
Enforced and Possible Parameters
Clean Room now provides additional controls for runtime parameters and template-based governance.
Controlled parameter values: Clean room owners can define the allowed values for runtime parameters used by questions, including parameter macros shared across multiple questions.
Default and fixed values: Owners can set default values or hard-code values for a specific collaboration when needed.
Template-based dataset filters: Dataset filters can be applied automatically when a clean room is created from a template, rather than requiring manual setup after cloning.
Intelligence filter controls: Owners can also define possible Habu Intelligence filter values, along with defaults or fixed values for a given Intelligence instance.
This makes templated workflows easier to operationalize while helping enforce governance controls more consistently.
Flow Provisioning Approvals for Partner-Owned Questions
Clean Room now adds an approval step when a flow is provisioned into another clean room and includes questions owned by a partner organization.
Approval workflow for flow provisioning: Organizations that own questions included in the flow can be asked to approve provisioning before the flow is moved.
Better protection for partner-owned assets: This helps prevent a partner’s logic from being provisioned into another clean room without their knowledge.
Improved visibility into requests: Provisioning requests are surfaced in the clean room request workflow.
This strengthens collaboration controls for multi-party flow management.
Export All Clean Compute Output Files
When users configure an export for a Clean Compute question, Clean Room now includes all output files generated by the run.
More complete exports: Exports can include supporting output files in addition to the report.
Better support for technical workflows: This is especially helpful for workflows that rely on artifacts such as pickle files or summary outputs.
Easier downstream processing: Teams can move a fuller set of results into external systems without separate retrieval steps.
This improves how Clean Compute results can be operationalized outside the platform.
Quick Hits and Fixes
Question run row counts: The run list and reports page now show output row counts for question runs. These values are automatically populated for newer runs, and older runs can be populated when the related report is opened.
API usage limits: Clean Room now enforces an organization-level limit of 5,000 API requests per day to help protect platform performance.
Permissions update for versioning actions: The ability to view version history and switch versions for clean room questions is now tied to the Question Builder permission.