Using Clean Room Templates
Clean room templates allow you to prepopulate multiple clean rooms with the same parameters, permissions, questions, flows, owner datasets, and other configurations and provision them to multiple partners. This can help you avoid manually configuring multiple clean rooms with similar configurations.
Possible use cases for templates include the following:
Create a proof-of-concept clean room for partner evaluation of data products
Perform overlap tests at scale for prospective partners
Productize a trial offering
You can create a template from scratch or from an existing clean room.
Once you create a template, you can use that template in a number of ways:
Generate a new clean room in the current organization
Add the template’s items (questions, flows, and Intelligence reports) to existing clean rooms in the current organization
Clean rooms generated from templates operate as independent clean rooms that can be customized or configured as desired.
When you create a clean room from a template, you can choose whether edits to a template’s questions get pushed to the clean rooms generated from that template or whether the clean rooms’ questions remain unchanged when the template’s questions are edited. In most cases, LiveRamp recommends decoupling the template from any generated or copied clean rooms. For more information, see the “Decoupling a Clean Room Template” section below.
Clean rooms created from templates inherently do not include partners or partner datasets because they are intended to be reusable across multiple collaborations. Once a clean room is generated from a template, it behaves like any other clean room. For a comprehensive guide on how to implement a new partnership within a clean room, see "Clean Room Owner Implementation Guide".
Once you’ve created a template, you can edit it. If you're no longer using a template, you can delete it.
Note
For answers to frequently asked questions, see "Template FAQs".
Decoupling a Clean Room Template
When you work with clean room templates, using “Decouple From Template” controls whether a generated clean room or copied template stays linked to the original template’s questions or becomes an independent copy.
You’ll see the Decouple From Template checkbox in two places:
When you generate a clean room from a template inside an org
In both flows, unchecked means coupled (ongoing question linkage between source and target), and checked means decoupled (independent copy).
Note
Other template flows (such as adding a template’s items to an existing clean room or creating a template from an existing clean room) operate as one‑time copies and do not establish an ongoing coupling relationship.
We strongly recommend checking “Decouple From Template” for most production and partner‑specific collaborations.
When you generate a clean room from a template and leave it coupled, small template changes can unexpectedly alter live collaboration behavior across many clean rooms.
The risk is even higher when you copy templates across organizations: if you don’t decouple in the Add to other Organizations flow, the original and copied templates remain linked for questions, so edits on either side can influence the other and their coupled clean rooms. Decoupling at generation/copy time turns those into safe forks that you can customize without surprise side effects.
Decoupling is the right choice whenever you expect local customization. After decoupling, you can freely adjust questions, adjust datasets and transforms, or tailor flows and Intelligence for a specific partner without worrying about changing anyone else’s environment. The trade‑off is that those decoupled clean rooms or templates stop receiving automatic question updates from the original template: if you later fix a bug or improve a query in the template, you’ll need to intentionally copy or re‑provision those changes into already‑decoupled clean rooms.
When you keep the template coupled, question logic lives in a shared “brain”: changes to template questions (such as SQL edits or new versions) can automatically update questions in coupled clean rooms, and certain edits made in coupled clones can also flow back to the template and out to other coupled rooms. In a decoupled state, that link is broken for questions—future changes in the template no longer affect the decoupled clean room/template, and its own edits no longer affect the original or other clones.
When you do not decouple, template question updates can be a powerful way to centrally manage a library of questions and roll out improvements uniformly—useful for tightly managed internal deployments, standardized proofs of concept, or short‑lived pilot environments where you explicitly want everything to move in lockstep. Even in those cases, remember that most other template changes (parameters, flows, Intelligence layout, members) are not retroactive; they apply only to net‑new clean rooms generated from the template, while dataset transforms are copied at generation time and are not pushed retroactively later.
For more information, see “Template FAQs”.