Skip to main content
Stripe is a payment processing platform that powers subscriptions and revenue for businesses. Connect Stripe to Kasava to automatically track MRR, ARR, churn rates, and other key revenue metrics for your product goals.

What You Can Do

With the Stripe integration, you can:
  • Track MRR & ARR - Monitor monthly and annual recurring revenue with optional trial inclusion
  • Count customers - Track total, active, new, or churned customer counts over time
  • Monitor subscriptions - Count subscriptions by status (active, trialing, past due, canceled)
  • Measure revenue - Track total revenue, net revenue, refunds, and processing fees
  • Calculate ARPU - Measure average revenue per user over time
  • Analyze churn - Track customer churn rate, revenue churn rate, and churned MRR
  • Monitor NRR - Track net revenue retention to measure expansion vs contraction
  • Set up alerts - Get notified when metrics cross thresholds or change significantly
  • Test mode support - Use test API keys to track metrics from test data during development

Connecting Stripe

1

Navigate to Settings

Click your profile menu in the top-right corner and select Settings, then go to Integrations
2

Find Stripe

Scroll to the Analytics & Data section and locate the Stripe integration card
3

Click Connect

Click the Connect button on the Stripe card
4

Enter Credentials

In the configuration dialog, enter:
  • Integration Name - A name to identify this connection (e.g., “Production Stripe”)
  • Secret API Key - Your Stripe secret key (starts with sk_live_ or sk_test_)
5

Save

Click Connect to save your integration
Stripe connection dialog with secret key field

Finding Your API Key

  1. Log in to your Stripe Dashboard
  2. Go to Developers > API keys
  3. Copy your Secret key (click to reveal if hidden)
Keep your secret key secure. Never share it publicly or commit it to version control. Kasava encrypts and securely stores your credentials.

Test Mode vs Live Mode

Stripe provides separate API keys for test and live mode:
Key PrefixModeUse Case
sk_test_TestDevelopment and testing with simulated data
sk_live_LiveProduction with real customer and payment data
When using a test mode key, metrics will only reflect test data. Use live mode keys to track real production metrics.

Linking Metrics to Goals

Once connected, you can link Stripe metrics to your product goals for automatic progress tracking.
1

Open a Goal

Navigate to your product’s Analysis section, select the Goals tab, and click on a goal
2

Add a Metric

In the goal detail dialog, click Add Metric in the metrics section
3

Select Stripe

Choose Stripe as the data source from the metric source picker
4

Choose Metric Type

Select the type of metric you want to track (see Metric Types below)
5

Configure and Test

Configure your metric settings and click Test Query to verify it works
6

Save

Click Link Metric to add the metric to your goal
Link Metric dialog showing Stripe query configuration

Metric Types

Stripe supports eight metric types for tracking different aspects of your subscription business:

MRR (Monthly Recurring Revenue)

Track your monthly recurring revenue from active subscriptions.
SettingDescription
Include TrialsToggle to include or exclude trialing subscriptions
Use cases:
  • Track overall business health
  • Monitor revenue growth month-over-month
  • Set revenue targets for product launches

ARR (Annual Recurring Revenue)

Track your annualized recurring revenue (MRR × 12).
SettingDescription
Include TrialsToggle to include or exclude trialing subscriptions
Use cases:
  • Report annual revenue projections
  • Compare against annual business goals
  • Track year-over-year growth

Customer Count

Count customers based on their status over a time period.
SettingOptions
Customer TypeAll Customers, Active Customers, New Customers, Churned Customers
Time RangeLast Day, Last Week, Last Month, Last Quarter, Last Year
Use cases:
  • Track total customer growth
  • Monitor new customer acquisition
  • Identify churned customer trends

Subscription Count

Count subscriptions by their current status.
SettingOptions
Subscription StatusAll, Active, Trialing, Past Due, Canceled, Incomplete
Use cases:
  • Monitor active subscription count
  • Track trial conversion pipeline
  • Identify at-risk subscriptions (past due)

Revenue

Track various revenue metrics over time.
SettingOptions
Revenue MetricTotal Revenue, Net Revenue, Refunds, Fees
Time RangeLast Day, Last Week, Last Month, Last Quarter, Last Year
Use cases:
  • Track total collected revenue
  • Monitor net revenue after refunds
  • Analyze refund trends
  • Track Stripe processing fees

ARPU (Average Revenue Per User)

Calculate the average revenue generated per customer.
SettingOptions
Time RangeLast Month, Last Quarter, Last Year
ARPU is calculated over monthly periods minimum to ensure meaningful averages. Daily and weekly time ranges are not available.
Use cases:
  • Measure monetization efficiency
  • Track pricing strategy impact
  • Compare customer segments

Churn

Track customer or revenue churn metrics.
SettingOptions
Churn MetricCustomer Churn Rate, Revenue Churn Rate, Churned MRR
Time RangeLast Month, Last Quarter, Last Year
MetricDescription
Customer Churn RatePercentage of customers lost in the period
Revenue Churn RatePercentage of revenue lost in the period
Churned MRRAbsolute MRR lost from cancellations
Use cases:
  • Monitor customer retention health
  • Identify revenue leakage
  • Set churn reduction targets

NRR (Net Revenue Retention)

Track net revenue retention to measure expansion vs contraction.
SettingOptions
Time RangeLast Month, Last Quarter, Last Year
NRR measures revenue retained from existing customers including:
  • Upgrades and expansions (+)
  • Downgrades (-)
  • Churned revenue (-)
An NRR above 100% indicates net expansion; below 100% indicates net contraction. Use cases:
  • Measure upsell/expansion effectiveness
  • Track customer value growth over time
  • Benchmark against industry standards

Refresh Intervals

Choose how often Kasava fetches new data from Stripe:
IntervalDescription
HourlyUpdates every hour - best for real-time dashboards
DailyUpdates once per day - best for most goals
WeeklyUpdates once per week - best for long-term trends
For most revenue metrics, daily refresh is recommended. MRR, ARR, and customer counts don’t change frequently enough to warrant hourly updates.

Setting Up Alerts

After linking a metric to a goal, you can configure alerts to be notified when values change:

Threshold Alerts

Get notified when a metric crosses a specific value:
  • Threshold - The value that triggers the alert (e.g., MRR drops below $10,000)
  • Direction - Alert when the metric goes above or below the threshold

Change Alerts

Get notified when a metric changes by a certain percentage:
  • Percentage - The change percentage that triggers the alert (e.g., 10% churn increase)
  • Direction - Alert on increase, decrease, or any change

Testing Your Connection

After configuring a metric query, always click Test Query before saving. This will:
  1. Verify your API credentials are valid
  2. Execute the query against Stripe’s API
  3. Show the current metric value
  4. Confirm the configuration is correct
Test query result showing MRR value

Managing Integrations

View Integration Status

Navigate to Settings > Integrations to see all connected Stripe integrations and their status.

Create Integration Metrics

You can create reusable metrics at the integration level that can be linked to multiple goals:
1

Go to Integration Settings

Navigate to Settings > Integrations and click Manage on your Stripe integration
2

Create Metric

Click Add Metric to create a new integration-level metric
3

Configure

Set up the query configuration and give the metric a descriptive name
4

Link to Goals

The metric can now be linked to any goal in your organization

Disconnect Integration

1

Go to Settings

Navigate to Settings > Integrations
2

Find Stripe

Locate the Stripe integration card (it will have a green “Connected” indicator)
3

Click Manage

Click the Manage button on the card
4

Disconnect

Click Disconnect and confirm to remove the integration
Disconnecting will stop all metric syncing for goals linked to this integration. Historical data will be preserved, but no new data will be fetched.

Troubleshooting

Verify your secret key starts with sk_live_ or sk_test_. Restricted keys or publishable keys (pk_) won’t work. Check that the key hasn’t been rolled or deleted in Stripe.
Ensure you have subscriptions with recurring prices (not one-time payments). Check that the subscriptions are in an active state and not trialing (unless you enabled “Include Trials”).
Check the sync status in the goal’s metric section. If it shows an error, try disconnecting and reconnecting the integration. Ensure your API key hasn’t been rolled.
Verify the time range matches your expectations. Short time ranges can show higher churn rates. Also check if you’re measuring customer churn vs revenue churn, which can differ significantly.
If you see a warning about test mode, you’re using an sk_test_ key. This is fine for development, but switch to an sk_live_ key to track real production data.
Kasava counts customers with the specific status you selected. The Stripe dashboard may show different views or include deleted customers. Ensure your filter settings match.

Best Practices

Start with MRR - Monthly recurring revenue is the most important SaaS metric. Start by tracking MRR before adding more complex metrics like churn or NRR.
Use live keys for production - Test keys are great for development, but make sure to switch to live keys when you’re ready to track real business metrics.
Match time ranges to your business cycle - If you report monthly, use monthly time ranges. Quarterly businesses should use quarterly ranges for meaningful comparisons.
Set meaningful thresholds - When setting up alerts, use thresholds that indicate real business impact, not just noise. A 5% MRR change might be normal variance; 20% likely isn’t.
Track both customer and revenue churn - They tell different stories. High customer churn with low revenue churn means you’re losing low-value customers, which may be fine.