# Use Checkout studio to track analytics

Track and analyze how your checkout integration is performing for your business.

The [Performance](https://dashboard.stripe.com/checkout/performance) tab in Checkout studio lets you monitor payment volume, track conversion rates, and understand how different Checkout integrations contribute to your revenue. All metrics appear as daily trends, which you can filter by country and Checkout integration, and compare across time periods.

## Tracked Checkout UIs 

The **Performance** tab tracks activity across the following checkout UIs:

- The [Checkout page](https://docs.stripe.com/payments/accept-a-payment.md?payment-ui=checkout&ui=stripe-hosted): A Stripe-hosted payment page. Your customers are redirected to Stripe to complete their payment, and then returned to your site.

- [Payment Links](https://docs.stripe.com/payment-links.md): Shareable URLs that open a Stripe-hosted payment page.

- [Custom Checkout](https://docs.stripe.com/payments/accept-a-payment.md?payment-ui=elements&api-integration=checkout): The Stripe prebuilt UI components embedded in your site that’s backed by a Checkout Session for server-side payment management.

- [Elements](https://docs.stripe.com/payments/accept-a-payment.md?payment-ui=elements&api-integration=paymentintents): The Stripe prebuilt UI components embedded in your site that’s backed by the Payment Intents API.

## Conversion funnel 

The **Performance** tab shows a three-step conversion funnel that tracks how customers move through your checkout flow. This funnel captures sessions where a customer is actively present on your checkout page.

- **Session loaded**: A Checkout page loads in the customer’s browser. This event is the funnel entry point and counts as one session.

- **Session completion attempted**: The customer starts the payment process by clicking the pay or submit button on your Checkout page. This event corresponds to a successful confirm API call.

- **Session completed**: The Checkout Session reaches completion. This event is the conversion point. For most payments, this means Stripe successfully authorizes the payment. For free trials and setup-only sessions, it means the customer saves a payment method.

Your conversion rate is the percentage of initialized sessions that result in a successful payment. Use this metric to monitor the health of your checkout acquisition flow. If your conversion rate drops, investigate whether customers abandon the flow at the completion attempt step or encounter payment failures.

## Metrics 

The **Performance** tab tracks four core metrics. Each is shown as a daily trend line, with the option to compare against a previous time period.

| Metric                     | What it measures                                                                            | How it’s calculated                                           | Revenue included       |
| -------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------- |
| Payment volume             | Total payment volume processed through your checkout integrations in your default currency. | Sum of all successful payment amounts in the selected period. | One-time and recurring |
| Session count              | Number of times a checkout session loaded on a customer’s browser                           | Count of initialized checkout sessions                        | One-time only          |
| Conversion rate            | Percentage of loaded checkout sessions that resulted in a completion                        | Completed sessions divided by loaded sessions                 | One-time only          |
| Average order volume (AOV) | Average amount per successful transaction                                                   | Payment volume divided by the number of successful payments   | One time and recurring |

A successful payment is a payment whose PaymentIntent reaches the `succeeded` state. Payment volume and AOV include both one-time and recurring revenue. Session loads and conversion rate measure only new revenue. Because recurring payments don’t generate sessions, dividing payment volume by session count doesn’t produce your average order value.

> #### Payment volume and session load metrics
> 
> We include revenue from Elements integrations. However, we don’t count those checkout page loads in the session load and conversion rate metrics.

## One-time and recurring revenue 

Stripe attributes each payment to the Checkout integration where the customer originally converted. The Checkout Session’s mode determines whether Stripe classifies that payment as one-time or recurring. Sessions in `payment` or `setup` mode are one-time. The customer loads your Checkout page, enters payment details, and completes a single purchase.

Sessions in `subscription` mode are recurring. This includes the initial subscription charge and all subsequent automatic renewal payments. Stripe attributes those payments back to the original Checkout integration, even though they don’t generate new sessions.

Payments completed through Elements don’t use the Checkout Sessions API. Stripe labels these payments as `Elements`, and includes them in payment volume and AOV, but not in session count or conversion rate.

## Attempted and completed sessions 

`Session completion attempted` and `Session completed` represent the conversion flow from payment submission to payment completion. For most card payments, these steps happen almost at the same time. However, the number of attempts is typically higher than the number of completions.

Common reasons for this difference include:

- **Payment failure**: The customer submits a payment, but the card network or issuer declines the charge. For example, this can happen because of insufficient funds, incorrect card details, or fraud blocks.
- **Authentication failure**: The customer triggers 3D Secure but fails or abandons the authentication challenge.
- **Asynchronous payment method**: For payment methods such as bank debits and SEPA, the customer confirms the payment, but the funds don’t settle until days later. A session might appear as attempted on day 1 and completed on day 3 or later.

For manual capture integrations, such as hotels or e-commerce businesses with shipping, session completion happens at authorization, not at capture. As a result, these two steps still coincide even though you capture the payment later, when the PaymentIntent is in `requires_capture` status.

To investigate payment acceptance and authentication performance, see [Payment Analytics](https://docs.stripe.com/payments/analytics/acceptance.md).

> #### Free trials and 0 USD payments
> 
> These sessions skip the payment submission step, for example, when your integration doesn’t collect a payment method. Stripe doesn’t set `Session completion attempted` for these sessions. Instead, they move directly from `Session loaded` to `Session completed`. `Session completed` might be higher than `Session completion attempted` if your integration includes a free trial or 0 USD flows.

## Filters 

Use filters to control the data shown across all metrics and charts. Filters apply globally, so changing a filter updates every metric, chart, and trend line on the page.

| Filter                         | Description                                                                                                                                                                                                                                   |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Country                        | Filter by your customers’ geographic location, based on the client browser IP address at the time of the Checkout Session.                                                                                                                    |
| Checkout                       | Filter by the Checkout integration your customers used: Checkout Page, Payment Links, custom Checkout, or Elements.                                                                                                                           |
| Adaptive Pricing enabled       | Filter by sessions where Adaptive Pricing was enabled, which allows your customer to pay in their local currency. Use this filter to isolate the impact of localized pricing on checkout performance.                                         |
| Dynamic payment method enabled | Filter by sessions where dynamic payment method ordering was enabled, which displays the most relevant payment methods for each customer. Use this filter to measure how relevant local payment methods affect conversion and payment volume. |
| Time period                    | Select a time range for all charts. Available periods include the past week, month, quarter, and year. Use **Compare to previous period** to compare your current metrics with the equivalent previous period.                                |

Toggle **Compare to previous period** to overlay the equivalent earlier time range on your daily trend charts. For example, if you view the past 30 days, the comparison shows the previous 30 days. Use this to identify whether a metric trends up or down relative to your recent baseline.

## Reading your data 

The **Performance** tab helps you answer if your Checkout integration is performing well for your business.

If your business primarily uses subscriptions or other recurring payments, **Recurring payment volume** reflects all subscription charges attributed to each original Checkout integration, including the initial payment and automatic renewals. Focus on session count and conversion rate to track new customer acquisition. Use the one-time versus recurring split to understand how much of your total volume comes from retention versus new transactions.

If your business primarily uses one-time transactions, payment volume and conversion rate typically move in the same direction. If they diverge—for example, if conversion rate stays steady but payment volume drops—investigate changes in average order value or shifts in your payment method mix. For transaction-heavy businesses, average order value is a useful diagnostic metric. A decline in average order value alongside stable conversion can indicate that your Checkout flow is attracting lower-value orders or that pricing or discount changes are affecting revenue.

Patterns to watch for include:

- **Sudden drop in session count**: This pattern can indicate a technical issue with session initialization, a change in traffic sources, or a configuration problem with your Checkout integration. Check whether the drop is isolated to a specific Checkout integration or country.
- **Conversion rate decline with stable session count**: This pattern means customers reach your Checkout page but don’t complete payment. Investigate payment method availability, page load performance, or friction in the checkout flow.
- **Payment volume divergence from conversion rate**: For subscription businesses, this pattern is often normal because recurring revenue accumulates over time. For transaction businesses, this pattern can signal a shift in average order value or product mix.
- **Average order value decline**: Review whether product pricing, discount strategy, or customer segments are changing. A lower average order value isn’t always a problem. It might reflect growth in a high-volume, lower-priced product line.