Skip to main content

Scoring Rules

Scoring rules let you automatically rank domains based on criteria that matter to your business. Each rule assigns points based on domain attributes, and the total score determines lead priority.

🎬Scoring Rules ConfigurationStep 1 of 6
🕰️CronDB Dashboard
📊Dashboard
🔍Explorer
📋Lead Lists
⚙️Scoring Rules
🔑Alerts
📧Developer
Scoring Rules
1
Click Scoring Rules
Navigate to Scoring Rules under Lead Management.

How Scoring Works

  1. You define rules — conditions that award or deduct points
  2. CronDB evaluates every domain against your rules
  3. Each domain gets a total score (sum of all matching rules)
  4. Domains are ranked from highest to lowest score
  5. Scores update automatically when domain data changes

Creating a Scoring Rule

  1. Navigate to Lead Management → Scoring Rules
  2. Click + New Scoring Rule
  3. Give it a name (e.g., "Ideal Customer Profile")
  4. Add conditions and point values
  5. Click Save Rule

Rule Configuration

Each rule consists of one or more conditions, each with a point value:

Industry Match

Award points when a domain matches your target industries:

ConditionPointsExample
Industry is "Technology"+25Target industry
Industry is "Healthcare"+20Secondary target
Industry is "Adult Content"-50Exclude

Country Match

Prioritize domains from your target markets:

ConditionPointsExample
Country is "US"+15Primary market
Country is "GB"+10Secondary market
Country is "EU" (any)+5Tertiary market

Tech Stack Match

Score higher for domains using technologies you sell to or integrate with:

ConditionPointsExample
Uses "Shopify"+30E-commerce target
Uses "WordPress"+10Common CMS
Uses "Intercom"+20Chat tool user
Uses competitor product+25Displacement opportunity

Business Type

ConditionPointsExample
Business Type is "B2B SaaS"+20Target type
Business Type is "Marketplace"+15Secondary type

Contact Data Availability

ConditionPointsExample
Has email+10Reachable
Has phone+5Extra contact
Has LinkedIn+5Social presence
No contact data-20Hard to reach

Confidence Score

ConditionPointsExample
Confidence > 0.9+10High-quality data
Confidence < 0.5-15Unreliable data

Weight Configuration

Each condition has a weight (point value) that can range from -100 to +100. Use negative weights to penalize unwanted attributes.

Example: SaaS Sales Scoring Model

Industry is "Technology"           → +25 points
Country is "US" or "GB" → +15 points
Uses "Stripe" or "Chargebee" → +30 points (payment = SaaS signal)
Business Type is "B2B SaaS" → +20 points
Has email contact → +10 points
Confidence > 0.85 → +10 points
Registered in last 90 days → +5 points
No website detected → -30 points

A domain matching all positive criteria would score 115 points — a top-tier lead.

Applying Scores to Lists

Scoring rules apply automatically to:

  • All domains in the Domain Explorer search results
  • All domains in your Lead Lists
  • All domains in your Audiences

The score column appears in all tables and can be used for sorting and filtering.

Score Tiers

CronDB automatically categorizes scored domains into tiers:

TierScore RangeLabelColor
Hot80+Hot LeadRed
Warm50–79Warm LeadOrange
Neutral20–49NeutralGray
ColdBelow 20Cold LeadBlue

These tiers appear as colored badges in the dashboard and can be used as filter criteria.

Multiple Scoring Rules

You can create multiple scoring rules for different use cases:

  • ICP Score — How well a domain matches your ideal customer profile
  • Intent Score — Based on tech adoption and buying signals
  • Timing Score — Based on registration recency and activity

Each rule produces its own score column. You can view all scores side-by-side in the domain table.

Scoring Rule Limits

PlanMax Rules
Free1
Starter5
Pro25
EnterpriseUnlimited
Best Practice

Start with one comprehensive scoring rule based on your ideal customer profile. Refine the weights over time based on which scored leads actually convert.

Next Steps

  • Lead Lists — Apply scores to your existing lists
  • Audiences — Combine audiences with scoring for prioritized segments
  • Scoring API — Apply scoring programmatically via the API