> 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/~/revisions/LpXrIuXoRo1tuAYMfI7z/getting-started/for-admins/step-3-find-developers-engaging-with-your-product.md).
# Step 3: Find developers engaging with your product
Reo.Dev empowers you with in-depth insights into developers engaging with your product assets. In this guide, we will take you through the different intel Reo.Dev provides for each developer.
**Step 1:** Navigate to the **Developers** page on the left panel. Here, you'll find various details about developers such as their company, location, Job Title, Dev Activity score, and contact IDs.
**Step 2:** **Click on a developer's name** to see their detailed profile and activity log.
The **Developer Profile** provides information such as designation, current company, joining date, location, first and last activity dates, past companies & more.
**Developer Activity** gives you a quick overview of the activities (and the count of activities) the developer has done across different sources/channels.
The **Activity Timeline** shows you a chronological view of all the activities done by the developer. You can further use the activity filter to narrow down and view specific activities.
This gives you more context on developer actions and helps you personalize your outreach based on those actions.
---
# 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.reo.dev/~/revisions/LpXrIuXoRo1tuAYMfI7z/getting-started/for-admins/step-3-find-developers-engaging-with-your-product.md?ask=&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.
