> 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/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects.md).

# Understand mediarithmics standard objects

The objects every mediarithmics data model is built from, and what each of them holds.

## Your goal

Know the objects the platform stores about a user before you write a schema or send data, so you can tell which object each piece of your data belongs to.

## Expected outcome

For each kind of data you hold, you know the standard object it lands in, and whether that object identifies the user or describes them.

## What a standard object is

A **standard object** is one of the objects the [default schema](https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/schema-definition.md#the-default-objects) declares, with its standard properties. Every one of them hangs off the [UserPoint](https://docs.mediarithmics.io/setup-and-monitor/understand-mediarithmics/how-mediarithmics-works.md#how-your-data-is-modelled-the-userpoint), the root element of any mediarithmics schema, which connects every piece of information collected about one user.

Standard objects fall into these families:

* **Identifiers** decide *who* the data belongs to, and therefore when two UserPoints become one: UserAccount, UserEmail, and UserDevice with its UserDeviceTechnicalIds. See [User identity](https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/user-identity.md).
* **Describing content** is what you query and segment on: UserActivity and UserEvent, UserProfile, UserSegment, and UserChoice.

## The objects

<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>UserActivity &#x26; UserEvent</strong></td><td>The interactions with a user, and the predefined events that power built-in analytics.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects/user-activity-and-user-event.md">UserActivity &amp; UserEvent</a></td></tr><tr><td><strong>UserAccount</strong></td><td>A registered user, from your CRM, loyalty programme, or authentication system - always paired with a compartment.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects/user-account.md">UserAccount</a></td></tr><tr><td><strong>UserProfile</strong></td><td>The timeless information you hold about a user.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects/user-profile.md">UserProfile</a></td></tr><tr><td><strong>UserSegment</strong></td><td>The record that says a user belongs to an audience segment.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects/user-segment.md">UserSegment</a></td></tr><tr><td><strong>UserEmail</strong></td><td>An identifier derived from the email address, normally a hash.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects/user-email.md">UserEmail</a></td></tr><tr><td><strong>UserDevice &#x26; UserDeviceTechnicalId</strong></td><td>Devices and their technical identifiers - cookies, mobile IDs, network IDs.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects/user-device.md">UserDevice &amp; UserDeviceTechnicalId</a></td></tr><tr><td><strong>UserChoice</strong></td><td>A user's choice for one of your processing activities.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects/user-choice.md">UserChoice</a></td></tr></tbody></table>

## 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>Schema definition</strong></td><td>Declare these objects and index the properties you query on.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/schema-definition.md">Schema definition</a></td></tr><tr><td><strong>User identity</strong></td><td>Identifiers, the identity graph, and resolution.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/user-identity.md">User identity</a></td></tr><tr><td><strong>How mediarithmics works</strong></td><td>Where the UserPoint sits in the platform.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/understand-mediarithmics/how-mediarithmics-works.md">How mediarithmics works</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/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects.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.
