> 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/collaborate-with-a-partner/enrich-user-profiles-with-partner-segments.md).

# Enrich user profiles with partner segments

Enrich your user profiles with the segments of a Segment catalog that overlap with your audience.

{% hint style="info" %}
Enrichment is in Alpha. Contact your Account Manager to learn more.
{% endhint %}

## Your goal

Enrich your user profiles with the segments of a Segment catalog - for example a data provider's socio-demographic, geographic and affinity segments - so that you know your customers better and can build more relevant segments of your own, without either side sharing raw data.

## Expected outcome

Your user profiles carry the catalog segments they belong to, based on the overlap computed in the Clean Room between your audience and every segment of the catalog.

## Before you start

* The Clean Room Template authorizes the **Enrichment** [output](https://docs.mediarithmics.io/collaboration/plan-and-integrate/understand-data-collaboration-concepts/collaborative-apps.md#what-a-collaborative-app-is).
* A [Segment catalog](https://docs.mediarithmics.io/collaboration/plan-and-integrate/understand-data-collaboration-concepts/datasets.md#dataset-types) is shared in the Clean Room, sourced from a datamart or [from a file](https://docs.mediarithmics.io/collaboration/prepare-your-environment/manage-your-datasets.md#create-a-segment-catalog-dataset).
* A [matching](https://docs.mediarithmics.io/collaboration/collaborate-with-a-partner/analyze-cross-partner-behavior.md#datasets-matching) exists between a Segment dataset and that catalog. Its [bulk match rate](https://docs.mediarithmics.io/collaboration/collaborate-with-a-partner/analyze-cross-partner-behavior.md#match-rate) shows the overlap per catalog segment.

## Activate enrichment

{% stepper %}
{% step %}

#### Open the matching

Open the matching from the **Matched datasets** tab, and go to its **Enrichment** tab. The tab appears only when the Clean Room Template authorizes the **Enrichment** output and a Segment catalog was used in the matching.
{% endstep %}

{% step %}

#### Activate it

Click **Activate enrichment**. The setting applies to every Segment catalog available in the Clean Room, and to all of their segments.
{% endstep %}

{% step %}

#### Wait for the next computation

Enrichment takes effect at the next scheduled computation, not immediately. The platform then calculates the overlap between the Segment dataset and every catalog segment.
{% endstep %}

{% step %}

#### Plan the profile enrichment

Your user profiles are enriched with the matched catalog segments by the mediarithmics team. Ask your Account Manager to plan it.
{% endstep %}
{% endstepper %}

## Boundaries

* **All catalogs, all segments.** Enrichment covers every Segment catalog in the Clean Room and all of their segments: there is no per-catalog or per-segment choice.
* **Not immediate.** Activating or deactivating takes effect at the next scheduled computation, so switching it several times in a row does not launch extra computations.
* **Small overlaps are left out.** Catalog segments whose overlap is too small are not used.
* **Stopping it.** Click **Deactivate enrichment**, in the same tab.

## 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>Analyze cross-partner behavior</strong></td><td>Match a Segment dataset with a Segment catalog, and read the overlap per catalog segment.</td><td><a href="https://docs.mediarithmics.io/collaboration/collaborate-with-a-partner/analyze-cross-partner-behavior.md">Analyze cross-partner behavior</a></td></tr><tr><td><strong>Manage your datasets</strong></td><td>Create a Segment catalog dataset, from a datamart or a file.</td><td><a href="https://docs.mediarithmics.io/collaboration/prepare-your-environment/manage-your-datasets.md">Manage your datasets</a></td></tr><tr><td><strong>Clean Rooms</strong></td><td>The authorized outputs a Clean Room Template allows, Enrichment included.</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/collaborate-with-a-partner/enrich-user-profiles-with-partner-segments.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.
