Packaged Clean Room
A clean room component that can be deployed within a customer's own data lakehouse, where identity-matching logic executes locally, raw PII does not leave the domain, and only matching results or aggregate statistics are output.
Timeline (last 90 days)
Databricks partnered with LiveRamp to launch a Packaged Clean Room solution that deploys the identity graph into the customer's data lakehouse in a controlled manner, with raw PII never leaving the domain.
A packaged clean room packages the clean room logic as components deployable inside the customer's data lakehouse, with matching logic executed locally, raw PII not leaving the domain, and no data migration required.
The goal of the packaged clean room solution is to make the process of onboarding RampID standardized and repeatable, lowering the barrier to identity resolution integration, rather than doing custom integration for each customer.
With a packaged clean room, what goes out is match results or aggregate statistics rather than raw identifiers, so the complexity and frequency of data egress approvals are significantly reduced.
When the clean room becomes an operator within the lakehouse, identity resolution can be orchestrated into existing data pipelines, managed with a unified scheduling, lineage and permission system, and iterations of matching logic versions are easier to track.
Local deployment of a packaged clean room reduces data flow risk, but does not eliminate dependence on the identity vendor (LiveRamp); the identity graph remains LiveRamp's asset, and match accuracy, coverage and maintenance quality depend on the vendor.
All Facts (6)
A packaged clean room packages the clean room logic as components deployable inside the customer's data lakehouse, with matching logic executed locally, raw PII not leaving the domain, and no data migration required.
50%UnverifiedThe goal of the packaged clean room solution is to make the process of onboarding RampID standardized and repeatable, lowering the barrier to identity resolution integration, rather than doing custom integration for each customer.
50%UnverifiedWith a packaged clean room, what goes out is match results or aggregate statistics rather than raw identifiers, so the complexity and frequency of data egress approvals are significantly reduced.
50%UnverifiedWhen the clean room becomes an operator within the lakehouse, identity resolution can be orchestrated into existing data pipelines, managed with a unified scheduling, lineage and permission system, and iterations of matching logic versions are easier to track.
50%UnverifiedLocal deployment of a packaged clean room reduces data flow risk, but does not eliminate dependence on the identity vendor (LiveRamp); the identity graph remains LiveRamp's asset, and match accuracy, coverage and maintenance quality depend on the vendor.
50%UnverifiedDatabricks partnered with LiveRamp to launch a Packaged Clean Room solution that deploys the identity graph into the customer's data lakehouse in a controlled manner, with raw PII never leaving the domain.
50%