Practitioner's Guide
Why Models Lose Credibility
Paminga surfaces three separate score types, each measuring a different dimension of a contact's relationship with your brand. That separation keeps your model from overvaluing a single signal and gives your team clearer context before sales gets involved.
Title, company size, location, persona tier, and other fields that tell you whether the person fits your ICP.
Form fills, event registration, account sign-up, email clicks, and other actions that show awareness.
Event attendance, repeat content visits, portal logins, conversions, and other signals of deeper intent.
Key principle
Contact Score
Contact score is built from who the person is, not what they have done. Typical inputs include job title, persona tier, company size, industry, geography, region, and any other field that helps identify fit.
If a contact matches criteria that signals they are not a fit — wrong region, irrelevant industry, student email — subtract points. Without subtractors, the wrong record can still accumulate points and appear qualified.
A required rule means the condition must be true for the contact to qualify at the threshold level, regardless of total score.
Example
Activity and Engagement
Activity score is the action layer: broad, high-volume, and relatively low-signal on its own. Engagement score captures the quality and depth of interaction, not just that the interaction happened.
Registered for a webinar
Attended the webinar
Received a newsletter
Clicked every newsletter for six months
Clicked a link in an email
Clicked a link and converted on the destination page
Signed up for a portal account
Logged into the portal 5+ times in 30 days
Run frequency matters
Thresholds and Actions
Once contacts accumulate scores, Paminga lets you define what happens when they hit certain levels. You can set an MQL threshold for total score, then add minimum score requirements per category so a contact cannot qualify entirely on demographic fit with no engagement.
Example threshold
Global Action
Any record that hits the threshold, such as enrolling in a nurture workflow when engagement score reaches 15.
Use when the same follow-up should happen for every qualifying record.
Conditional Action
Records that meet the threshold and an additional condition, such as creating a Salesforce task if engagement reaches 15 and last activity was 90+ days ago.
Use when the next step depends on context beyond the score itself.
Enroll in a workflow, create a CRM task, send an internal notification, add to a paid ads audience, or sync a field to your CRM.
If engagement drops beneath a certain level, you can automatically add the contact to a re-engagement or nurture sequence.
Building a Model That Holds Up
A lead scoring model is only as good as the math underneath it. Before launching, map out scoring rules and calculate how many realistic activity and engagement signals a contact would need to hit your MQL threshold.
Know how much each category can contribute so one dimension does not overwhelm the others.
Let scores cool as intent ages, especially when a contact stops engaging.
Use negative signals to prevent poor-fit records from looking qualified.
Pressure test
Worked Example
A Director of Marketing Ops at a mid-market SaaS company submits a form on a migration guide page. It is a meaningful signal — right persona, right content, right moment — but it is not enough on its own. The journey to MQL combines fit, activity, and repeated engagement.
This contact qualifies because the model confirms ICP fit, awareness of Paminga, and active engagement. A global action can enroll them in a sales-touch workflow, while a conditional action can create a Salesforce task with context for the assigned rep.
Final thought
Lead Scoring in Paminga
Talk with a platform expert about contact, activity, engagement, thresholds, decay, and the actions your team wants to automate.
Schedule Your Personalized DemoBuilt with pride in Denver, Colorado, USA
Copyright © Paminga, Inc. 2026