> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/commerce-data-models/users.md).

# Users

### New vs. repeat users

In purchasing, we have the concept of new vs. returning users or customers:

**New Users:** Whether or not the user is a new user, as defined by if the user has completed a first order.

**Repeat Users:** Whether or not the user is a returning user, as defined by the user has purchased again following a first order.

If analyzing new unique users and repeat unique users in a given period, they can be counted more than once since a user can be both new and repeat in the period when there's more than one purchase. As a result, the count of new users plus the count of repeat users may be greater than the count of total unique users. For example, this user is shown as a new and repeat user in this period and only counted once as a unique customer:

| User OMS User ID | Unique New Customer Count | Unique Repeat Customer Count | Unique Customer Count |
| ---------------- | ------------------------- | ---------------------------- | --------------------- |
| 12345678         | 1                         | 1                            | 1                     |

If we add the purchase dates, we'll see that this user purchased twice over the period analyzed, which is why this user shows as both new and repeat in this period:

| User OMS User ID | Order Completed Date | Unique New Customer Count | Unique Repeat Customer Count | Unique Customer Count |
| ---------------- | -------------------- | ------------------------- | ---------------------------- | --------------------- |
| 12345678         | 1/1/2024             | 1                         | 0                            | 1                     |
| 12345678         | 2/5/2024             | 0                         | 1                            | 1                     |

{% hint style="success" %}
if you have any questions or need help, please reach out to us at <help@chord.co>
{% endhint %}


---

# 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.chord.co/model-your-data/commerce-data-models/users.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.