Data Sharing & Clean Rooms
Collaborating on data neither party may hand over, with computation as the interface.
4 to work through
-
advanced Multiple choice
A retailer wants to measure whether a brand's advertising drove in-store purchases. The brand has exposure data with hashed identifiers and the retailer has transactions. Neither may see the other's raw records. Which arrangement should they use?
2 min answer -
advanced
A retailer with 40 million loyalty members and a brand with 12 million exposed device identifiers want to measure in-store purchase lift inside a clean room. Hashed-email match comes back at about 23%. The four-week category purchase rate is around 2%. Roughly what relative lift can this measurement detect, and what does the number rule out?
3 min answer -
advanced
Two companies want to analyse their combined data without either seeing the other's records. What makes that architecturally possible?
2 min answer -
advanced Multiple choice
Two companies want to measure advertising overlap without either seeing the other's user data. What architecture supports this?
1 min answer
5 terms in this topic
Aggregation Threshold Policy
A rule that only returns results computed over at least a minimum number of subjects, plus limits on overlapping queries, so that shared analytics ca…
patternComputation-Only Collaboration
Two parties analysing their combined data without either receiving the other's records, by permitting only queries whose outputs are aggregate.
patternData Clean Room
A controlled environment where two parties analyse their combined data without either gaining access to the other's raw records.
conceptDifferencing Attack
Inferring an individual's data from the difference between two permitted aggregate results - the reason that returning only aggregates is not by itse…
conceptMatch Rate Bias
The systematic skew introduced when only the identifiable subset of each party's population joins, so a shared measurement describes the matched coho…
Neighbouring topics
Data Governance & Semantics
General material on ownership, meaning, quality and control of data at enterprise scale.
Data Mesh
Domain ownership, data as a product, self-serve platform, and federated governance.
Data Products
A dataset with an owner, an interface, an SLO, and consumers who can rely on it.
Data Contracts
Producers committing to schema, semantics and freshness, and breaking builds when they do not.
Data Catalog
Discovery, ownership and technical metadata, and why catalogues go stale.
Business Glossary
Agreeing what a term means before arguing about which number is right.
Semantic Layer
Metric definitions held once and served to every tool that asks.
Master Data Management
One authoritative record for a customer or product across systems that each have their own.
Reference Data
Code lists, hierarchies and currencies — small, shared, and quietly load-bearing.
Data Quality Dimensions
Completeness, accuracy, timeliness, consistency, validity and uniqueness as testable claims.
Data Observability
Freshness, volume, schema and distribution monitoring for pipelines that fail silently.
Data Stewardship
The operating model that makes ownership a role rather than a slide.
Data Access Models
Role, attribute and purpose-based access over analytical data, and how they compose.
Row & Column-Level Security
Restricting slices of a table rather than the whole table, and where it is enforced.
Tokenisation & Masking
Dynamic masking, deterministic tokens, and preserving joinability without exposure.
Retention & Purge
Deleting from an append-only estate, and proving the deletion happened.
Sensitivity Labelling
Propagating a classification through joins and derived tables so controls follow the data.
BI Governance
Dashboard sprawl, certified reports, and the number the board is allowed to see.
Self-Service vs Governed
Letting analysts move fast without four teams reporting four different revenues.