Conversion Tracking

What's a Conversion?

A conversion is when a user does the thing you want them to do. Examples:

• Signs up for your app
• Makes a purchase
• Subscribes to a plan
• Fills out a contact form
• Starts a free trial

When SupaStory knows what conversions matter to you, it can tell you which bugs are blocking users from converting—and estimate how much money you're losing.

Why Track Conversions?

Without conversion tracking, all bugs look the same. With it, you can see:

• "This button bug is blocking 12% of purchases"
• "Fixing this form issue could recover $2,400/month"
• "After merging that PR, signups increased 8%"

It turns "there's a bug" into "this bug is costing you money."

Setting Up Conversions

You can define conversions in your dashboard or in code.

Option 1: Dashboard Setup

Go to Settings > Conversions and add your goals. No code required.

Option 2: Code Setup

Add conversion goals when you initialize SupaStory:

import { SupaStory } from '@supastory/capture-sdk';

SupaStory.init({
  projectKey: 'pk_live_...',
  conversions: {
    goals: [
      {
        name: 'signup',
        selector: '[data-conversion="signup"]', // Track when this element is clicked
      },
      {
        name: 'purchase',
        event: 'purchase', // Track when you call trackConversion('purchase')
      },
    ],
  },
});

Tracking Conversions in Code

For events that happen in JavaScript (not just button clicks), use trackConversion:

// When a user completes a purchase
SupaStory.trackConversion('purchase', {
  value: 49.99,      // How much the purchase was worth
  currency: 'USD',
});

// When a user signs up
SupaStory.trackConversion('signup', {
  plan: 'free',
});

// When a user starts a trial
SupaStory.trackConversion('trial_started');

Including the value helps SupaStory estimate dollar impact for bugs that block conversions.

Understanding the Numbers

When you have conversion tracking set up, every insight includes impact data:

Issue: Checkout button unresponsive on mobile

Sessions affected: 234
Users who didn't convert: 89
Estimated monthly impact: ~$4,680

The AI calculates this by comparing conversion rates between sessions that hit the bug versus sessions that didn't.

Measuring Fix Impact

After you merge a fix, SupaStory automatically tracks what happens:

• Before: What was the conversion rate with the bug?
• After: What's the conversion rate now?
• Impact: How many more users are converting?

You can see this in your dashboard under Insights > Merged Fixes.

Common Conversion Goals

Here are goals that most apps track:

Tips

Start simple — Pick 2-3 conversions that really matter. You can always add more later.

Add dollar values — If you know a signup is worth $10 or a purchase averages $75, include that. It makes impact estimates more meaningful.

Check weekly — Review which bugs are blocking conversions. Fix the expensive ones first.