> 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/developers/how-to-find-inbound-developers-in-reo.dev.md).
# How to Find Inbound Developers in Reo.Dev
When managing active developers in Reo.Dev, you may track activity across both **first-party assets** (your website, docs, product, Slack community, LinkedIn page) and **third-party assets** (competitor or complementary GitHub repositories).
While integrating competitor & complementary GitHub repos expands your **TOFU (Top of Funnel)** audience for targeted ads and email campaigns, it can make the **Developer Tab** cluttered when you need to focus on developers **engaging with your owned assets**.
To streamline this, we recommend creating an **"Inbound Developers" segment**—a filtered view of developers who are active on your first-party assets, excluding those only interacting with third-party repositories.
***
### **Steps to Create an Inbound Developers Segment**
#### **1) Navigate to the Segment Creation Panel**
1. In Reo.Dev, go to **Segments** panel.
2. Click **Create New**
3. Select Advance Segment & Choose **Developer Segment.**
4. Name the segment **"Inbound Developers"**.
***
#### **2) Define Segment Criteria**
Use the **Advanced Filtering** options to include only first-party engagement activities.
**Segment Filters Configuration**
| **Criteria** | **Includes Any** |
| ------------------------ | --------------------------------------------- |
| Repository Type | OWNER |
| Activity Type: Website | Viewed Pages, Copied Content |
| Activity Type: Docs | Docs Review, Copied Content |
| Activity Type: Product | Screen Visited, Product Login, Copied Content |
| Activity Type: Slack | Posts, Reactions, Replies, Joined Community |
| Activity Type: LinkedIn | Reposts, Comments, Reactions |
| Data API (if applicable) | Custom Telemetry Metric |
{% hint style="info" %}
**Note:** If your integrated data sources are different, modify the filters to reflect the first-party assets you track in Reo.Dev.
{% endhint %}
🔗 **Related Guide:** [Understanding Basic and Advanced Segments in Reo.Dev](/segments/basic-and-advanced-segments.md)
***
### **Why This Matters**
* Helps you **focus on engaged developers** within your ecosystem.
* **Filters out** developers only active on third-party repos.
* Enables **better targeting** for nurture campaigns & community-building.
***
### Summary
By configuring this segment, you create a **clear, first-party developer audience** in Reo.Dev, helping your team differentiate inbound interest from external activity.
---
# 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/developers/how-to-find-inbound-developers-in-reo.dev.md?ask=&goal=
```
`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.