AirbookLogo
Integrations
Pricing
AirbookLogo
Customer Success Guide

How to Join Product Usage and CRM Data to Understand Account Health

Learn how to combine product usage data with CRM data to predict churn, identify expansion opportunities, and improve customer success operations. Complete with SQL examples and step-by-step setup.

45 min setup time
Advanced level
Customer Success focused

Introduction

Most SaaS companies track product usage and customer data in completely separate systems. Product teams monitor feature adoption in Amplitude or Mixpanel. Sales teams track deals and accounts in Salesforce or HubSpot. Customer Success teams are left trying to manually piece together which accounts are healthy, at risk of churning, or ready for expansion.

This guide shows you how to automatically join product usage data with CRM data to create a complete view of account health. You'll learn to identify churn risk before it's too late, spot expansion opportunities early, and give your Customer Success team the insights they need to be proactive rather than reactive.

Why This Matters for Your Business

73%
reduction in churn when usage data informs CS outreach
2.3x
higher expansion revenue with usage-based segmentation
45%
faster time to identify at-risk accounts
Pro Tip: The most successful SaaS companies don't just track usage—they tie usage to business outcomes. This guide shows you how to connect the dots between product engagement and revenue metrics.

Tools You'll Need

To implement account health scoring using product usage and CRM data, you'll need access to the following tools and data sources:

Product Analytics Platform

Track user behavior and feature usage:

  • Amplitude: Event tracking, user properties, cohort analysis
  • Mixpanel: User engagement, feature adoption, retention
  • Pendo: Product analytics with user feedback
  • Custom events: Via Segment, mParticle, or direct API

CRM System

Customer and account relationship data:

  • Salesforce: Account records, opportunity data, contacts
  • HubSpot: Company properties, deal stages, contact info
  • Pipedrive: Organization data, pipeline tracking
  • Account details: Contract value, renewal dates, CSM assignments

Airbook Integration Platform

Airbook connects your product analytics and CRM data without requiring engineering resources. Key capabilities:

  • • Pre-built connectors to 150+ data sources
  • • Automatic schema mapping and data sync
  • • SQL workspace for custom analysis
  • • Real-time dashboards and alerts
  • • No-code data transformation
  • • Automated account health scoring
Data Requirements: You'll need at least 3 months of historical product usage data and corresponding CRM records to establish baseline health scores. The more historical data you have, the more accurate your churn predictions will be.

Step-by-Step Setup

Follow these steps to connect your product usage and CRM data sources and start tracking account health automatically.

1

Connect Your Product Analytics Data Source

Start by connecting your product analytics platform to Airbook. This will give you access to user events, feature usage, and engagement metrics.

For Amplitude users:

  • • Navigate to Data Destinations in your Amplitude project
  • • Create a new cohort export or raw data export
  • • Copy the API key and secret for Airbook integration
  • • Ensure you're exporting user properties and event properties
2

Connect Your CRM Data Source

Connect your CRM system to access account information, contract details, and customer relationship data.

For Salesforce users:

  • • Ensure you have API access enabled in your Salesforce org
  • • Create a connected app or use an existing one
  • • Note the Consumer Key, Consumer Secret, and Security Token
  • • Verify access to Account, Contact, and Opportunity objects
3

Set Up Account-to-User Mapping

The most critical step is mapping product users to CRM accounts. This connection allows you to aggregate usage data at the account level.

Mapping Strategies:
Email Domain: Map users with @company.com to Company Account
Account ID: Pass account_id as a user property in your product
Custom Fields: Use organization_id or tenant_id for multi-tenant apps
Contact Records: Join on email address through CRM contact records
4

Verify Data Integration

Before building complex queries, verify that your data is flowing correctly and accounts are properly mapped.

$ SQL Query
-- Verify account mapping coverage
SELECT 
  COUNT(DISTINCT crm_account_id) as mapped_accounts,
  COUNT(DISTINCT user_id) as total_users,
  COUNT(DISTINCT CASE WHEN crm_account_id IS NOT NULL THEN user_id END) as mapped_users,
  ROUND(
    COUNT(DISTINCT CASE WHEN crm_account_id IS NOT NULL THEN user_id END) * 100.0 / 
    COUNT(DISTINCT user_id), 2
  ) as mapping_coverage_percent
FROM amplitude_users

Sample SQL Query

Here's a comprehensive SQL query that combines product usage data with CRM information to calculate account health scores. This query creates a complete picture of account engagement, risk factors, and expansion opportunities.

$ SQL Query
-- Account Health Scoring: Join Product Usage with CRM Data
WITH usage_metrics AS (
  SELECT 
    account_id,
    account_name,
    
    -- Usage Activity Metrics
    COUNT(DISTINCT user_id) as active_users_30d,
    COUNT(DISTINCT DATE(event_time)) as active_days_30d,
    COUNT(*) as total_events_30d,
    
    -- Feature Adoption Metrics
    COUNT(DISTINCT CASE WHEN event_type = 'feature_used' THEN event_properties:feature_name END) as features_used,
    COUNT(DISTINCT CASE WHEN event_type = 'advanced_feature_used' THEN user_id END) as power_users,
    
    -- Engagement Depth
    AVG(session_length_minutes) as avg_session_length,
    MAX(DATE(event_time)) as last_activity_date,
    MIN(DATE(event_time)) as first_activity_date,
    
    -- Value Realization Signals
    COUNT(DISTINCT CASE WHEN event_type = 'goal_completed' THEN event_id END) as goals_completed,
    COUNT(DISTINCT CASE WHEN event_type = 'integration_connected' THEN event_id END) as integrations_active
    
  FROM amplitude_events 
  WHERE event_time >= CURRENT_DATE - INTERVAL 30 DAY
    AND account_id IS NOT NULL
  GROUP BY account_id, account_name
),

crm_context AS (
  SELECT 
    id as account_id,
    name as account_name,
    annual_recurring_revenue__c as arr,
    contract_start_date__c as contract_start,
    contract_end_date__c as contract_end,
    customer_success_manager__c as csm_id,
    account_tier__c as tier,
    industry,
    employees as company_size,
    
    -- Contract Health
    DATEDIFF(contract_end_date__c, CURRENT_DATE) as days_to_renewal,
    DATEDIFF(CURRENT_DATE, contract_start_date__c) as days_since_start,
    
    -- Account Value Metrics
    CASE 
      WHEN annual_recurring_revenue__c >= 100000 THEN 'Enterprise'
      WHEN annual_recurring_revenue__c >= 25000 THEN 'Mid-Market' 
      ELSE 'SMB'
    END as revenue_segment
    
  FROM salesforce_accounts 
  WHERE type = 'Customer'
    AND is_deleted = FALSE
),

account_health AS (
  SELECT 
    u.account_id,
    u.account_name,
    c.arr,
    c.contract_end,
    c.days_to_renewal,
    c.revenue_segment,
    c.tier,
    c.industry,
    
    -- Usage Health Scores (0-100)
    LEAST(100, u.active_users_30d * 10) as user_adoption_score,
    LEAST(100, u.active_days_30d * 3.33) as frequency_score,
    LEAST(100, u.features_used * 5) as feature_breadth_score,
    LEAST(100, u.power_users * 20) as depth_score,
    LEAST(100, u.goals_completed * 2) as value_realization_score,
    
    -- Engagement Metrics
    u.active_users_30d,
    u.active_days_30d,
    u.features_used,
    u.power_users,
    u.avg_session_length,
    u.goals_completed,
    u.integrations_active,
    
    -- Risk Factors
    DATEDIFF(CURRENT_DATE, u.last_activity_date) as days_since_last_activity,
    CASE 
      WHEN DATEDIFF(CURRENT_DATE, u.last_activity_date) > 14 THEN 'High Risk'
      WHEN DATEDIFF(CURRENT_DATE, u.last_activity_date) > 7 THEN 'Medium Risk'
      ELSE 'Active'
    END as activity_risk_level,
    
    -- Expansion Signals
    CASE 
      WHEN u.power_users >= 5 AND u.features_used >= 15 THEN 'High Expansion Potential'
      WHEN u.power_users >= 2 AND u.features_used >= 8 THEN 'Medium Expansion Potential'
      ELSE 'Low Expansion Potential'
    END as expansion_potential
    
  FROM usage_metrics u
  LEFT JOIN crm_context c ON u.account_id = c.account_id
)

SELECT 
  account_id,
  account_name,
  arr,
  revenue_segment,
  tier,
  industry,
  
  -- Overall Health Score (weighted average)
  ROUND(
    (user_adoption_score * 0.25 + 
     frequency_score * 0.20 + 
     feature_breadth_score * 0.20 + 
     depth_score * 0.15 + 
     value_realization_score * 0.20), 1
  ) as overall_health_score,
  
  -- Individual Component Scores
  user_adoption_score,
  frequency_score, 
  feature_breadth_score,
  depth_score,
  value_realization_score,
  
  -- Engagement Details
  active_users_30d,
  active_days_30d,
  features_used,
  power_users,
  ROUND(avg_session_length, 1) as avg_session_minutes,
  goals_completed,
  integrations_active,
  
  -- Risk Assessment
  days_since_last_activity,
  activity_risk_level,
  days_to_renewal,
  
  -- Opportunity Classification
  expansion_potential,
  
  -- Health Categorization
  CASE 
    WHEN ROUND((user_adoption_score * 0.25 + frequency_score * 0.20 + feature_breadth_score * 0.20 + depth_score * 0.15 + value_realization_score * 0.20), 1) >= 80 THEN 'Excellent'
    WHEN ROUND((user_adoption_score * 0.25 + frequency_score * 0.20 + feature_breadth_score * 0.20 + depth_score * 0.15 + value_realization_score * 0.20), 1) >= 60 THEN 'Good'
    WHEN ROUND((user_adoption_score * 0.25 + frequency_score * 0.20 + feature_breadth_score * 0.20 + depth_score * 0.15 + value_realization_score * 0.20), 1) >= 40 THEN 'At Risk'
    ELSE 'Critical'
  END as health_category,
  
  contract_end

FROM account_health
ORDER BY overall_health_score DESC, arr DESC;
Query Explanation: This query creates a comprehensive account health score by combining usage activity, feature adoption, engagement depth, and value realization metrics. It weights different components based on their predictive power for churn and expansion.

Key Metrics Explained

User Adoption Score: Based on number of active users per account

Frequency Score: How often the account uses your product

Feature Breadth Score: Variety of features being used

Depth Score: Number of power users showing advanced usage

Value Realization: Completion of key goals or workflows

Expansion Signals: Usage patterns indicating growth potential

Visualizing Account Health

Raw account health scores are just the beginning. The real value comes from visualizing this data in ways that drive action across your Customer Success, Sales, and Product teams.

Account Health Dashboard

  • Health Score Distribution: Bubble chart showing accounts by health score vs. ARR
  • Risk Alerts: Red-flag accounts with declining health scores
  • Renewal Pipeline: Health scores overlaid on renewal calendar
  • Expansion Opportunities: High-health accounts ready for upsell

Customer Success Views

  • CSM Account Lists: Health scores grouped by CSM assignment
  • Engagement Trends: Usage trajectory over 90-day periods
  • Feature Adoption Maps: Heat maps showing feature usage by account
  • Cohort Analysis: Health scores by customer acquisition date
Dashboard Best Practices:
• Update health scores daily to catch changes early
• Include both absolute scores and trends (7-day, 30-day changes)
• Segment views by account value, industry, or customer lifecycle stage
• Set up automated alerts for accounts dropping below health thresholds

Essential Visualizations

Health Score Trends

Line charts showing health trajectories over time

Risk Segmentation

Accounts categorized by churn risk level

Revenue Impact

ARR at risk vs. expansion opportunities

Interpreting Results

Understanding what your account health scores mean and how to act on them is crucial for driving customer success outcomes. Here's how to interpret different score ranges and identify the right actions to take.

Health Score Benchmarks

80-100: ExcellentExpansion ready
60-79: GoodStable, monitor trends
40-59: At RiskNeeds intervention
0-39: CriticalImmediate action required

Red Flag Indicators

  • Declining user adoption: Fewer users active month-over-month
  • Feature abandonment: Drop in advanced feature usage
  • Reduced session frequency: Longer gaps between usage
  • Support ticket increase: More help requests or complaints
  • Integration disconnects: Removing connected tools
  • Admin-only usage: End users not engaging with product

Expansion Opportunity Signals

High Usage Velocity

  • • 5+ power users per account
  • • 90%+ feature adoption rate
  • • Daily active usage patterns

Value Realization

  • • Completing key workflows
  • • Multiple integrations active
  • • Goal achievement metrics

Growth Indicators

  • • Adding new team members
  • • Requesting advanced features
  • • API usage increasing
Trend Analysis: Don't just look at current scores—track 7-day and 30-day trends. A account with a score of 70 that's declining rapidly needs more attention than an account with a score of 60 that's steadily improving.

Who Should Track This

Account health scoring isn't just for Customer Success teams. Different roles need different views of the data, with varying frequencies and focus areas. Here's how each team should use account health insights.

Customer Success

Frequency: Daily monitoring

Focus: At-risk accounts, expansion opportunities

Actions: Proactive outreach, health check calls, onboarding optimization

Key Metrics: Overall health score, usage trends, feature adoption

Sales Teams

Frequency: Weekly reviews

Focus: Expansion revenue, upsell timing

Actions: Qualified expansion conversations, renewal strategy

Key Metrics: Expansion signals, power user growth, feature breadth

Product Teams

Frequency: Bi-weekly analysis

Focus: Feature adoption patterns, user engagement

Actions: Product roadmap decisions, feature optimization

Key Metrics: Feature usage depth, adoption rates, session quality

Revenue Operations

Frequency: Monthly reporting

Focus: Revenue forecasting, churn prediction

Actions: Model refinement, process optimization

Key Metrics: Predictive accuracy, revenue at risk, expansion pipeline

Executive Team

Frequency: Quarterly reviews

Focus: Strategic health trends, business impact

Actions: Resource allocation, strategic initiatives

Key Metrics: Portfolio health, churn rates, expansion rates

Data Teams

Frequency: Ongoing maintenance

Focus: Data quality, model accuracy

Actions: Pipeline monitoring, score calibration

Key Metrics: Data freshness, mapping coverage, prediction accuracy

Cross-Team Alignment: Set up shared dashboards and regular cross-functional reviews to ensure everyone is working from the same account health data. Misaligned metrics between teams can lead to conflicting customer outreach and poor experiences.

Mistakes to Avoid

After helping dozens of companies implement account health scoring, we've seen the same mistakes repeatedly. Here are the critical pitfalls to avoid when building your own system.

1. Over-Weighting Recent Activity

The Mistake: Giving too much weight to the last 7 days of activity, causing scores to fluctuate wildly based on vacation schedules, holidays, or temporary usage spikes.

The Fix: Use rolling 30-day averages and include trend analysis. A single week of low activity shouldn't tank an otherwise healthy account's score.

Example: An account goes quiet for a week due to a company holiday. Their health score drops from 85 to 45, triggering unnecessary CS outreach and creating customer confusion.

2. Ignoring Account Context

The Mistake: Using the same health scoring criteria for a 10-person startup and a 10,000-person enterprise. Different account sizes and industries have completely different usage patterns.

The Fix: Segment your scoring by account size, industry, or customer lifecycle stage. Create different benchmarks for different account types.

Example: A small startup with 3 active users gets a low health score, while an enterprise with 50 active users (out of 500 licenses) gets a high score, despite having much lower adoption rates.

3. Focusing on Vanity Metrics

The Mistake: Prioritizing metrics that look good (total logins, page views) over metrics that predict outcomes (feature depth, goal completion, integration usage).

The Fix: Focus on value-realization metrics. Track actions that correlate with customer success and retention, not just engagement volume.

Example: An account has high daily login counts but never completes key workflows or connects integrations. They churn despite appearing "engaged" in surface metrics.

4. Poor Data Quality Management

The Mistake: Not validating that product users are correctly mapped to CRM accounts, leading to incomplete or inaccurate health scores.

The Fix: Implement data quality checks and regular audits. Monitor mapping coverage and investigate accounts with suspiciously low usage data.

Example: 30% of your product users can't be mapped to CRM accounts due to email domain mismatches, causing major enterprise accounts to appear inactive.

5. Static Scoring Models

The Mistake: Setting up health scoring once and never revisiting the model. Customer behavior and product features evolve, but the scoring stays the same.

The Fix: Review and refine your scoring model quarterly. Test different weightings and add new metrics as your product and customer base mature.

Example: Your scoring heavily weights a feature that's no longer core to customer success, while ignoring a new integration that's become critical for retention.

6. Lack of Actionable Insights

The Mistake: Creating beautiful health score dashboards that don't tell teams what to do next. Scores without context or recommended actions don't drive behavior change.

The Fix: Include specific recommendations with each health score. "Account health: 45" should become "Account health: 45 - Low feature adoption, recommend onboarding call."

Example: CS team sees an account with a score of 60 but doesn't know if that's trending up or down, or what specific actions would improve the score.

Remember: Account health scoring is a tool to drive better customer outcomes, not an end in itself. If your scores aren't helping teams make better decisions and take more effective actions, revisit your approach.

Frequently Asked Questions

How do you join product usage data with CRM data for account health?

Answer: Join product usage data with CRM data by mapping product users to CRM accounts using email domains, account IDs, or custom identifiers. Connect your product analytics platform and CRM system through a data integration tool, then use SQL queries to combine usage metrics with account information.

Step-by-step process:

  1. Connect product analytics platform (Amplitude, Mixpanel)
  2. Connect CRM system (Salesforce, HubSpot)
  3. Map users to accounts via email domain or account ID
  4. Build SQL queries to aggregate usage by account
  5. Calculate health scores combining usage + CRM data

What are the key metrics for account health scoring?

Answer: Key metrics for account health scoring include user adoption, usage frequency, feature breadth, usage depth, and value realization. Weight these metrics based on their correlation with customer retention and expansion in your specific business.

Usage Metrics (60% weight):

  • • Daily/Weekly Active Users per account
  • • Session frequency and duration
  • • Feature adoption breadth and depth
  • • Goal completion rates

CRM Metrics (40% weight):

  • • Contract value and renewal dates
  • • Customer satisfaction scores
  • • Support ticket volume and sentiment
  • • Payment history and compliance

How do you predict churn using product usage and CRM data?

Answer: Predict churn by identifying accounts with declining usage patterns combined with CRM risk factors. Build predictive models that weight historical churn patterns against current account behavior and contract details.

High Churn Risk Indicators:

Usage Signals:
  • • 30%+ decrease in active users
  • • Reduced session frequency
  • • Declining feature adoption
  • • No goal completions in 30 days
CRM Signals:
  • • Contract renewal in 90 days
  • • Low NPS or CSAT scores
  • • Increased support tickets
  • • Budget constraints noted

What tools are needed to integrate product usage with CRM data?

Answer: You need a product analytics platform, a CRM system, and a data integration platform. Airbook provides pre-built connectors and SQL workspace for analysis without requiring engineering resources.

Product Analytics
Amplitude, Mixpanel, Pendo
CRM Platform
Salesforce, HubSpot, Pipedrive
Integration Platform
Airbook (recommended)

How do you map product users to CRM accounts accurately?

Answer: Map product users to CRM accounts using email domain matching, account ID properties, organization IDs, or contact record joins. Validate mapping coverage regularly to ensure account-level metrics accuracy.

Email Domain Matching (Most Common)
Map users with @company.com to "Company" account in CRM
Account ID Properties (Most Accurate)
Pass account_id as user property in product analytics
Contact Record Joins (B2B)
Join on email through CRM contact-to-account relationships

What are expansion opportunity signals in account health data?

Answer: Expansion opportunity signals include high user adoption within existing seats, advanced feature usage, API usage approaching limits, and strong engagement trends with health scores above 80.

Strong Expansion Signals:

  • • 90%+ seat utilization
  • • Premium feature adoption
  • • API limits being reached
  • • Multiple department usage
  • • High integration connectivity
  • • Consistent 30-day growth

Timing Indicators:

  • • 6+ months into contract
  • • Recent successful outcomes
  • • Budget planning season
  • • Team growth at company
  • • Product roadmap alignment
  • • Positive CSM interactions

How often should you monitor account health scores?

Answer: Monitor account health scores daily for high-value accounts, weekly for standard accounts, and monthly for lower-tier accounts. Set up automated alerts for significant score changes and accounts approaching renewal dates.

Account TierMonitoring FrequencyAlert ThresholdsResponsible Team
Enterprise (>$50k ARR)DailyScore drop >10 pointsCSM + Account Manager
Mid-Market ($10k-$50k)WeeklyScore drop >15 pointsCustomer Success
SMB (<$10k ARR)MonthlyScore drop >20 pointsCustomer Success

Real-World Implementation Scenarios

Learn from real implementations of account health scoring across different SaaS business models and use cases.

Scenario 1: B2B Collaboration Platform

Challenge:

Customer Success team couldn't identify which enterprise accounts were at risk until contracts were already up for renewal.

Implementation Approach:

  • • Connected Amplitude events to Salesforce accounts
  • • Mapped users via email domain + contact records
  • • Weighted collaboration events heavily (75%)
  • • Added contract timeline alerts

Key Metrics Tracked:

  • • Team invitation rates
  • • Cross-departmental usage
  • • Document sharing frequency
  • • Meeting integration usage

Results:

Reduced churn by 23% by identifying at-risk accounts 45 days earlier. Customer Success team now has 90-day lead time for intervention strategies.

Scenario 2: Analytics SaaS Platform

Challenge:

High trial-to-paid conversion but significant churn after 6 months due to poor adoption of advanced features.

Implementation Approach:

  • • Integrated Mixpanel with HubSpot deal data
  • • Created feature adoption scoring model
  • • Built expansion readiness indicators
  • • Automated CSM handoff workflows

Success Metrics Focus:

  • • Dashboard creation depth
  • • Data source connections
  • • Advanced query usage
  • • Report sharing behavior

Results:

Increased 12-month retention by 34% and identified $2.1M in expansion opportunities through advanced feature adoption tracking.

Scenario 3: DevTool Platform

Challenge:

Individual developer sign-ups weren't converting to team plans, missing enterprise expansion opportunities.

Implementation Approach:

  • • Mapped developers to companies via email domains
  • • Tracked API usage patterns by organization
  • • Built team expansion scoring
  • • Created developer influence mapping

Expansion Signals:

  • • Multiple developers from same company
  • • Production API key usage
  • • GitHub integration connections
  • • CI/CD pipeline implementations

Results:

Increased individual-to-team conversion by 67% and identified enterprise prospects 3 months earlier in the adoption cycle.

Scenario 4: E-commerce SaaS

Challenge:

Seasonal businesses showed erratic usage patterns that triggered false churn alerts during off-peak periods.

Implementation Approach:

  • • Added business seasonality flags to CRM
  • • Built industry-specific health models
  • • Created year-over-year comparison metrics
  • • Implemented seasonal alert adjustments

Seasonal Adjustments:

  • • Holiday retail vs. Q1 patterns
  • • B2B services vs. consumer seasonal
  • • Geographic market variations
  • • Product category differences

Results:

Reduced false positive churn alerts by 78% and improved CS team efficiency by focusing on truly at-risk accounts rather than seasonal variance.

Summary

Joining product usage data with CRM information creates a powerful foundation for understanding and improving account health. Here's a recap of the key steps and considerations.

✅ What You've Accomplished

  • • Connected product analytics and CRM data sources
  • • Mapped users to accounts for aggregated analysis
  • • Built comprehensive health scoring queries
  • • Created actionable dashboards and visualizations
  • • Established monitoring practices for different teams
  • • Learned to avoid common implementation pitfalls

🎯 Next Steps

  • • Start with a pilot group of high-value accounts
  • • Set up automated alerts for health score changes
  • • Train Customer Success team on new insights
  • • Establish weekly review processes
  • • Plan quarterly model refinements
  • • Expand to include additional data sources

Key Takeaways

45min
Setup time with proper data connections
5 components
User adoption, frequency, breadth, depth, value
Daily
Recommended monitoring frequency for CS teams
MAKE YOUR MOVE
© Airbook 2025 / The full stack data workspace that powers growth.