> For the complete documentation index, see [llms.txt](https://developer.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.mediarithmics.io/user-points/user-identifiers.md).

# User identifiers

It is important to distinguish the nodes representing a user identifier and the nodes describing content on the user. 

Every activity or import that'll have one of those properties set will automatically be related to the correct UserPoint.

Any activity using an identifier that doesn't already exist in the datamart will trigger the creation of a new UserPoint.

{% hint style="info" %}
You can bulk associate, dissociate or delete user identifiers using the [bulk import](/data-ingestion/bulk-processing.md) feature.
{% endhint %}

There are three different types of user identifiers:

* [User accounts](/user-points/user-identifiers/useraccount.md)
* [User emails](/user-points/user-identifiers/useremail.md)
* [User device points and device technical ids](/user-points/user-identifiers/userdevicetechnicalid.md)


---

# 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://developer.mediarithmics.io/user-points/user-identifiers.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.