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

# UserProfile

The timeless information you hold about a user, how it attaches to a UserPoint, and what to fill when you import it.

## Your goal

Know what a UserProfile holds and how it attaches to a user, so that the profiles you import land on the right UserPoint, in the right compartment.

## Expected outcome

Profiles that carry the account and compartment they belong to, and that hold the timeless information your use cases need.

## What a UserProfile is

A **UserProfile** is a summary of timeless information about the user, such as first name, last name, birth date, address, or age. It is usually imported from an existing information system such as a CRM or a login database, and typically collects:

* Contact details.
* User preferences.
* Status in a loyalty programme.
* Subscriptions to a newsletter.
* CRM information.
* Scores calculated outside the platform.
* Aggregated values.

Each UserProfile is associated with a UserPoint by a [user identifier](https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/user-identity/user-identifiers.md). It can also be linked to a [UserAccount](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).

A UserPoint can carry several UserProfiles on the same datamart, kept apart by [compartment](https://docs.mediarithmics.io/setup-and-monitor/plan-and-integrate/set-up-the-environment/set-up-compartments.md) - for example a profile on one of your sites and another profile on another site.

## The profile object

| Field                 | Type              | Description                                                                                |
| --------------------- | ----------------- | ------------------------------------------------------------------------------------------ |
| `$user_account_id`    | String, optional  | The associated UserAccount ID. If none, the profile remains anonymous.                     |
| `$compartment_id`     | Integer, optional | The compartment ID. If none, the profile is imported into the default compartment.         |
| `$last_modified_ts`   | Timestamp         | The timestamp of the last edit operation on this profile. Set automatically by the system. |
| `$creation_ts`        | Timestamp         | The timestamp of the creation of this profile. Set automatically by the system.            |
| *any custom property* | Any               | The value of a custom property.                                                            |

```json
{
    "$compartment_id": 1606,
    "$user_account_id": "c9879698769OIUYOIY9879879",
    "$last_modified_ts": 5467987654613,
    "$creation_ts": 6579874654654654,
    "firstname": "<first name>",
    "lastname": "<last name>",
    "gender": 1,
    "newsletter_options": {
        "subscribed": true,
        "preferred_periods": "MONTHLY"
    }
}
```

## When importing profiles

A `UserProfile` carries `$user_account_id` and `$compartment_id` of its own, separately from the identifier used to route the import.

{% hint style="warning" %}
When importing profiles, fill `$user_account_id` and `$compartment_id` in the profile itself **even if the values are the same** as the ones used as the identifier - the values are not inherited from the identifier information.
{% endhint %}

The compartment ID and the account in the profile object can legitimately differ from the ones used as the UserPoint identifier. See [Import profiles](https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/import-profiles.md).

## Verify

* Every imported profile carries `$user_account_id` and `$compartment_id` inside the profile object.
* A known test user shows the profile in the compartment you targeted.

## 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>Import profiles</strong></td><td>Load CRM data and scoring into user profiles.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/import-profiles.md">Import profiles</a></td></tr><tr><td><strong>Enrich user profiles</strong></td><td>Targeted updates inside an existing profile.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/enrich-user-profiles.md">Enrich user profiles</a></td></tr><tr><td><strong>Compartments</strong></td><td>Keep profiles from different systems separate on the same user.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/plan-and-integrate/set-up-the-environment/set-up-compartments.md">Compartments</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/user-profile.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.
