Using Microsoft Clarity to Improve SaaS Onboarding

SaaS onboarding is where you win or lose users. Most teams track signup conversion rates but have no visibility into what happens after signup. Microsoft Clarity gives you that visibility for free — heatmaps, session recordings, and behavioral signals that reveal exactly where new users get stuck.

Why SaaS Onboarding Needs Behavioral Analytics

Product analytics tools like Mixpanel or Amplitude tell you how many users completed each onboarding step. But they don't tell you why users dropped off at step 3. Did they not see the button? Did they rage-click on something that wasn't working? Did they scroll past the instructions?

This is the gap Clarity fills. By watching session recordings of users going through your onboarding flow, you can identify specific UX problems that aggregate metrics would never reveal.

Setting Up Clarity for SaaS Onboarding

Before diving into analysis, set up Clarity to capture the right data:

1. Install the Tracking Script

Add the Clarity JavaScript snippet to your application's layout template. For SaaS apps, this typically goes in the base HTML template that wraps all authenticated pages:

<script type="text/javascript">
  (function(c,l,a,r,i,t,y){
    c[a]=c[a]||function(){(c[a].q=c[a].q||[]).push(arguments)};
    t=l.createElement(r);t.async=1;t.src="https://www.clarity.ms/tag/"+i;
    y=l.getElementsByTagName(r)[0];y.parentNode.insertBefore(t,y);
  })(window,document,"clarity","script","YOUR_PROJECT_ID");
</script>

2. Configure URL Masking

SaaS URLs often contain user IDs or workspace slugs (e.g., /workspace/abc123/settings). In Clarity's Settings, set up URL grouping to combine these into logical page groups. This way, all settings pages are analyzed together instead of being treated as unique URLs.

3. Set Up Custom Tags

Use Clarity's custom tags to identify onboarding sessions. You can tag sessions with the user's onboarding stage, plan type, or signup source:

// Tag the session with onboarding step
clarity("set", "onboarding_step", "profile_setup");
clarity("set", "plan", "trial");
clarity("set", "signup_source", "google_ads");

These tags let you filter recordings and heatmaps to see only users at a specific onboarding stage.

Key Onboarding Metrics to Watch in Clarity

Once data is flowing, focus on these behavioral signals for onboarding pages:

Rage Clicks on Onboarding Steps

Rage clicks during onboarding are critical signals. They indicate that a new user — someone who just decided to try your product — is already frustrated. Common causes in onboarding flows:

• Submit buttons that don't respond due to validation errors the user can't see
• Loading states without visual feedback (user thinks the click didn't register)
• Disabled buttons without explanation of what needs to be completed first
• Integration setup steps that fail silently

Dead Clicks on Feature Discovery

During onboarding, users explore your UI and click on things they think are interactive. Dead clicks reveal:

• UI elements that look like buttons but aren't (labels styled like links, icons without actions)
• Placeholder content that users try to interact with
• Screenshots or illustrations that users think are interactive demos

Scroll Depth on Setup Pages

If your onboarding has instructional pages or setup wizards, scroll heatmaps show whether users read the instructions. If 70% of users don't scroll past the first paragraph of your setup guide, the guide needs to be restructured — not just rewritten.

Quick Backs from Key Pages

Quick backs (users immediately navigating away from a page) during onboarding indicate that users reached a page they didn't expect or couldn't understand. This is especially problematic on:

• Integration setup pages (too complex, user retreats)
• Pricing/upgrade pages shown during trial (unexpected paywall feeling)
• Advanced configuration screens shown too early in the flow

Analyzing the Signup Flow

The signup flow is the first interaction users have with your product. Here's how to analyze it with Clarity:

Step 1: Watch 20 Recordings of Signup Completions

Filter recordings to the signup page and watch users who successfully completed registration. Note patterns:

• How long does it take? If users spend more than 60 seconds on a signup form, it's too complex.
• Do users hesitate on any field? Watch for pauses before typing.
• Do users scroll up and down looking for something?

Step 2: Watch 20 Recordings of Signup Abandonment

Filter for sessions that visited the signup page but didn't convert. Common findings:

• Users start filling out the form but stop at a specific field (often phone number, company size, or credit card)
• Users scroll to the bottom looking for pricing information or terms before committing
• Social login buttons don't work or take too long to respond

Step 3: Check Heatmaps for Click Distribution

The click heatmap on your signup page reveals where attention goes. Healthy patterns show clicks concentrated on form fields and the submit button. Unhealthy patterns show:

• Clicks on the navigation or logo (users leaving before signing up)
• Clicks on "Terms" or "Privacy" links (users hesitating, wanting more info)
• Clicks on areas outside form fields (confusion about the interface)

Finding Drop-Off Points in Onboarding Funnels

Most SaaS onboarding follows a multi-step pattern: signup, profile setup, first action, integration, and value delivery. Here's how to use Clarity at each transition point:

Signup to First Action

This is the most critical transition. After signing up, does the user actually do something? Use Clarity's custom tags to identify sessions where users signed up but never performed the first key action. Watch these recordings to understand what went wrong. Common findings:

• The post-signup screen is a blank dashboard with no guidance
• Users are dropped into settings instead of the core experience
• A tutorial modal appears but users dismiss it immediately (and then don't know what to do)

First Action to Regular Use

After the initial action, does the user come back? Watch recordings of second and third sessions to see:

• Do users remember how to find the feature they used in their first session?
• Are they exploring new features or repeating the same action?
• Do they encounter errors or confusing UI on subsequent visits?

Practical Example: Optimizing a Project Management Tool's Onboarding

Here's a realistic example of how Clarity data leads to specific improvements:

Clarity findings:

1. 40% of new users rage-click on the "Create Project" button because it's disabled until they enter a project name — but the name field is above the fold while the button is below it
2. Dead-click heatmap shows users clicking on the template thumbnails, expecting a preview — but clicking does nothing
3. Scroll heatmap shows only 25% of users see the "Invite Team Members" section at the bottom of the setup page
4. Quick backs are high on the "Integrations" page, suggesting it's shown too early

Changes made:

1. Move the project name field directly above the create button, both visible without scrolling
2. Make template thumbnails clickable to show a preview modal
3. Move the team invitation step to after the first project is created (when users have context)
4. Remove the integrations page from the initial onboarding flow — move it to a "Set up later" section

Results: Onboarding completion rate increased from 34% to 58%, with a corresponding improvement in 7-day retention.

Automating Onboarding Analysis

Manually watching session recordings is time-consuming. For ongoing monitoring, consider these approaches:

• Weekly Clarity reviews: Dedicate 30 minutes each week to watching onboarding recordings. Focus on sessions with rage clicks or dead clicks.
• Automated reporting: Use tools like ClarityInsights to automatically pull Clarity data and send weekly reports. This ensures onboarding friction signals are surfaced without manual effort.
• Alert on spikes: Monitor rage-click rates on key onboarding pages. A sudden spike often indicates a bug or broken flow after a deployment.

Privacy Considerations for SaaS

When using Clarity on a SaaS application, be mindful of privacy:

• Mask sensitive data: Clarity automatically masks common input fields, but verify that customer data (names, emails, financial data) is properly masked in recordings.
• Respect user preferences: If your SaaS serves enterprise customers, some may require that session recording be disabled for their users.
• Update your privacy policy: Disclose that you use session recording tools and explain what data is collected.
• Don't record on sensitive pages: Exclude pages that display sensitive customer data (billing details, API keys) from Clarity tracking.