Skip to main content

Levels (Engagement, Profile, Account)

Levels classify leads and accounts into named ranges based on their scores. This makes it easier to understand at a glance where a lead stands in your funnel and helps teams prioritize outreach.

Types of Levels​

Engagement Levels​

Engagement Levels bucket a lead's engagement score into named ranges like "Cold," "Warm," and "Hot."

Use Case: Quickly identify leads showing high buying intent based on their recent activity.

Example Configuration:

  • Cold (0-24 points): Minimal engagement, needs nurturing
  • Warm (25-49 points): Showing interest, ready for marketing follow-up
  • Hot (50-74 points): High engagement, sales-ready
  • Very Hot (75+ points): Extremely engaged, immediate outreach recommended

Profile Levels​

Profile Levels bucket a lead's profile fit score based on demographic and firmographic attributes.

Use Case: Identify leads that match your ideal customer profile (ICP) regardless of engagement.

Example Configuration:

  • Poor Fit (0-24 points): Doesn't match ICP criteria
  • Okay Fit (25-49 points): Some ICP match, moderate priority
  • Strong Fit (50-74 points): Good ICP match, high priority
  • Perfect Fit (75+ points): Ideal customer profile

Account Levels (Phase 2 - ABM)​

Phase 2 Feature

Account Levels are part of LeadVibe's Account-Based Marketing (ABM) capabilities in Phase 2 and require ABM to be enabled in Settings → Scoring. Contact your account manager for access.

Account Levels bucket account scores when ABM is enabled.

Use Case: Prioritize entire companies/accounts based on aggregate signals.

Example Configuration:

  • Low Intent (0-24 points): Minimal account-level activity
  • Medium Intent (25-49 points): Some engagement across contacts
  • High Intent (50+ points): Strong signals across multiple contacts

How Levels Work​

Score-Based Classification​

Each level is defined by:

  • Name: The label displayed to users (e.g., "Hot")
  • Min Score: Minimum score (inclusive) for this level
  • Max Score: Maximum score (inclusive) for this level
  • Color: Optional color for UI display

Example:

{
  "name": "Hot",
  "min_score": 50,
  "max_score": 74,
  "color": "#FF6B35"
}

OU Scoping​

Levels are configured per Organizational Unit (OU):

  • Each OU can define its own level thresholds
  • Level names and ranges are independent across OUs
  • All API operations respect the active OU

Non-Overlapping Ranges​

Level ranges cannot overlap within the same OU:

  • ✅ Valid: Level A (0-24), Level B (25-49), Level C (50+)
  • ❌ Invalid: Level A (0-50), Level B (25-75) - overlaps at 25-50

Adjacent ranges are allowed and recommended.

Infinity Ranges​

Use a very high number (2147483647) to represent infinity for the max score:

  • Hot (75 to 2147483647): Captures all scores ≥ 75

Configuring Levels​

Via Web UI​

Engagement Levels:

  1. Navigate to Configure → Engagement Levels
  2. Click Add Level
  3. Enter name, min score, and max score
  4. Optionally choose a color
  5. Save

Configure Levels page showing the color-coded level bar visualization, level table with score ranges, and Add Level button

Profile Levels:

  1. Navigate to Configure → Profile Levels
  2. Follow same steps as Engagement Levels

Account Levels (when ABM enabled):

  1. Navigate to Configure → Account Levels
  2. Follow same steps as Engagement Levels

Via API​

Engagement Levels Endpoints:

  • GET /engagement-levels - List all levels for current OU
  • POST /engagement-levels - Create new level
  • PUT /engagement-levels/{id} - Update existing level
  • DELETE /engagement-levels/{id} - Delete level

Profile Levels Endpoints:

  • GET /profile-levels
  • POST /profile-levels
  • PUT /profile-levels/{id}
  • DELETE /profile-levels/{id}

Account Levels Endpoints (ABM required):

  • GET /account-levels
  • POST /account-levels
  • PUT /account-levels/{id}
  • DELETE /account-levels/{id}

Example: Create Engagement Level:

curl -X POST "https://api.leadvibe.com/engagement-levels" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Hot",
    "min_score": 50,
    "max_score": 74,
    "color": "#FF6B35"
  }'

Response:

{
  "level_id": "level_abc123",
  "name": "Hot",
  "min_score": 50,
  "max_score": 74,
  "color": "#FF6B35",
  "created_at": "2025-01-15T10:00:00Z",
  "updated_at": "2025-01-15T10:00:00Z"
}

How Levels Are Used​

Lead Lists​

Levels appear as chips in the Leads table:

  • Display: "Level 3 • Hot" or just "Hot" depending on view settings
  • Sorting: You can sort leads by level
  • Filtering: Filter to show only leads in specific levels

Leads table showing engagement scores, profile scores, engagement level badges such as Committed, Very Engaged, Engaged, Cold, and New, and profile level badges such as Good Fit, Bad Fit, and Okay alongside each lead

Lead Detail Pages​

Lead detail pages show both:

  • Engagement Level: Based on engagement score
  • Profile Level: Based on profile fit score

Notifications​

Slack, Teams, and webhook notifications include level information:

{
  "lead_id": "ld_123",
  "engagement_score": 75,
  "engagement_level": "Very Hot",
  "profile_score": 85,
  "profile_level": "Perfect Fit"
}

Segments​

You can create segments based on levels:

  • "All Hot Leads" → Engagement Level = Hot
  • "Strong Fit, Low Engagement" → Profile Level = Strong Fit AND Engagement Level = Cold

Validation Rules​

When creating or updating levels:

  1. Name Required: Must provide a non-empty name
  2. Min ≤ Max: Minimum score must be less than or equal to maximum score
  3. No Overlaps: Ranges cannot overlap with existing levels in the same OU
  4. Score Bounds: Scores must be integers between -2147483648 and 2147483647

Common Errors:

ErrorCauseSolution
"Ranges overlap"New level overlaps with existing levelAdjust min/max to eliminate overlap
"Min greater than max"min_score > max_scoreSwap the values or correct the input
"Name required"Empty or missing nameProvide a descriptive level name

Best Practices​

Naming Conventions​

Use clear, intuitive names:

  • ✅ Good: Cold, Warm, Hot, Very Hot
  • ✅ Good: Low Fit, Medium Fit, High Fit
  • ❌ Bad: Level 1, Level 2, Level 3 (not descriptive)

Number of Levels​

Recommended: 3-5 levels per score type

  • Too few (1-2): Not enough granularity
  • Too many (8+): Overwhelming, hard to act on

Score Distribution​

Design ranges based on your actual score distribution:

  1. Review your leads' current scores
  2. Identify natural breakpoints
  3. Ensure each level has meaningful volume

Example: If 90% of leads score below 50, don't make your "Hot" level 75+

Alignment Across Teams​

Ensure sales and marketing agree on:

  • What each level means
  • What actions to take for each level
  • When to escalate from one level to another

Regular Review​

Revisit level thresholds quarterly:

  • Are the right leads being prioritized?
  • Do level names still resonate with teams?
  • Have scoring models changed requiring level adjustments?

Troubleshooting​

"No level shown for this lead"​

Cause: Lead's score doesn't fall within any defined level range

Solution: Ensure you have levels covering the full score range, including negative scores if negative scoring is enabled

Example Fix: Add a "Very Cold" level with range -∞ to -1 or 0

"Account Levels page missing"​

Cause: ABM is not enabled for your organization

Solution: Contact your account manager to enable ABM features in Settings → Scoring

"Level changes but UI doesn't update"​

Cause: Browser cache or stale data

Solution: Refresh the page or clear browser cache

"Can't delete level"​

Cause: Some systems may prevent deletion if levels are referenced elsewhere

Solution: Check if the level is used in segments, triggers, or dashboards before deleting

  • Segments: Create segments based on level membership
  • Triggers: Fire triggers when leads move between levels
  • Scoring Rules: The rules that generate the scores levels are based on
  • Notifications: Levels appear in Slack/Teams notifications

See Also: