How to Find Inbound Developers in Reo.Dev

When managing developer audiences 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 Segment.

3. Select Advance Segment & Choose Developer Segment.

4. Name the segment "Inbound Developers".

5. Set Segment Type to 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

Note: If your integrated data sources are different, modify the filters to reflect the first-party assets you track in Reo.Dev.

🔗 Related Guide: Understanding Basic and Advanced Segments in Reo.Dev

---

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.