LogoLogo
API DocsChangelogPlaybooksLoginBook a Demo
  • Getting Started
    • Introduction to Reo.Dev
    • For Users
      • Step 1: Find active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Identify developers engaging with your product
      • Step 4: Build custom segments that are most likely to convert
      • Step 5: Use filters to spot high-intent leads
    • For Admins
      • Step 1: Identify active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Find developers engaging with your product
      • Step 4: Create custom segments that are most likely to convert
      • Step 5: Integrating data sources with Reo.Dev
      • Step 6: Integrate Slack and set up notifications
      • Step 7: Add Customer Fit Criteria
  • Accounts
    • Account Lifecycle Stage
    • Custom CRM Stages
    • Developer Funnel Stages
    • Account Activity Score
    • Tags
    • Customizing Tags
    • Custom Lists
    • Using the Lists API in Reo.Dev
    • Managing CRM Owners in Reo.Dev
    • Follow an Account
    • How to Set Up Notification Alerts for Accounts, Developers & Segments in Reo.Dev
    • Flag incorrect data
  • Developers
    • Interpreting Intel on the Developer view page
    • Developer Activity Score
    • How to Find Inbound Developers in Reo.Dev
  • Segments
    • Creating Segments
    • Basic & Advance Segments
    • Filters 101
    • Segment Actions
    • My Segments
    • Shared Segments
    • Magic Segments
    • Favourite Segment
    • Add notes for better collaboration and context
    • CSV Exports for Segments
    • 10 Advanced Segments to create to spot high-intent opportunities
  • Buyers
    • Find Buyer Contact
    • How to Find, Segment & Engage Decision-Makers in Reo.Dev’s Buyer Section
    • Buyer Persona Configuration in Reo.Dev
  • Enrichment
    • Enrichment
  • Audiences
    • Buyer Audience
  • Integrations
    • Connect GitHub repositories
    • Reo.Dev Zapier Integration Guide
    • Webhooks
    • Developer Docs
      • Docusaurus
      • GitBook
    • CRM
      • HubSpot
      • Salesforce
      • Pipedrive
      • Zoho
      • Freshworks
      • Leadsquared
    • Tracking Beacon
      • Install JavaScript for Documentation
      • Install JavaScript for Product
      • Install JavaScript in Website
      • Install JavaScript in Local Product
      • Track Code Interactions
      • Install JavaScript for Documentation through Google Tag Manager
      • Reo.Dev JavaScript Cookies and Consent Guide
    • Product Usage API
      • Overview
      • How to Configure Product Usage Metrics in Settings
      • Telemetry Data
      • Product API
      • Examples of Product Usage Metrics
      • Data Collected for Product Usage
    • Communities
      • Open Communities
      • Owned Communities
        • Slack
        • LinkedIn Company Page
    • Email
      • Apollo.io
      • How to Integrate and Use Outreach.io with Reo.Dev
      • How to Integrate and Use Salesloft with Reo.Dev
    • Website Tracking
      • RB2B
  • Analytics
    • Impact Dashboard
  • Campaigns
    • Run bulk email campaigns
    • Testing Your Email Integration with Reo.Dev
  • Settings
    • Add Customer Fit Score Criteria
    • Add Firmographic and Technographic Filters
    • Configure Slack & Email Notifications
  • Account and Contact Usage Limit
    • Manage Account and Contact Limit Usage
  • User Management
    • Invite a teammate to Reo.Dev
    • Manage CRM Permissions
    • Roles and Permissions: Admin vs User
    • What Happens to Data When a User Is Deleted in Reo.Dev?
  • FAQs/Troubleshooting
    • How to Exclude Competitors from My Segments in Reo.Dev?
    • How to Sync a Segment to Salesforce/HubSpot?
    • Why Is the 'Sync to CRM' Button Greyed Out?
    • I Synced My Accounts, But They Are Not Showing in My CRM – What to Do?
    • Why Am I Seeing More Accounts in CRM Than I Synced?
    • Why Can't I Find My Account in the Dashboard Search Bar?
    • Resolving Caching Issues in Reo.Dev
    • Understanding Score Discrepancies Between Account and Developer Activity Score
    • Reo.Dev Credit-Based Pricing: FAQs
Powered by GitBook
LogoLogo

Resources

  • Changelog
  • Playbooks
  • DevGTM Conversations
  • Support
  • API Docs

Company

  • Blog
  • Contact Us
  • Book a Demo

Policies

  • Privacy Policy
  • Terms of Service

© 2025 All rights reserved Reo.Dev

On this page
  • How Activity Score is Calculated for Accounts
  • Filtering Accounts by Activity Score Category
  • Create Account Segments Using Activity Score Filters
  • Insights Panel & Trend Analysis
  • Actionable Playbooks for Account Engagement
  • Key Takeaways
  • FAQs: Account Activity Score

Was this helpful?

  1. Accounts

Account Activity Score

PreviousDeveloper Funnel StagesNextTags

Last updated 12 days ago

Was this helpful?

Activity Score at the account level in Reo.Dev measures developer engagement across all identified developers within an organization. This score is an aggregated metric that evaluates engagement based on recency, frequency, and intent across multiple tracked sources.

Overview:

  • Available as both a categorical (High, Medium, Low) and numeric (0-100) score.

  • Hover functionality shows activity sources contributing to the score.

  • Insights Tab in an Account displays a 90-day trend graph for account activity score.

  • Numeric Activity Score filters allow for more granular targeting.


How Activity Score is Calculated for Accounts

The Activity Score at the account level aggregates activity from multiple sources, including:

  • Active Developers

  • GitHub Activity

  • Documentation Activity

  • Website Activity

  • Form Signups

  • Product Usage

  • Product Installation

  • Community Activity

  • Telemetry Activity

The account’s activity score is a weighted calculation of all its developers’ engagements.


Filtering Accounts by Activity Score Category

In addition to using Activity Score (Numeric) for advanced segmentation, you can also filter accounts by their Activity Score category (High, Medium, Low) directly from the Accounts panel.

How to Apply the Activity Score Category Filter:

  • Navigate to the Accounts panel.

  • Click on "Add Filter" and select Activity Score.

  • Choose from High, Medium, or Low to filter accounts accordingly.

  • Apply the filter to instantly see accounts that match the selected engagement level.

This provides a quick and easy way to identify high-activity accounts without needing to set up a numeric threshold.

Score Ranges:

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

This range applies to both Account Activity Score (AAS) and Developer Activity Score (DAS) and helps teams easily filter and prioritize high-value engagements.


Create Account Segments Using Activity Score Filters

  1. Navigate to the Accounts tab.

  2. Click on "Add Filter."

  3. Select Activity Score (either categorical or numeric).

  4. Apply conditions:

    • For categorical filtering: Choose High, Medium, or Low.

    • For numeric filtering: Use greater than, less than, or equal to conditions.

  5. Click Apply to filter the results.


Insights Panel & Trend Analysis

  • The Insights Tab for an account displays:

    • A 90-day trend graph of Activity Score fluctuations.

    • A detailed breakdown of activity volume per source (e.g., GitHub commits, docs reviews, website visits).

    • An overview of active developers contributing to the score.

Use this to track engagement trends and identify high-priority accounts.


Actionable Playbooks for Account Engagement

1. Identifying High-Engagement Accounts in Your Pipeline

Segment Criteria:

✔ Activity Score (Numeric) > 80 ✔ Lifecycle Stage: In Pipeline

Why This Matters:

Not all accounts in your pipeline are equal—some show significantly higher engagement than others. This segment helps you focus on accounts where developers are actively interacting with your product, whether through GitHub contributions, documentation views, or product usage. These accounts are likely closer to conversion and should be prioritized for follow-ups.

Action Steps:

  • Accelerate Sales Outreach – These accounts are already warmed up. Get your sales team to schedule demos, share case studies, or address potential blockers.

  • Provide Additional Support – Developers within these accounts are engaged. Offer personalized guidance, technical resources, or direct access to solutions architects to ensure they don’t drop off.

  • Monitor Activity Trends – If engagement is increasing, this could indicate a buying signal. If it’s dropping, it might mean the account is losing interest—adjust your approach accordingly.

  • Align with Marketing – Run ABM (Account-Based Marketing) campaigns targeting these accounts with relevant content, such as advanced use-case guides or customer success stories.


2. High-Engagement Accounts with Buyer Involvement

Segment Criteria:

✔ Activity Score (Numeric) > 80 ✔ Developer Tags: Buyer ✔ Lifecycle Stage: Not a Customer

Why This Matters:

This segment identifies accounts where developers are highly engaged, and a buyer is also present. This is crucial because while developer engagement is great, deals don’t close unless there’s a decision-maker involved. These are high-value accounts that need strategic attention to convert into paying customers.

Action Steps:

  • Activate Multi-Threading – Since a buyer is already engaged, introduce sales leadership or account executives into the conversation to navigate procurement discussions.

  • Leverage Developer Champions – Encourage the engaged developers in these accounts to internally advocate for your product. Provide them with ROI-focused content, internal pitch decks, or cost-benefit analysis reports to help push the deal forward.

  • Personalized Executive Engagement – Since this account isn’t a customer yet, a well-timed executive-level conversation could expedite the decision-making process. Consider inviting decision-makers to an exclusive roundtable or a private product roadmap discussion.

  • Monitor Engagement to Prevent Drop-offs – If engagement remains high but the deal isn’t progressing, check for objections, procurement delays, or competitor evaluations. Address these proactively with targeted messaging.


Key Takeaways

  • Aggregated score based on developer activity across multiple sources.

  • Helps track overall engagement of an account.

  • New trend graphs & segmentation filters for deeper insights.


FAQs: Account Activity Score

These FAQs help clarify how the Activity Score at the account level (AAS) works, how it is calculated, and how to use it effectively.

1. What parameters are included in Account Activity Score (AAS)?

The Account Activity Score (AAS) is calculated by aggregating developer activities across the following sources:

  • Active Developers

  • GitHub Activity

  • Documentation Activity

  • Website Activity

  • Form Signups

  • Product Usage

  • Product Installation

  • Community Activity

  • Telemetry Activity

Key Insight: The AAS aggregates engagement across all developers within an account, helping teams track overall account activity trends.

2. What does a score of 100 or 80 mean?

Activity Score is based on activity type, frequency, and recency.

  • 100 AAS = Highest engagement level. The account is actively interacting with multiple tracked sources on a consistent basis.

  • 80 AAS = Strong engagement, but not as recent. The account has performed key activities but may not be continuously active.

  • Scores naturally decay over time if there is no continued engagement. You can track these changes in the Insights tab to monitor trends.

Actionable Insight: 80+ AAS is a key marker of strong engagement and intent.

3. Why do some accounts have a score of 100?

Each tenant has unique activity thresholds based on their engagement patterns.

  • If an account crosses the defined engagement threshold, it receives a default score of 100 to indicate continuous high engagement.

  • This makes it easier to identify high-priority accounts.

Pro Tip: Instead of focusing on static 100s, track engagement trends over time to monitor increases or decreases in activity.

4. What is considered a "good" Account Activity Score?
  • 60+ AAS = Moderate engagement—good, but may require continued nurturing.

  • 80+ AAS = Strong engagement—ideal for outreach and prioritization.

  • 100 AAS = Continuous engagement—potential champions and power users.

Pro Tip: Tracking Activity Surges in Accounts

To identify accounts with a sudden increase in activity over the past 7 days, you can use the "Has Activity Surge" filter. This is a strong signal that helps prioritize high-intent accounts.

How is a "Surge" calculated in Reo.dev?

A Surge occurs when the Account Activity Score (AAS) for an account increases by more than 40 in the last 7 days. The surge status lasts for 7 days unless the activity continues to increase, in which case it may persist.

There are two ways to apply this filter in the product:

1) As a Segment Filter for Account Segments:

  • When creating an account segment, add the "Has Activity Surge" filter to identify accounts that have seen a recent spike in activity.

  • This is useful for automating tracking and running targeted campaigns for engaged accounts.

2) Directly in the Accounts Panel:

  • If you’re already viewing an account segment, click "Add Filter" at the top left.

  • Select "Surge" from the dropdown to instantly filter the list based on recent activity spikes.

  • This is helpful for quick, on-the-fly analysis without needing to create a new segment.

Using the Activity Surge filter in both ways ensures you never miss a high-engagement account that’s moving down the funnel.


5. How can I track and improve Account Activity Score?
  • Focus on increasing developer interactions with GitHub, documentation, product usage, and community participation.

  • Identify trends in engagement to spot growth opportunities or potential drop-offs.

  • Use trend reporting to measure engagement changes over time and refine activation strategies.

Takeaway: Tracking and improving AAS helps measure account health, developer engagement, and pipeline movement.

For a deeper understanding of how Activity Score is calculated at the Developer Level, checkout our

[Developer Activity Score Guide].