> 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/datasets.md).

# Datasets

What a dataset is, its types and sources, and which type and source combinations are available.

## What a dataset is

A **dataset** represents a structured collection of records that can be imported into the platform, shared in a Clean Room, and used as input for dataset matching and analysis. Every dataset is stored in your [Bunker](https://docs.mediarithmics.io/collaboration/plan-and-integrate/understand-data-collaboration-concepts/bunkers.md).

Each dataset is defined by these characteristics:

* **Type** - the nature of the records it holds.
* **Source** - where the records originate from.

## Dataset types

| Type                | Description                                                                        | Typical use case                             | Availability |
| ------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------- | ------------ |
| **Segment**         | A single audience segment that contains unique identifiers such as email addresses | Standard activation and audience matching    | Self-service |
| **Segment catalog** | A collection of audience segments                                                  | Bulk 1-to-N overlap analysis                 | Self-service |
| **User profile**    | Enriched user-level attributes                                                     | Deep-dive analytics on overlapping audiences | Self-service |
| **Campaign log**    | Raw advertising exposure events                                                    | Attribution and frequency analysis           | On request   |
| **Transaction log** | Purchase and sales events                                                          | ROI and conversion analysis                  | On request   |

## Dataset sources

| Source             | Description                                                    | Availability |
| ------------------ | -------------------------------------------------------------- | ------------ |
| **Datamart**       | Records are imported from your mediarithmics environment (CDP) | Self-service |
| **File**           | Records are imported from a file upload                        | Self-service |
| **Data warehouse** | Records are imported from an external data warehouse           | Provisioned  |

## Dataset types and sources availability matrix

The following table shows the availability of each combination of dataset type and source.

<table data-search="false"><thead><tr><th></th><th>Datamart</th><th>File</th><th>Data warehouse</th></tr></thead><tbody><tr><td><strong>Segment</strong></td><td>Self-service</td><td>Self-service</td><td>Provisioned</td></tr><tr><td><strong>Segment catalog</strong></td><td>Self-service</td><td>Self-service</td><td>Provisioned</td></tr><tr><td><strong>User profile</strong></td><td>Not available</td><td>Self-service</td><td>Provisioned</td></tr><tr><td><strong>Campaign log</strong></td><td>On request</td><td>On request</td><td>On request</td></tr><tr><td><strong>Transaction log</strong></td><td>On request</td><td>On request</td><td>On request</td></tr></tbody></table>

{% hint style="info" %}
**Self-service** - you create, manage, and use the dataset independently. **Provisioned** - mediarithmics creates it for you; once available, you use it independently. **On request** - not yet natively supported in self-service; mediarithmics can support the use case through a managed implementation. Contact your Account Manager.
{% 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>Manage your datasets</strong></td><td>Create a dataset in your Bunker, by type and by source.</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>Share your datasets</strong></td><td>Share a dataset into a Clean Room.</td><td><a href="https://docs.mediarithmics.io/collaboration/prepare-your-environment/share-your-datasets.md">Share your datasets</a></td></tr><tr><td><strong>Matching keys</strong></td><td>The identifiers your dataset and your partner's are matched on.</td><td><a href="https://docs.mediarithmics.io/collaboration/plan-and-integrate/understand-data-collaboration-concepts/matching-keys.md">Matching keys</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/datasets.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.
