> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/why-a-developer-profile-may-not-be-created-on-reo.dev.md).

# Why a Developer Profile May Not Be Created on Reo.Dev

Reo captures developer activity across different channels and uses verified identity signals to create developer profiles. In most cases, when we have enough confidence in a developer’s identity, a profile is created and associated with the relevant account.

However, there may be cases where an activity is captured, but a developer profile is not created. Reo prioritizes data accuracy and identity confidence when creating developer profiles.

Creating profiles based on incomplete or unverified information can lead to:

* Incorrect developer profiles
* Wrong account associations
* Duplicate records
* Low-confidence de-anonymization
* Noisy account activity

To prevent this, Reo only creates developer profiles when the underlying identity signals meet the required confidence threshold.

### When can this happen?

#### 1. The email address could not be verified

In some cases, Reo may capture an email address from a developer activity source, such as a community interaction or product activity.

However, if the email address cannot be verified, Reo may not create a developer profile. This is done to avoid creating incorrect or low-confidence developer records.

An email may be difficult to verify if it is temporary, inactive, recently deleted, or not consistently recognized by verification systems.

#### 2. The activity signal is available, but identity confidence is low

Reo may capture activity such as:

* Joining a community
* Visiting a page
* Interacting with documentation
* Using a product or developer tool
* Engaging with other tracked developer touchpoints

However, activity alone may not always be enough to create a developer profile. If Reo cannot confidently verify who the developer is, the activity may be retained without generating a full profile.

#### 3. The developer is not yet available in Reo’s developer graph

Sometimes, Reo may capture a signal related to a developer, but the developer may not yet exist as a verified entity in Reo’s developer graph.

In such cases, Reo may not immediately create a profile unless there are enough verified identity signals available.

#### 4. The available data is too limited

There may be cases where the only available information is an email address or a single activity event.

If that information is not enough to confidently confirm the developer’s identity, Reo may avoid creating a developer profile to maintain data accuracy.


---

# 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://docs.reo.dev/why-a-developer-profile-may-not-be-created-on-reo.dev.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.