🎮 Moving Beyond “The Click” to “The Action”

In Traditional Lead Scoring (1.0), points are assigned to marketing interactions.

• Downloaded eBook → +10 points
• Opened Email → +5 points

This works for service businesses. It fails for SaaS.

In SaaS, you don’t care if someone reads your blog. You care if they use your product.

• Invited a team member → +50 points
• Hit the export limit → +100 points
• Logged in 5 days in a row → +75 points

This is Lead Scoring 2.0. It tracks behavior — not just content consumption. It identifies Product Qualified Leads (PQLs): users who are raising their hand by using your product aggressively.

The engine behind this is HubSpot Custom Behavioral Events (CBEs) (Marketing Hub Enterprise).

CBEs let you track any digital action — inside your app, on your website, or in third-party tools — and use it for workflows and scoring.

📡 What Is a “Custom Behavioral Event”?

Think of it as a pixel on steroids.

• Standard Events: Page views, form submissions, email clicks (tracked automatically by HubSpot)
• Custom Events: “Clicked Add to Cart,” “Completed Onboarding Step 3,” “invited_user” (you define these)

You can capture CBEs in three ways:

• The Code Way: Using the HubSpot Tracking Code API (JavaScript) inside your app
• The No-Code Way: HubSpot Chrome Extension to click and select site elements
• The API Way: Sending server-side events from your backend

🧪 The PQL Model: 3 Events You Must Track

A strong SaaS scoring model tracks the true “Aha!” moments.

Event 1: The “Activation” Moment

• Event: completed_onboarding
• Logic: A user who signs up but never completes setup is a churn risk. A user who completes setup is an active lead.
• Score: If completed_onboarding occurs -> +20 Points.

Event 2: The “Viral” Moment

• Event: invited_team_member
• Logic: SaaS is sticky when teams use it. A single user is a tester. A team is a customer.
• Score: For every invited_team_member event -> +10 Points (Cumulative).

Event 3: The “Paywall” Moment

• Event: hit_usage_limit OR clicked_upgrade_button
• Logic: The user tried to do something, but the free plan stopped them. They hit the ceiling. They are begging to pay you.
• Score: If hit_usage_limit occurs -> +100 Points (Instant PQL).

🛠️ The Automation: Turning Events Into Sales

Scoring without action is useless.

Step 1: The “PQL” Workflow

• Trigger: HubSpot Score > 100
• Action: Set Lifecycle Stage → PQL
• Action: Rotate to Sales PQL Team
• Action: Create Task — “User hit usage limit. Call now.”

Step 2: The “Smart Nurture”

• Trigger: completed_onboarding has NOT occurred in 3 days
• Action: Send email: “Stuck on setup? Here’s a 2-minute guide.”

⚠️ The “Enterprise” Reality Check

Custom Behavioral Events are powerful — and they’re an Enterprise feature.

• YES: If you are a PLG (Product-Led Growth) SaaS with a "Free Trial" or "Freemium" model. You cannot run PLG without behavioral data.
• NO: If you are "Sales-Led" (Demo Request only). Standard "Page View" tracking is probably enough for you.

Stop selling to readers. Sell to users.

Lead Scoring 2.0 shifts your GTM from Marketing-Led to Product-Led. Sales talks to people who tried to upgrade — not people who downloaded a PDF.