February 2026 LiveRamp Clean Room Release Notes
This release introduces improvements to data connection setup, privacy controls for Clean Compute, flow management in the external API, and Intelligence dashboard delivery, along with a limited-release update for Azure data connections.
Product Updates – General Availability
Hive-Style Partition Detection for GCS Data Connections
Clean Room now automatically detects Hive-style partition fields for Google Cloud Storage (GCS) data connections when data is organized in paths such as fieldName=value.
Automatic partition discovery: Clean Room can discover partition fields directly from file path segments.
Type inference for partition fields: Date macro-based partition fields are inferred as DATE, while other partition fields are inferred as STRING.
Automatic partition column assignment: Detected fields are automatically marked as partition columns on the connection.
Avoids duplicate partition definitions: If a partition is already part of the configured static base path, it is not re-added as a dynamic partition column.
This reduces manual configuration, improves schema accuracy, and makes GCS-based connections more resilient as new partitions are added over time.
For more information, see the following articles:
K-min Support for Clean Compute Questions
Clean Compute question authors can now reference dataset- or clean room-specific crowd-size and aggregation thresholds through environment variables in their code.
Configurable privacy thresholds: Authors can reference variables such as crowd-size or aggregation thresholds directly in Clean Compute code and templates.
Runtime resolution: During execution, these variables are automatically resolved to the values configured on the relevant clean room or dataset.
Auditability: The resolved values are recorded in logs so teams can confirm which thresholds were applied during execution.
Better support for reusable workflows: This reduces the need to hardcode thresholds into question logic and helps teams build more reusable, policy-aware workflows.
This brings Clean Compute closer to the privacy-control model already available for SQL-based questions.
New External API Endpoints for Flow Management
Two new endpoints have been added to the Clean Room External API to improve flow management.
Get a Clean Room flow by ID: Retrieve a flow by ID, including its structure and version information.
Set Clean Room flow version: Update a flow to use a specific existing version, enabling rollback or version switching.
These additions improve operational efficiency and expand the robustness of the external API for workflow management.
Email Subscriptions for Intelligence Dashboards
Intelligence dashboards now support scheduled email delivery of dashboard content.
Scheduled dashboard delivery: Users can configure recurring email subscriptions for dashboard content.
Flexible delivery options: Subscriptions support configuration options such as filters, frequency, and embedded visualizations.
Broader reporting access: Dashboard emails can be used to share results with stakeholders who may not work directly inside the clean room environment.
A few important considerations apply:
Recipients should be chosen carefully: Dashboard deliveries reflect the dashboard as configured by the sender, so users should be deliberate about distribution.
Subscriptions are user-managed: Users can manage only the subscriptions they create.
Shared inboxes may be helpful: Teams may want to route deliveries to shared mailboxes or service accounts for better continuity and control.
Product Updates – Limited Release
Delegation SAS Support for Azure Data Connections
Clean Room now supports Delegation SAS tokens as a credential type for Azure data connections in limited release, including support for CSV Catalog sources.
New Azure credential option: Customers can connect Azure storage using Delegation SAS instead of relying on older access patterns.
Supports Hybrid environments: This applies to Azure data used with Hybrid and Hybrid Confidential Computing clean rooms.
Improved security alignment: The update supports secure execution requirements for trusted execution environments while maintaining expected logging and operational controls.
This establishes a modern Azure access pattern for customers with stricter security requirements.