> 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.mediarithmics.io/user-points/user-identifiers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.