# Dev Activity Score

The Activity Score at the developer level in Reo.Dev is a personalized engagement metric that evaluates an individual developer’s interactions with your product ecosystem. It provides a numerical (0-100) and categorical (High, Medium, Low) score based on their recency, frequency, and intent of activities.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F3C1OTNOUMIAl05IxGoWG%2Fimage.png?alt=media&#x26;token=ba8d7731-f387-4950-a788-23aaee5b3b35" alt=""><figcaption></figcaption></figure>

**Overview**

* Activity Score is now available at the Developer level.
* Numeric (0-100) and categorical (High, Medium, Low) formats.
* Hover functionality provides detailed activity breakdowns.

***

### **How Activity Score is Calculated for Developers**

A developer's **Activity Score** is based on their interactions with key sources, including:

* GitHub Activity
* Documentation Activity
* Website Activity
* Form Signups
* Product Usage
* Product Installation
* Community Activity
* Telemetry Activity

{% hint style="info" %}
For a deeper understanding of how Activity Score is calculated at the account level, checkout our [\[Account Activity Score Guide\].](https://docs.reo.dev/accounts/account-activity-score)
{% endhint %}

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F4WinK02ColNEZWtd6ve6%2Fimage.png?alt=media&#x26;token=eea32935-efc7-450a-b521-96921ddc22d3" alt=""><figcaption></figcaption></figure>

The developer’s score is a real-time reflection of their engagement with your product.

***

### **Filtering Developers by Activity Score**

#### **Step 1: Apply Filters in the Developers Segment**

1. Navigate to **Segments** → Create a **Developer Segment.**
2. Click **"Add Filter."**
3. Select **Activity Score (Numeric) or Activity Score**&#x20;

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FUPLfGH3IENbMSAcRsypv%2Fimage.png?alt=media&#x26;token=15ed5083-8181-4ecb-88db-307299feee3d" alt=""><figcaption></figcaption></figure>

**Apply conditions:**

* **For Activity Score filtering:** Choose **High, Medium, or Low**

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2Fx2gi5zEosmbGjozZ7SYY%2Fimage.png?alt=media&#x26;token=2195175e-5bdb-4501-9396-ac0b280f33a4" alt=""><figcaption></figcaption></figure>

* **For Activity Score (Numeric) filtering:** Use **greater than, less than, or equal to** conditions.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FfcvxePjRxs7z10I0GIib%2Fimage.png?alt=media&#x26;token=5e3d061e-1b95-4a3c-94b2-59fde3ceba1f" alt=""><figcaption></figcaption></figure>

**Score Ranges for High, Medium, & Low:**

* **High:** **60 - 100** → Strong engagement, high activity levels.
* **Medium:** **20 - 60** → Moderate engagement, requires nurturing.
* **Low:** **0 - 20** → Minimal activity, potential drop-off risk.

These score ranges provide a standardized way to assess developer engagement and help teams quickly prioritize high-value developers.

***

### **Developer Profile Card & Activity Score**

In a developer’s profile card, the Activity Score is displayed as a numeric value (0-100) along with a High, Medium, or Low label. This score provides a quick overview of the developer’s engagement level.

#### **Activity Score in the Developer Profile Card**

* Located in the developer profile card
* Shows a numeric score with a corresponding engagement level (e.g., High (100), Medium (50), Low (10)).
* Provides a snapshot of the developer’s activity strength based on tracked interactions.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2Fs8EdrupW1FTrAMX7McRp%2Fimage.png?alt=media&#x26;token=a1123f6f-4e41-4efe-9c45-01285aaad7bd" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Use this to assess a developer's engagement and identify potential advocates.
{% endhint %}

***

### Actionable Playbooks for Developer Engagement

#### **1. Identify Champions in ICP Accounts Active on GitHub**

**Filter Criteria:**

✔ Account > Intel > ICP Fit Score: "Strong" & "Moderate".

✔ Developer > Intel > Activity Score (Numeric) > 60

✔ Activity > Activity Type > GitHub: Includes any → Select All + Date Range is set to last 60 days

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FkcQBaoRWkGM5rgOZa3ap%2Fimage.png?alt=media&#x26;token=6f56708f-bea0-43af-b926-177c66a92f07" alt=""><figcaption></figcaption></figure>

**Action:**\
Prioritize these developers for direct outreach—engage them with technical content and relevant resources tailored to their activity timeline. Customize your pitch and messaging based on their interactions. Additionally, identify key buyers within the account to connect with decision-makers.

👉 For more guidance, check out this guide: [\[Find Buyer Contact\].](https://docs.reo.dev/buyers/find-buyer-contact)

***

#### **2. Find Champion Developers in Your Target List**

**Filter Criteria:**

* Account > Source > Lists > Developers: Select a specific uploaded developer list to create a segment.
* Developer > Intel > Activity Score : Includes any "HIGH"

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F7mkfKA7pW5B0jkzwx1Yj%2Fimage.png?alt=media&#x26;token=ecd6ea55-56ff-40e6-9169-c01905ffd928" alt=""><figcaption></figcaption></figure>

**Action Steps:**

* **Prioritize outreach to these highly engaged developers**—review their activity history and tailor messaging based on their interactions with your product.
* **Offer personalized technical resources** such as in-depth documentation, advanced tutorials, or product deep dives to keep them engaged.
* **Invite them to participate in hands-on experiences** like beta testing, feature previews, or hackathons to strengthen their connection with your product.
* **If their organization is a target account, align with sales teams to identify key buyers** and create a warm introduction based on the developer's engagement.

***

### **Key Takeaways**

* A granular engagement metric for individual developers.
* Allows better segmentation & targeting based on developer activity.
* Supports GTM teams in identifying champions.

{% hint style="success" %}
Use the Developer Activity Score to engage top developers, identify champions, and drive advocacy!
{% endhint %}

***

### **FAQs: Developer Activity Score (DAS)**

These FAQs explain how the **Developer Activity Score (DAS)** works and how it helps track individual developer engagement.

<details>

<summary>1. What parameters are included in Developer Activity Score (DAS)?</summary>

The **Developer Activity Score (DAS)** is calculated based on an individual developer’s interactions across these sources:

* GitHub Activity
* Documentation Activity
* Website Activity
* Form Signups
* Product Usage
* Product Installation
* Community Activity
* Telemetry Activity

{% hint style="success" %}
**Key Insight:** The **DAS provides a granular view of a developer's engagement**, helping teams identify active users and champions.
{% endhint %}

</details>

<details>

<summary>2. What does a score of 100 or 80 mean?</summary>

DAS is based on **activity type, frequency, and recency**.

* **100 DAS** = **The developer is highly engaged and interacting frequently** with tracked sources.
* **80 DAS** = **The developer has engaged meaningfully but not as recently**.
* If a developer **stops engaging**, their DAS **will decay over time**.

{% hint style="success" %}
**Actionable Insight:** **80+ DAS** is a key indicator of developer activation and retention.
{% endhint %}

</details>

<details>

<summary>3. Why do some developers have a score of 100?</summary>

Each tenant has a **custom threshold** based on the frequency of developer activities.

* If a developer **crosses that threshold**, they are assigned **a default score of 100**, indicating **continuous high engagement**.
* This makes it easy to **identify power users and developer advocates**.

{% hint style="success" %}
**Pro Tip:** Instead of focusing on static 100s, **track developer engagement trends** over time to **spot champions and potential drop-offs.**
{% endhint %}

</details>

<details>

<summary>4. What is considered a "good" Developer Activity Score?</summary>

* **60+ DAS** = Moderate engagement—indicates an active but less frequent user.
* **80+ DAS** = Highly engaged—ideal for community building, outreach, and advocacy programs.
* **100 DAS** = **Consistently engaged—these developers are power users and potential champions.**

{% hint style="success" %}
**Pro Tip:** Monitor DAS over time to track developer adoption and conversion into advocates.
{% endhint %}

</details>

<details>

<summary>5. How can I track and improve Developer Activity Score?</summary>

* Encourage more developer interactions with GitHub, docs, product usage, and community engagement.
* Use DAS trends to identify potential champions and nurture them into advocates.
* Track week-over-week DAS changes to see which developers are becoming more engaged over time.

{% hint style="success" %}
**Takeaway:** **Aiming for 80+ DAS** helps track developer activation, retention, and potential champions.
{% endhint %}

</details>