> 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/measure-campaign-performance-with-third-party-data.md).

# Measure campaign performance with third-party data

What a Clean Room lets you measure about a joint campaign, and where the evidence stops.

## Your goal

Understand what a Data Clean Room lets you measure about a campaign run jointly with a partner, without either side exposing raw exposure or transaction data.

## What is documented

A Clean Room is described as a place where you can "measure the incremental sales, reach, or conversions generated by a joint campaign," and "analyze and measure campaign results (reach, frequency, …)." Two dataset types exist specifically to support this:

| Dataset type        | Typical use case                   | Availability |
| ------------------- | ---------------------------------- | ------------ |
| **Campaign log**    | Attribution and frequency analysis | On request   |
| **Transaction log** | ROI and conversion analysis        | On request   |

Some Collaborative Apps name measurement outcomes explicitly as part of what they are for - for instance, letting a brand "measure whether their campaigns on your inventory drove incremental sales," or letting an advertiser "measure the duplication between their TV reach on your inventory and their digital reach." See [Clean Rooms](/collaboration/plan-and-integrate/setup-clean-rooms/clean-rooms.md#what-a-collaborative-app-is) for the full list.

Beyond onboarding a Campaign log or Transaction log dataset and matching it like any other dataset (see [Analyze cross-partner behavior](/collaboration/collaborate-with-a-partner/analyze-cross-partner-behavior.md)), the resulting reach, frequency, incrementality, or attribution figures are delivered through **Insights dashboards built by the mediarithmics team on request** - there is no documented self-service measurement dashboard specific to campaign performance.

{% hint style="warning" %}
Campaign log and Transaction log datasets are on-request rather than self-service. Contact your Account manager to scope a measurement use case before assuming it is available in your environment.
{% endhint %}

{% hint style="info" %}
Measuring a campaign's performance **without** third-party data - tracking, attribution models, funnels, and A/B testing - is documented in the `Measurement & Attribution` section.
{% endhint %}

## 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>Insights and match rate, common to every matching.</td><td><a href="/collaboration/collaborate-with-a-partner/analyze-cross-partner-behavior.md">Analyze cross-partner behavior</a></td></tr><tr><td><strong>Share your datasets</strong></td><td>Dataset types, including Campaign log and Transaction log.</td><td><a href="/collaboration/prepare-your-environment/share-your-datasets.md">Share your datasets</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/measure-campaign-performance-with-third-party-data.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.
