Skip to main content

Primary Rulesets

When multiple rulesets are active for the same scoring surface, a lead can have multiple concurrent scores — one per ruleset. The primary ruleset designates which score is treated as the default. This page explains why primary rulesets matter and how to configure them.

Why a Primary Ruleset?​

Without a primary, the UI doesn't know which score to show. Should the Leads table sort by the campaign-specific score or the general engagement score? Should the level badge reflect the experimental ruleset's tier or the production one?

The primary ruleset answers that question with a single canonical default. Every other active ruleset's score remains accessible — in tooltips, in the per-ruleset score map, in API responses — but the primary is what you see by default.

What the Primary Ruleset Powers​

  • Single canonical score in the UI. Leads table, lead detail, default sorting, and level badges use the primary ruleset's score.
  • Default API responses. Many endpoints return a score without requiring a ruleset_id. With a primary configured, the default comes from the primary ruleset.
  • Per-OU control. Primary rulesets are configured per Organizational Unit, so different OUs can default to different rulesets independently.
  • Stable level calculations. Levels are computed against the primary score, keeping prioritization consistent.
  • Profile and account parity. You can set a primary engagement ruleset, a primary profile ruleset, and (with ABM enabled) a primary account ruleset.

Setting the Primary​

In the App​

  1. Navigate to Configure > Scoring.
  2. Pick the scoring surface (Engagement / Profile / Account / Deal).
  3. Find the ruleset you want as primary.
  4. Click the ⋯ menu and choose Set as Primary.

You can set one primary per surface per OU.

Via API​

When creating a ruleset, include is_primary: true:

  • Engagement: POST /engagement-scoring/rulesets
  • Profile: POST /profile-scoring/rulesets
  • Account (requires ABM): POST /account-scoring/rulesets

Fallback Behavior​

If no primary is configured for an OU, the UI falls back to the highest engagement score across all active rulesets. This keeps lists and levels usable, but it's ambiguous and can shift unexpectedly when rulesets change. Setting a primary explicitly is always recommended.

Score Visibility When Multiple Rulesets Are Active​

The UI doesn't hide non-primary scores — it just emphasizes the primary:

  • The leads table score cell shows the primary score, with a tooltip listing the top three alternate ruleset scores.
  • Tooltips appear only when at least two rulesets have a score for the lead.
  • The leads toolbar shows badges for the primary engagement and primary profile ruleset names when consistent across the filtered results. If different leads use different primaries (rare, after switches), the badge reads "varies by lead".

This makes A/B testing painless — production scoring stays canonical while experimental rulesets accumulate parallel data you can review on demand.

Switching the Primary​

Switching primary is the typical roll-forward pattern:

  1. Build the new ruleset alongside the existing one.
  2. Activate both. Both produce scores in parallel.
  3. Compare results — review the tooltip alternates on the leads table to see how the new ruleset would tier leads differently.
  4. When confident, set the new ruleset as primary.
  5. Optionally deactivate the old one.

The switch is instant. The UI re-reads the primary ruleset and Leads, levels, and default APIs all reflect the new canonical score immediately.