> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/collaboration/plan-and-integrate/understand-data-collaboration-concepts/collaborative-apps.md).

# Collaborative Apps

The pre-configured envelopes mediarithmics provides, and what each one lets you and a partner do in a Clean Room.

## What a Collaborative App is

A Collaborative App is a pre-configured envelope that defines what kind of collaboration can happen in a Clean Room. Think of it as an application blueprint on top of the Clean Room infrastructure: it declares which datasets are expected, which analytical actions can be run, and which outputs are allowed. Collaborative Apps are provided out-of-the-box by mediarithmics - you pick the one that matches the business context of your partnership.

A Collaborative App declares:

| Property               | Description                                                                                                                                                                                                                                         |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Supported roles        | Which participant roles can join the collaboration (Advertiser, Retailer, Data Provider, …)                                                                                                                                                         |
| Expected dataset types | Which [dataset types](https://docs.mediarithmics.io/collaboration/plan-and-integrate/understand-data-collaboration-concepts/datasets.md#dataset-types) can be shared inside (Segment, Segment catalog, User profile, Campaign log, Transaction log) |
| Clean room actions     | Which operations are allowed (Overlap, Profile insights, Campaign reports, …)                                                                                                                                                                       |
| Authorized outputs     | Which types of data can leave the Clean Room: `INSIGHTS` (aggregated results only), `ACTIVATION` (identifiers leave for media activation), `ENRICHMENT` (user attributes or segment memberships leave to enrich a partner's datamart)               |

{% hint style="info" %}
Enforcement of some properties (supported roles, expected dataset types, clean room actions) is being rolled out progressively.
{% endhint %}

Each Collaborative App answers a distinct set of business questions:

| Collaborative App                  | For (Clean Room owner)                                                                               | What it lets you do                                                                                                                                                                        |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Data Sourcing**                  | An operator (publisher, broadcaster, retailer, platform) enriching its own data assets from partners | Enrich your inventory with third-party signals; build new monetizable segments from partner data; close blind spots in your datamart                                                       |
| **Media Audience Portal**          | A publisher or digital platform exposing its first-party audience catalog to advertiser partners     | Let advertisers project their CRM onto your inventory to measure addressable reach; offer strategic-segment targeting; enable exclusion or over-targeting without receiving files in clear |
| **Retail Brand Portal**            | A retailer exposing its shopper audience and business data to brand partners                         | Help brands identify shopper segments with the highest incremental potential; let brands measure incremental sales; expose cross-category buyer profiles                                   |
| **TV Audience Portal**             | A TV operator exposing its audience catalog to advertiser partners                                   | Let advertisers activate addressable TV from their own CRM segments; measure duplication between TV and digital reach; exclude loyal customers from acquisition campaigns                  |
| **Classified Ads Audience Portal** | A classified ads platform exposing its first-party behavioural audience                              | Let advertisers reach in-market users before they convert elsewhere; surface predictive intent signals; contextualize messaging to the intent phase                                        |

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Clean Room Templates</strong></td><td>Your organisation's configuration of a Collaborative App.</td><td><a href="https://docs.mediarithmics.io/collaboration/plan-and-integrate/understand-data-collaboration-concepts/clean-room-templates.md">Clean Room Templates</a></td></tr><tr><td><strong>Clean Rooms</strong></td><td>The space where you and a partner collaborate, and who does what in it.</td><td><a href="https://docs.mediarithmics.io/collaboration/plan-and-integrate/understand-data-collaboration-concepts/clean-rooms.md">Clean Rooms</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/collaboration/plan-and-integrate/understand-data-collaboration-concepts/collaborative-apps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
