> 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/activate-audiences-across-partners.md).
# Activate audiences across partners
Send the common or exclusive users of a datasets matching to your activation platforms.
## Your goal
Once a datasets matching has computed the overlap between your audience and your partner's, reach either the **common** users or your **exclusive** users on your preferred activation platforms.
## Prerequisites
* A completed [datasets matching](/collaboration/collaborate-with-a-partner/analyze-cross-partner-behavior.md) between a dataset of yours and one of your partner's.
* Both datasets must be **Segment** type and shared in the Clean Room with the **Activation** purpose.
* You must be the Clean Room's **Administrator**, and a Core CDP customer.
## Activate a matching result
{% stepper %}
{% step %}
### Open the matching
Head to your Clean Room, open **Matched datasets**, and pick the datasets matching to activate.
{% endstep %}
{% step %}
### Go to Activation
Click the **Activation** tab.
{% endstep %}
{% step %}
### Choose which users
Click **Activate common records**, or **Activate exclusive records** (the Clean Room owner's exclusive records - the users in your dataset that did not match your partner's).
{% endstep %}
{% step %}
### Set up the feed
Follow the same Feed setup described in the `Audience & Activation` section, under Set up a destination.
{% endstep %}
{% endstepper %}
## Which identifiers you can activate with
Any identifier compatible with the selected feed, and available in your own environment, can be used to activate common or exclusive users - the **Matching stats** tab shows which identifiers are available for the matched users.
{% hint style="info" %}
Identifiers used for activation do not need to be the same as the ones used during matching. For example, you can use **hashed email** to match users with a partner, then activate the matched users on an ad platform using their **mobile IDs**, **email**, or **phone number**.
{% endhint %}
## Managing the compatible feed list
By default, no feeds are available for activation within a Clean Room. The list of feeds available is based on mutual agreement between both partners - only feeds mutually approved are whitelisted.
{% hint style="info" %}
Contact your Account manager to whitelist the feeds approved by you and your partner for a particular Clean Room. Only server-side feeds can be whitelisted.
{% endhint %}
Both partners of a Clean Room can see which feeds have been activated on a matching, and the volume of identifiers upserted or deleted for each.
## Related pages
---
# 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/activate-audiences-across-partners.md?ask=&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.